Search Issue Tracker
Fixed
Fixed in 2020.3.42f1, 2021.3.12f1, 2022.1.21f1
Votes
0
Found in
2020.3.2f1
2021.3.0f1
Issue ID
UUM-1805
Regression
No
[Backport] Data indices don't match when using ArticulationBody GetDriveTargets and GetJointPositions
How to reproduce:
1. Open the user's attached project
2. Open scene Scene_AB_Test
3. Press the Play button
4. In the Hierarchy window, select the GameObject "Viking_AB2"
5. In the Inspector window, observe the values under the "Test_AB Get Dof Start Indices (Script)" component
Expected result: Changing each index of the Targets list should be reflected in the Positions list on the same index that was changed
Actual result: After some amount of indexes, the indexes stop matching and wrong data is returned
Reproducible with: 2020.3.31f1, 2021.2.16f1, 2022.1.0b12, 2022.2.0a8
Not reproducible with: 2019.4.36f1 (Articulation Body not supported)
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2022.1.21f1):
Fixed in: 2022.1.21f1
Resolution Note (fix version 2021.3.12f1):
Fixed in: 2021.3.12f1
Resolution Note (fix version 2020.3.42f1):
Fixed in: 2020.3.42f1