Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2019.4
2019.4.26f1c1
2020.3
2021.1
2021.2
Issue ID
1336151
Regression
No
The movement speed of an Animation is inconsistent for a single frame when transitioning between Animations
How to reproduce:
1. Open the user's attached "Anim" project
2. Open the Scene "SampleScene"
3. Enter the Play Mode
4. Inspect the created GameObjects' name in the Hierarchy
Expected results: The 3rd parameter (parameters are separated by "_") are steady and similar
Actual results: On one frame the 3rd parameter (which is speed) will be significantly smaller
Reproducible with: 2019.4.27f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a17
Could not test with: 2018.4.35f1 because of the "Unexpected node type." error
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 (fix version 2022.1):
Won't fix, as fixing this would require lots of refactoring. This bug happens only when doing root motions and transitioning to a state with a transition duration really small. What would happen, is that it's impossible to evaluate the root motion if a delta time of 0.1s happened for example, but only 0.05 were spent on the previous and next state. Refactoring to give knowledge of the root motion for the previous state would cost a lot in performance for an edge case/ A warning was added to make sure that this case, the transition duration should be bigger than a deltaTime.
Workaround :
1. Use looping clips
2. Make sure that the transition duration is above a deltaTime
3. add an offset to the transition, which will start the next state at least the deltaTime.
The warning has been added in Unity 2022.1.0a6