Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a4
2018.3.0b3
Issue ID
1086070
Regression
Yes
ApplyBuiltinRootMotion() does not evaluate when being manually called in a script overriding Root Motion
How to reproduce:
1. Open the user's attached project
2. In the hierarchy open Scenes/SampleScene
3. Enter Play Mode
Expected result: ApplyBultinRootMotion() method evaluates (Dummy with Rootmotion script moves)
Actual result: ApplyBuiltinRootMotion() does not evaluate (Dummy with Rootmotion script does not move)
Reproducible on 2018.3.0a4, 2018.3.0b5, 2019.1.0a4
Not reproducible on 2017.4.12f1, 2018.1.9f2, 2018.2.11f1, 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
- Lights with Cookies generate Cookie Atlas and increase Memory usage every time when Play mode is entered
- Crash on mono_traverse_object_internal when exiting Play mode on a specific project
- Camera prefab shows up in overrides after upgrade when game view is changed to Simulator
- Prefab Override context menu does not appear when changing attributes on a Terrain Component
- Particles are visible through Mesh when Sprite-Lit-Default Material is used
Resolution Note (fix version 2019.1):
Ended up testing for script overrides as a condition for root motion to be enabled. We reworked how applyRootMotion is applied and it no longer needs to rebuild bindings.