Search Issue Tracker
Fixed in 2022.2.X
Duplicate in 2021.3.X
Votes
1
Found in
2021.2.0a7
2021.2.19f1
2021.3
2022.1
2022.2
Issue ID
1428866
Regression
Yes
Performance cost of looping animations increases over time
Steps to reproduce:
1. Open the attached "InflatingAnimationCostBugReport.zip" project
2. Open SampleScene in Assets > Scenes
3. In the Toolbar select Window > Analysis > Profiler
4. In the Profiler window set Play mode as Target Selection
5. In the Profiler window press Record
6. Enter Play Mode
7. In the Profiler window observe the Animation category of the CPU Usage Profiler module for at least a minute
Expected result: time spent on animation processes remains roughly the same
Actual result: time spent on animation processes increases continuously
Reproducible with: 2021.2.0a7, 2021.3.3f1, 2022.1.1f1, 2022.2.0a15
Not reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.2.0a6
Notes:
- The shorter the animation clip, the faster the performance cost increases
- Turning off Loop Time in the Animation tab of the Idle_Pose.fbx clip prevents this issue
- Anything that resets state time, such as jumping to or transitioning to any other state temporarily staves off the issue
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.2):
Matrix exponentiation methods for root motion extraction has been rewrite to avoid O(n3)