Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
1
Found in
2017.2.0p1
Issue ID
996035
Regression
No
Mesh collider gets corrupted if no triangles are specified
How to reproduce:
1. Open attached Unity project "MeshColliderBug"
2. Open the MeshColliderBug scene
3. Select MediumPolySphere in the Inspector window
4. Note that it has a polygon mesh in the scene view
5. Right-Click on the Mesh Collider Bug (Script) in the Inspector window
6. Select "0) Set Original Mesh"
7. Select "1) Set broken Mesh On Collider"
8. Note that the mesh disappears
9. Select "2) Set Mesh On Collider"
10. Note that, even though a new mesh has been set, the collider is still broken
Expected result: Setting a new mesh 'fixes' the mesh collider.
Actual result: Collider is still broken after setting new mesh.
Reproduced with: 2018.1.0b6, 2017.3.1f1, 2017.2.1p3, 2017.1.3p1, 5.6.5p1.
Fixed in: 2019.2.0a5, 2019.1.0b5, 2018.3.9f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment