Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
2019.2.0a4
Issue ID
1129130
Regression
No
Non-Convex Mesh Collider's Wireframe is invisible when Mesh Renderer Component is active
How to reproduce:
1. Open the "SampleScene" Scene in the attached "bugmeshcollider.zip" Project
2. Click on the Track > "submesh_0" GameObject in the Hierarchy
3. Observe the GameObject in the Scene View
Expected behavior: The Mesh Collider's Wireframe is outlining the GameObject
Actual behavior: The Wireframe is invisible
Reproducible with: 2017.4.21f1, 2018.3.7f1, 2019.1.0b4, 2019.2.0a6
Note: The Wireframe is visible after disabling Mesh Renderer in the Inspector. However, this is not a viable Workaround as the Object become invisible. If you check "Convex" Checkbox under the Mesh Collider's Component - the Wireframe becomes visible.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
I suggest to use the physics debug view instead. It's a faster, and a more convenient way to debug physics with meshes.