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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
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.