Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
1
Found in
2018.4.0f1
2018.4.2f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1184690
Regression
Yes
Animator.Update CPU time spikes when multiple animations are playing
Steps to reproduce:
1. Download AnimationTest.zip and open "Character with animation" scene
2. Enter play mode with open Profiler
3. Wait for 10 - 30 seconds
Actual results: Notice that Animators.Update spikes. On i7-6700k in the example project Animator.Update takes -2.5ms to calculate and when it spikes it takes 5-7ms to calculate.
Reproduced with: 2020.1.0a4, 2019.3.0b4, 2019.2.6f1, 2018.4.9f1
Not reproducible with: 2017.4.32f1
Note:
- Tested and reproduced in Standalone player
Comments (15)
- 
        
Lydwen
Mar 16, 2020 16:08
This issue is still not fixed in 2018.4.19 LTS.
Can we have an ETA or some news about it please? - 
        
yanivng
Feb 29, 2020 12:48
Still listed as a known issue for 2018.4.18f1. Can someone please let us know when it will be ready for 2018.4 LTS?
 - 
        
imaginationrabbit
Feb 11, 2020 21:14
It's still listed as a known issue in 2018.4.1.17f1 https://i.imgur.com/Eb7KWhs.png
 - 
        
Shadowing
Feb 11, 2020 16:45
It was fixed in todays updates on version 2018.4.17f1
 - 
        
yanivng
Feb 11, 2020 07:58
For which 2018.4 LTS version is this fix planned?
 
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
- Video does not play in macOS build when built app is placed in a path with a space in it on a specific project
 - Crash on AuxWindowManager::OnGotFocus when trying to maximize a tab while Visual Effect Graph window is open
 - “NullReferenceException: Object reference not set to an instance of an object” error is thrown when
 - [Metal] Game freezes after command buffer Timeout error
 - Addressables Report window UI is broken when opening via Build > New Build > Default Build Script
 
Resolution Note (fix version 2019.3):
2019.3.1f1
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.27f1