Search Issue Tracker
Third Party Issue
Third Party Issue in 2023.3.X
Votes
2
Found in
2021.3.33f1
2022.3.14f1
2023.2.1f1
2023.3.0a16
Issue ID
UUM-57060
Regression
No
Custom GameObject crashes the Editor when the Mesh Collider Component is added
How to reproduce:
- Open the “MeshColliderCrash bug.zip“ project
- Select the “crashing-mesh-collider“ GameObject in Hierarchy
- Add a Mesh Collider to the GameObject
- Observe the Editor
Expected result: The Mesh Collider Component is added
Actual result: The Mesh Collider Component causes a crash
Reproducible in: 2021.3.33f1, 2022.3.14f1, 2023.2.1f1, 2023.3.0a16
Reproduced on: Windows 11 Pro
Not reproduced on: Mac M1 12.6.1, Mac M1 13.5.2, Linux Ubuntu 20.03 5 LTS
Notes:
- Workaround: Before adding the Collider remove the Mesh from the Mesh Filter Component, Add the Mesh Collider, and Assign the “crashing-mesh-collider“ Mesh for the Mesh Filter and the Mesh Collider Components
- After the workaround Information, Warnings, and StackOverflow Errors appear in the Console, and memory usage is increased when anything is changed within the Editor (most noticible by toggling the Convex property off, see the workaround video)
- Bug reporter window does not open after the crash
WORKAROUND: Disable the fast midphase cooking option.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This is a problem in the PhysX version we're using at the moment. For until we have a newer version that doesn't suffer from this problem, a possible workaround is to disable the fast midphase option in the MeshCollider cooking options.
Resolution Note (2023.3.X):
This is a problem in the PhysX version we're using at the moment. For until we have a newer version that doesn't suffer from this problem, a possible workaround is to disable the fast midphase option in the MeshCollider cooking options.