Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a9
2019.3.0f3
2020.1
Issue ID
1215857
Regression
No
Mesh Collider performance drop when "Everything" Cooking Option is enabled
Reproduction steps:
1. Open attached project "1215857_mesh" and scene "SampleScene"
2. Enter Play Mode and observe the Profiler
3. Exit Play Mode, open "Cube" in Prefab Mode and the Inspector in Debug Mode
4. Change Mesh Collider's "Cooking Options" from 30 to -1 (all Cooking Options will be selected and "Everything" will be marked)
5. Enter Play Mode and observe the Profiler
Expected result: Performance is the same as when all the options are selected but the "Everything" option is not marked
Actual result: Editor performance is worse ("Mesh.Bake Scaled Mesh PhysX CollisionData" can be seen in the Profiler)
Reproducible with: 2019.3.0a9, 2019.3.0f6, 2020.1.0a22
Could not test with: 2017.4.36f1, 2018.4.17f1, 2019.2.20f1, 2019.3.0a8 ("Use Fast Midphase" not implemented)
Workaround: Resetting the Mesh Collider component or setting Cooking Options to 30 in the Inspector's Debug Mode
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
- Crash on GetSceneGUID when building a scene
- ComputeShader compilation is executed sequentially, resulting in subpar performance
- Crash on UnityObjectToString(Object*) when an object has a field with a type mismatch and an active Animator
- Visual Effect Graph Node creation folder colors are not set to default by default
- The Attach button is active and shows the Attached to Visual Effect" tooltip when the Visual Effect Graph is no longer attached
Resolution Note (fix version 2019.3):
Fixed in 2019.3.7f1