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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.