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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.