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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #878740