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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.