Search Issue Tracker
Fixed in 2022.2.X
Votes
1
Found in
2022.1
2022.1.0b3
2022.2
Issue ID
1397106
Regression
No
ArticulationBody index hierarchy is incorrect when using GetDriveForces method
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. Press the Play button
4. In the Hierarchy window, select the GameObject "revolute joint" (under "root" -> "fixed joint")
5. In the Inspector window, observe the Body Index value under the Arti Force (Script) component
Expected result: The information from the Revolute joint is supposed to come in at index 3 from the GetDriveForces method
Actual result: The information from the Revolute joint comes in at index 0
Reproducible with: 2022.1.0b10, 2022.2.0a7
Could not test with: 2019.4.36f1 (Articulation Body not supported), 2020.3.30f1, 2021.2.14f1 ('ArticulationBody' does not contain a definition for 'GetDriveForces')
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
- Windows Player exe contains unwanted properties, causing text "Unity Playback Engine" to appear in task bar when mousing over it
- Changes made by the Script in the UI Document are reset when performing an Undo operation after changing the GameObject with this Script
- Emissive materials are broken when loading Scene via SceneManager.LoadScene
- [URP] [Decals] ProxyLighting Decal shader doesn't work in Screen Space Technique
- "Pin in New Scene Dialog" option position migrates with "Inspector" window resizing
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a12