Search Issue Tracker
Fixed in 2022.2.X
Duplicate in 2020.3.X
Votes
0
Found in
2020.3
2021.2
2021.2.2f1
2022.1
2022.2
Issue ID
1386970
Regression
No
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
- Crashes in the wild on Vulkan in CreateDepthSurfaceImpl
- Position and rotation of a GameObject with Rigidbody reset when it is enabled and moved in the same Update call and the frame rate is low
- “Ignoring depth surface store action as it is memoryless” warnings thrown when Capturing new Snapshot while in Play Mode
- Certain textures are not loaded when using the "Load texture data on demand" feature
- [Android][OpenGL] The 2DLight is disproportionately bright on some Android devices when OpenGLES3 is used
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a12