Search Issue Tracker
By Design
Votes
1
Found in
2019.1.0b1
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1154168
Regression
No
Inserting transforms between the Gameobject having the Animator component and the root of the skeleton causes resolve errors
How to reproduce:
1. Open the attached project ("case_115416.zip") and open the "handle_error" scene
2. Enter Play Mode and observe that the animation is working properly
3. Create two new game objects, parent them to one another and then parent them to the "DefaultMale_Generic" object
4. Drag the "Body" and "Skeleton" objects to the child newly created object
5. Try to enter play mode again and observe the console
Expected result: the animation is played without issues
Actual result: the animation isn't played and "InvalidOperationException: The TransformStreamHandle cannot be resolved" errors are continuously thrown
Reproduced in: 2019.3.0a3, 2019.2.0b2, 2019.1.3f1, 2019.1.0b1
Couldn't test with: 2019.1.0a15, 2018.4.0f1, 2017.4.27f1 (Couldn't enter play mode due to multiple errors/version conflicts)
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
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
- Graph and Camera options for Render Graph Viewer disappear after maximising the window
Resolution Note (2019.3.X):
These errors are normal behavior.
Since the character hierarchy underneath the animator root has changed, the predefined Avatar "DefaultMale_GenericAvatar" is no longer valid and a new Avatar needs to be created. This can be done using the little cog icon on the animator component or by leaving the avatar field blank. This will prevent having invalid TransformStreamHandle errors altogether.
While this will fix the immediate issue, the next thing that will need to be updated are the clip bindings used in the SimpleMixer script since the paths will also be invalid for this new hierarchy. These can be changed via the AnimationWindow but batching the operation via a script would be best. In this case, AnimationUtility.[Get/Set]CurveBindings functions will be useful.