Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0a9
2019.3.13f1
2020.1
2020.2
Issue ID
1247599
Regression
Yes
Editor crashes in Play Mode when hovering the mouse over a mesh with a MeshCollider
How to reproduce:
1. Tester-attached package(MeshColliderCrash.unitypackage)
2. Create a new Unity project
3. Import the package
4. Open the CrashScene
5. Enter Play Mode and hover the mouse over/click the model terrain surface
Expected result: the Editor does not crash
Actual result: the Editor crashes
Reproducible with: 2019.3.0a9, 2019.3.15f1, 2020.1.0b10, 2020.2.0a12
Not reproducible with: 2017.4.40f1, 2018.4.24f1, 2019.3.0a8
Notes:
Disabling the Terrain/default MeshCollider prevents the crash when hovering over the terrain
WORKAROUND: Disable 'Use Fast Midphase' in the cooking options of this mesh.
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
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Resolution Note:
Unfortunately, this mesh cannot be used with the 'Fast Midphase' cooking option, because the spatial search tree that is built here turns out to be degenerate. It's addressed in the upcoming PhysX 5, but we cannot back-port that code, sadly.