Search Issue Tracker
Fix In Review for 1.3.0
Votes
13
Found in [Package]
1.1.1
Issue ID
1373387
Regression
No
Animation Rigging fails when GameObjects with Skinned Meshes are not direct children of the Animator
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. In the Hierarchy window, select the GameObject "Modular Character (Doesn't Work)"
4. At the top of the Inspector view, disable the GameObject by unchecking the box next to its name
5. Press the Play button and observe the Console
6. Select "Modular Character (Doesn't Work)" again in the Hierarchy view and re-enable it in the Inspector view
7. Observe the Console
Expected result: no errors or warnings are thrown to the Console
Actual result: an error and several warnings are thrown to the Console (System.InvalidOperationException: The TransformStreamHandle cannot be resolved <...>)
Reproducible with: 1.0.3, 1.1.1 (2020.3.21f1, 2021.1.26f1, 2021.2.0b16, 2022.1.0a12)
Could not test with: 2019.4.31f1 (project breaks after downgrading)
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
- EditorGUILayout.PropertyField foldout icon inside Vertical Layout Group has an incorrect indent when used with OnInspectorGUI()
- [Android] [iOS] "NullReferenceException: Object reference not set to an instance of an object" throws when entering the Play Mode/opening the application
- The Player freezes on load when building Web platform
- Animator "Conditions" tab breaks when the only Parameter is deleted and another one is created
- "Shader error in 'Universal Render Pipeline/Lit': maximum ps_5_0 sampler register index (16) exceeded" error thrown after a build is completed when the "LOD Cross Fade" parameter is enabled
Resolution Note (fix version 1.3.0):
Transforms that were children in the Animator hierarchy, but not necessarily nested under the avatar root game object were not handled properly in Animation Rigging.