Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.1
2020.2.0b7
2021.1
Issue ID
1286866
Regression
No
[PhysX] Articulation joint Motion - "Limited" can be broken by force
How to reproduce:
1. Open the user's attached project ("ArmRobot.zip")
2. Enter Play mode
3. Aim at the robot arm and shoot spheres clicking "Space Bar" until the "Base" is forced to rotate and spin out of control
Expected results: The "Base" of the robot arm does not rotate because Motion is set to "Limited"
Actual results: The "Base" of the robot arm is forced to rotate and spins out of control
Reproducible with: 2020.1.15f1, 2020.2.0b13, 2021.1.0a7
Couldn't test with: 2018.4.29f1, 2019.4.15f1 (PhysX didn't have Articulation Bodies yet)
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
Resolution Note:
Articulation is pushed into an unsolvable configuration by an incoming large rigidbody.