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')
-
IngemarSkelanderHiab
Nov 03, 2022 11:37
I'm not sure if this is the correct place to write this, but I can reproduce this issue in Beta 13.
I have a demo project where the problem can be seen, if it would help.
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
- SHADERPASS has incorrect value when using Shader Graph for Built-In target
- [VFX] Gizmo still incorrectly rendered for a hidden property
- Nested object label indentation is incorrect when using the UI Toolkit Inspector
- Crash on tlsf_free when UI Elements are moved to the side by scrolling
- Setting VideoPlayer.time and pausing results in incorrect player.frame values
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a12