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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #878740