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
- “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
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.