Search Issue Tracker
Duplicate
Votes
0
Found in
5.5.0p4
Issue ID
881243
Regression
Yes
Crash in physx::PxsBroadPhaseContextSap::batchUpdate when disabling/enabling and changing scale of physics objects
To reproduce:
1. Open attached project "crashDone.zip"
2. Open and Play "LilyPadCrash" scene.
3. Open Scene views, Select "Main Camera" in hierarchy and drag it around over white platform. (no crash)
4. Stop the Play mode. Open "LilyPadTilting" prefab, select it's child "visual" and change it's Scale Z to be negative.
5. Press play, and drag around "Main Camera" again. (crash).
Expected result: Objects are activated/deactivated normally.
Actual result: Unity crashes.
Reproducible with: 5.5.0f1, 5.6.0b10
Not Reproducible: 5.5.0b9
Notes:
This happens when activating/deactivating and setting scale of GameObject with RigidBody, MeshCollider and negative Scale.
Workaround:
Set scale to be positive.
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
This is a duplicate of issue #878740