Search Issue Tracker
By Design
By Design in 1.2.X
Votes
0
Found in [Package]
1.1.1
1.2.0
Issue ID
ARB-16
Regression
No
The model does not follow the aim when Rig is enabled
To reproduce:
1. Open the project “Test”
2. Enter Play mode
3. Toggle “Enable Rig” on
4. Move the Slider to any extremum
Expected result: The model follows the sphere (aim) always when Rig is enabled
Actual result: The model follows the sphere (aim) only when the Slider is in the middle
Reproducible with: 1.1.1 (2020.3.37f1, 2021.3.6f1, 2022.1.10f1), 1.2.0 (2022.2.0b1, 2023.1.0a2)
Reproduced on: macOS Monterey 12.4 (Intel)
Notes:
- Doubled negative rotation of the root animation rotation is added when using 2 or more rotation-kind constraints
- The sphere object (aim) is at Model → Rig 1 → aim
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
After investigating this issue, we have found out that the aim constraint is evaluated before a rotation constraint. When evaluated, the rotation constraint will move the torso causing the aim to change.
To fix this, just reorder the aim constraint and the rotation constraint in the game object hierarchy. Refer to this section in the documentation for more details:
https://docs.unity3d.com/Packages/com.unity.animation.rigging@1.2/manual/RiggingWorkflow.html#rig-component
Resolution Note (1.2.X):
After investigating this issue, we have found out that the aim constraint is evaluated before a rotation constraint. When evaluated, the rotation constraint will move the torso causing the aim to change.
To fix this, just reorder the aim constraint and the rotation constraint in the game object hierarchy. Refer to this section in the documentation for more details:
https://docs.unity3d.com/Packages/com.unity.animation.rigging@1.2/manual/RiggingWorkflow.html#rig-component