Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0a9
2019.4
2019.4.9f1
2020.1
2020.2
2021.1
Issue ID
1297721
Regression
Yes
A hard stack overflow happens when raycasting vs a dense mesh in BV4_ProcessStreamKajiyaOrderedQ
How to reproduce:
1. Open the user's attached "BrokenMeshRepro.zip" project
2. Open the "SampleScene" Scene
3. Drag the mouse on "BrokenMesh" GameObject to Raycast it
Expected result: No crash occurs
Actual result: Editor crashes
Reproducible with: 2019.3.0a9, 2019.4.16f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0a10
Not reproducible with: 2018.4.30f1, 2019.3.0a8
Notes:
- Editor also crashes when opening the Physics Debugger and checking the Collision Geometry property
- The issue is reproducible in both Play Mode and in Build
WORKAROUND: Disable "Use Fast Midphase" option on such meshes.
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
- 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
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
Resolution Note:
A workaround is available but the real fix is expected to come with PhysX 5 that is not yet out.