Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2020.3.35f1
2021.3.5f1
2022.1.6f1
2022.2.0a17
2023.1.0a2
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-7397
Regression
No
A mixed hierarchy of ArticulationBodies and Rigidbodies is read back incorrectly
If in a hierarchy, a Rigidbody is parented to an ArticulationBody, and connected to it with a joint, then its position won't be correctly reflected by the Transform, even though the actual position as seen by the physics engine was correct (see the Physics Debugger).
To reproduce:
1) Open the project attached to this case
2) Open the art-test scene
3) Press play
4) Make sure the physics debugger is open (Window - Analysis - Physics Debugger)
5) Notice that the sphere on the right ("parented") is not drawn solid. This is because the visual position (Transform) is different from the physical position (as shown by the Debugger)
6) Notice that the magnitude of the drift depends on the "Target Velocity" of the child articulation.
Expected: The sphere on right should look like the sphere on the left, that is the physical position should be identical to its transform.
WORKAROUND: Unparent all Rigidbodies from ArticulationBodies.
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
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
- New Hierarchy visibility and pickability icon behavior differs from documentation
- [Usability] Selected node gets unselected when undoing changes in the Graph Inspector Node Settings tab
Resolution Note:
After review we have elected not to address this issue at this time.
Resolution Note (6000.0.X):
After review we have elected not to address this issue at this time.