Search Issue Tracker
By Design
Votes
2
Found in
2017.3.0b9
2017.3.0b10
Issue ID
971836
Regression
Yes
[Regression] Generating a MeshCollider took 5-10 times longer
How to reproduce:
1. Download attached project file
2. Enter Play Mode
Actual result: In Unity 2017.3.0b9 the time it takes to add the MeshCollider and assign the mesh is 17-35ms. In Unity 2017.3.0b10 it takes 159-250ms, which is over 5-10 times slower. For larger or more complex meshes the difference increases even further
Reproduced with: 2017.3.0b10, 2017.3.0b11
Not reproduced with: 2017.3.0b9, 2018.1.0a5
Regression since: 2017.3.0b10
Comments (1)
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
- “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
Peter77
Nov 23, 2017 16:41
Related forum thread:
https://forum.unity.com/threads/adding-a-meshcollider-much-slower-in-b10-than-in-b9.505809/