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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment