Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
5.3.4p4
Issue ID
810165
Regression
No
Humanoid rig not animating additional prop bones correctly
Humanoid rig not animating additional prop bones correctly, but Legacy works fine
(Generic also works as expected)
When importing a Humanoid Model & Animation in separate files, resulting hierarchies are different because the "animation" files get their top node removed (single parent node), while the rig/model file keeps the top node because it's not a single parent (skeleton root + mesh root)...
in consequence, the animation is not mapped properly to prop/extra joints since the joint is not found where it's expected in the hierarchy.
see attached gif...
We should handle this case properly, as the user originally created two identical hierarchies, with the exception of an additional mesh root, which is normal/expected practice.
repro:
-import attached 810165.unitypackage into a new project
-open phoneJointScene scene
-expand/search hierarchy for...
... CMR:R_WeaponAttachMent_jnt & CMR:R_WeaponAttachMent_jnt joints
-compare rotations... identical.
-click the Editor Play, then Pause...
-compare rotations... 90' difference between the two. This is caused by the animation not being applied to this joint.
-open comparison scene
-expand both roots...
notice the difference in hierarchy...
"Biped:CMR:root_jnt" joint is not at the same level of the hierarchy.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment