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
- csc.rsp -additionalfile files are not treated as dependencies and are not reloaded when the file contents change
- Error ‘cannot use casts on l-values’ when a variable is assigned inside a second-level nested if statement before being used in a conversion
- "You cannot save to an invalid folder" warning dialog box is shown when canceling Tile Palette creation
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [Android] Stage information is not logged when Log Shader Compilation is enabled
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.