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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.