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
- Adaptive Probe Volume “No Adaptive Probe Volume in Scene” warning is shown only on the first time and is never shown again when baking the Adaptive Probe Volumes with all the Adaptive Probe Volume components disabled
- “NullReferenceException” thrown in Console when changing Profile field to ‘DefaultLookDevProfile’ in Lighting window after deleting Directional Light
- "GardenDraft_LightingSettings" Asset is included in the URP Sample Template
- “Releasing render texture that is set as Camera.targetTexture!” Error thrown in the Console when undoing/redoing Camera addition in Graphics Compositor window > Render Schedule list
- The cursor moves into wrong place when renaming folder/asset
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.