Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.1f1
2022.1
2022.2
Issue ID
1385538
Regression
No
Playables API's Root Motion inconsistent with Root Motion from Animator Controller
How to reproduce:
1. Open the attached project from "Inconsistent Root Motion.zip"
2. Open Scene "SampleScene" and enter Play Mode
3. In the Inspector position X for "Playables" and "Animator Controller" from Hierarchy is different
Expected result: Position X is calculated in the same way
Actual result: Position X is different
Reproducible with: 2019.4.36f1, 2020.3.29f1, 2021.2.12f1, 2022.1.0b7, 2022.2.0a4
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
The is an expected imprecision in the root motion sampling. This is caused by single vs double float precision. The animator time is single float precision, where the director playable is double. Hence the discrepancy between the two systems.