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
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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/