Search Issue Tracker
Fixed in 2020.1
Fixed in 2019.2, 2019.3
Votes
7
Found in
2019.2.10f1
2020.1.0a2
Issue ID
1183581
Regression
Yes
[Animation Stream] binding AnimationStream handles on a nested Animator hierarchy triggers an exception
[Animation Stream] binding AnimationStream handles on a nested Animator hierarchy triggers an exception.
Repro:
1- Open scene '2BoneIK' in attached project.
2- Go in playmode.
Notice the following error in the console.
"Transform 'root' must be the top most parent, found 'main'."
If the 'root' game object containing the Animator is indeed the top most parent in the hierarchy, everything works fine.
This prevents from having nested animated hierarchies which is something that works without using the Animation Stream.
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
- Object references are not loaded after you git checkout to another branch
- Only one of multiple copies of the same StateMachineBehaviour script is visible when added to the Animation state
- [XR][Vulkan][Oculus] Crash in hybrid renderer BeginRenderPass
- [Mobile]Dynamic batching is not working when working with sub mesh on a mobile device
- [Hub] Warning pop-up contains <strong></strong> when attempting to add a project to the list of projects while it's already open
Victor-Guerrero
Jan 23, 2020 08:04
Fixed in 2019.2.19f1. Thanks!
nimravid
Nov 19, 2019 02:31
This bug has forced us to freeze all Unity development on 2019.2.9 otherwise all our existing animations break. This is a very high-priority issue for our company.
ibernd
Oct 25, 2019 06:21
Bug exists already in 2019.2.10
Makes the animation rigging package unusable if you have nested animator.