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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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.