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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.