Search Issue Tracker
Third Party Issue
Votes
0
Found in
2020.3.18f1
Issue ID
1378062
Regression
No
Issue with teleporting Articulation body with spherical joints
This issue has no description.
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:
Teleporting the root body doesn't imply resetting the articulation pose actually, all it does is to move the root, and make all the children follow on with the offset. Unfortunately, that creates some residual velocities in the spherical joints code that PhysX can't really deal with. Until we have a proper fix from Nvidia, we recommend to obtain pose somewhere during the init sequence (with articulationBody.GetJointPositions), and then immediately apply this pose right after teleportation. This will have the effect of resetting agent to initial state safely & reliably well.