Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
1
Found in
2018.3.0a4
2018.3.0b1
Issue ID
1080216
Regression
Yes
Animator resets to the default layer when changing applyRootMotion during runtime
Repro steps:
1. Open QA attached project "repro_1080216"
2. Enter Play Mode
3. Press Space on your keyboard and observe the Game View
Expected: The landing animation is played when the player lands to the ground after the jump
Actual: The landing animation is skipped
Reproducible with: 2018.3.0b5, 2019.1.0a4
Not reproducible with: 2017.4.12f1, 2018.2.12f1, 2018.3.0a3
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2019.1):
Reworked how applyRootMotion works with the Animator bindings so that we no longer need to recreate bindings when we change applyRootMotion value.