Search Issue Tracker
Active
Votes
0
Found in
2022.3.56f1
6000.0.34f1
6000.1.0b1
Issue ID
UUM-95801
Regression
No
Crash on BV4_OverlapBoxAll when moving in play mode
Reproduction steps:
1. Open the attached project "CrashRepro"
2. Enter the play mode
3. Select the game view tab
4. Move around for a few seconds (might need to jump - “space“, to not fall through the floor)
Expected result: The play mode continues
Actual result: Editor crashes
Reproducible with: 2022.3.56f1, 6000.0.34f1, 6000.1.0b1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
Upgrading the project to 6000.x seems to break the meshes in the scene.
The crash is significantly less frequent on 6000.1 and took about 5 minutes of walking around to crash, while it only took a few seconds in previous versions
First few lines of stack trace:
{noformat}0x00007ff61fa6be3f (Unity) BV4_OverlapBoxAll
0x00007ff61f9d70dc (Unity) physx::Gu::intersectBoxVsMesh_BV4
0x00007ff61f995ce8 (Unity) physx::PxMeshQuery::findOverlapTriangleMesh
0x00007ff61f80da79 (Unity) physx::PxMeshOverlapUtil::findOverlap
0x00007ff61f7dddb0 (Unity) outputMeshToStream{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Undoing Animator Parameter name change breaks references to it
- Crash on BV4_OverlapBoxAll when moving in play mode
- Custom mesh water surface normal map fades out when Y Position increases
- Sprite renderer does not issue draw calls correctly when using SRP Batcher
- [Android] Flickering artifacts when using "ScriptableRenderer.EnqueuePass(RenderPassEvent.BeforeRenderingPostProcessing)" multiple times
Add comment