Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.6f1
Issue ID
1080471
Regression
No
[Animation][Jobs] Simple animations with AnimationMixerPlayable generates spikes
Steps to reproduce:
1. Open attached project
2. Play the scene
3. Open profiler and observe the spikes in Animator.ProcessRootMotion and AnimationClipPlayable.EvaluateClip if on 2018.3
Expected result: Animations with AnimationMixerPlayable should not generate spikes
Reproduced in: 2018.3.0b1, 2018.2.6f1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The spikes as reported are not related to playables:
When clips loop, playback has to seek back to the start of the file, which is more expensive than normal evaluation. When all your clips are synchronized together, this causes spiking. In most use cases, all your clips will not loop on the same frame.