Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0.3
Issue ID
1319150
Regression
No
"Could not resolve <...>, because it is not a child Transform in the Animator hierarchy" warnings after animations play
Reproduction steps:
1. Open attached user project and scene "SampleScene"
2. Enter Play Mode
3. Wait until the animations are finished and observe Console window
Expected result: No warnings
Actual result: "Could not resolve <...> because it is not a child Transform in the Animator hierarchy" warnings
Reproducible with: 1.0.3 (2020.3.0f1, 2021.1.0b11, 2021.2.0a8)
Could not test with: 2018.4.32f1, 2019.4.22f1 (AnimationRigging RigLayer functionality missing)
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note:
This is the expected behaviour. You cannot add transform at runtime once the animator component is already binded.
All the transforms needed by rigging constraint must exist on the game object hierarchy to get binding information before the animator get his first OnEnable call.
Create your rigging transforms on your unity chan model in the editor rather than adding them at runtime.