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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
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.