Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
2
Found in
2019.2.10f1
2019.3.0f1
Issue ID
1201991
Regression
Yes
[Animation Stream] binding AnimationStream handles on a nested "Humanoid" Animator hierarchy does not work
This issue now only occurs with Humanoid characters. Same issue on generic hierarchy was addressed with bug#1183581
As soon as you "parent" the Animator (with Humanoid Avatar) child of another GO in the scene, the is no runtime evaluation of the Animation Rigging constraint(s) and erros are generated in the console...
> Transform 'DefaultMale' not found in HumanDescription.
> System.InvalidOperationException: The TransformStreamHandle cannot be resolved.
Repro:
1- Open scene 'Humanoid' in attached project.
2- Go in playmode.
Bug: no runtime evaluation of constraint and errors are generated in the console
If the 'DefaultMale' 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.
Comments (4)
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
mostafa3dblender
Nov 17, 2020 23:05
hi
i dont know what is my problem i do as toturials say but animation rigging not work for me same as those tutorials showing
and also for characters i make not working good at all
they flying in space when i active new rig and still i dont know why
ibernd
Dec 26, 2019 09:38
fixed in 2020.1.0a17
nimravid
Dec 19, 2019 20:11
This bug still exists in Unity 2019.3.0f3 which is the latest 2019.3 release.
NOTE: It is highly frustrating when an issue (this one or any other issue) is flagged as fixed in a particular release when that fix is not available for us to download. Can you guys please post the actual fix release number for these issues so that we can plan around the expected release date.
AriaTLowMood
Dec 02, 2019 17:26
JUST leave IT ALONE!!