Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.1.0f2
Issue ID
1038127
Regression
No
Root is not moving together with player animation when root motion is applied on additive layer
How to reproduce:
1. Open the attached "1038127_repro.zip" project
2. Open the "Main" scene
3. Select "Loli" GameObject from the Hierarchy
4. In the Animator Window, observe that it has two Animation Layers ("New Layer" on top with Blending type "Override" and "Base layer" with "Additive" blending)
5. Enter the Play mode
6. Move the player around
Expected result: The "Loli" root is moving along with the animation.
Actual result: The "Loli" root is not moving along with the animation.
Reproducible with - 2018.1.5f1, 2018.2.0b9, 2018.3.0a2
Note: Could not be tested on versions prior to 2018.1 due to "Loli" prefab not working on those versions. ("Unable to instantiate prefab. Prefab may be broken." warning)
Update: This issue has been resolved as won't fix. Ignoring root motion in additive layers when mixing layers is a design choice in the original implementation of the state machine additive layers. Changing this behavior would potentially invalidate existing projects. If you intend on using additive layers with a character using root motion, it is advised to move root motion information to the base layer or to an override layer instead.
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
- Standalone profiler process is hidden in macOS dock
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
- The Player hangs when activating another maximized application
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
CaseyHofland
Mar 01, 2023 10:16
I agree with Shinali, I can only hope the new animation system will be better
ShinAli
Feb 04, 2022 22:08
Not sure why would this be a "won't fix" when you can setup a default behaviour to not apply root motion on additive layers and exposing the option.
This was needed for a controller I was working on and had to re-do it to a much more complicated machine because of this limitation. Please reconsider.