Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1117386
Regression
No
Mesh scaling results in performance drop when using non-default Mesh Collider parameters
Reproduction steps:
1. Open the attached project
2. Open the "SampleScene" scene
3. Press "Play"
4. Select all children GameObjects of the GameObject "Lambo_James_Robbins"
5. Inside Mesh Collider, set the Mesh Cooking Options -> Everything
Expected: Editor does not stutter or has minimal performance impact
Actual: Editor starts stuttering a lot
Reproduced with: 2017.4.18f1, 2018.3.3f1, 2019.1.0a14, 2019.2.0a1
Note: All pre 2018.3 versions had an "Inflate Convex Mesh" option which if turned off after selecting "Everything" makes the performance smooth again.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Custom mesh flags are per MeshCollider instance, and have to baked into the mesh when cooking, it's not something we can apply on top of an already cooked stream, like we do with scaling. For that reason, the usage of custom cooking flags will make it so that we cook a new copy of a mesh per each instance.