Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.3f1
Issue ID
901635
Regression
No
Animation twitches at the start of a animation loop
Steps to reproduce:
1. Download 901635_repro.zip and open "Test" scene
2. Enter play mode
3. Observe looping idle animation
Expected results: animation smoothly loops
Actual results: at the start of the loop animation twitches
Reproduced with: 2017.1.0b6, 5.6.1p1, 5.5.3p4
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 (2018.3.X):
There are many factors to consider in this specific case, and the fact that the source is a Maya file (an extra export involved) with pre-rotations on the animated joints, which something Unity does not support which forces a resample at FBX import in order to preserve existing animation properly. This means many different Maya, Maya FBX Exporters/options & Unity versions can be involved to track down the exact regression in a version that is not longer officially supported (more than 2 versions back). This combined with the fact that there are a couple possible workarounds, such as adding 1 extra key as padding before after the start/end times in Maya, (or not using pre-rotations on animated joints), are a very acceptable solutions. Fixing this issue would have a high risk of the result being different/wrong in other cases.
For all these reasons, we have no plans to address this issue in the near future.