Search Issue Tracker
Fixed
Fixed in 2022.3.66f1, 6000.0.55f1, 6000.1.15f1, 6000.2.0b12, 6000.3.0a4
Votes
13
Found in
2022.3.64f1
6000.0.52f1
6000.1.11f1
6000.2.0b9
6000.3.0a1
Issue ID
UUM-111056
Regression
No
Animation playback and transitions start being erratic when state normalized time gets too large with no indication what is the problem
How to reproduce:
1. Open the “AnimationTest_250618_ETimeOn_2021.zip” project
2. Open “SampleScene“
3. Enter Play Mode
4. In the Edit > Project settings > Time, change the Time Scale to 100
5. Select the “PJPCumulative“ GameObject in the Hierarchy
6. Wait ~1 hour
7. Afterward, change the Time Scale back to 1
8. In the Animator window, change the 'Lvl' parameter to 2, and observe the Animator and the Game view and the Console
Expected result: An error, a warning, or a log is thrown in the console informing about this behavior
Actual results: The active state does not change to the corresponding state (unless 0 or 7 is put in 'Lvl' parameter), the Sprite size does not change, and the Console does not output anything
Reproducible in: 2022.1.0a1, 2022.3.64f1, 6000.0.52f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Comments (14)
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
TomekMC
Sep 25, 2025 09:26
Jumping in to add another voice. We have lots of this errors after updating Unity. I don't think it should spam the error logs like this. Can you please change it to appear once or implement the fix differently?
philc9999
Sep 24, 2025 09:59
Agree with TAOBAO, this should either be be a warning that can be switched off with animator.logWarnings = false; or only appear once, not spam the error logs. Please fix this.
electric_jesus
Aug 25, 2025 13:02
After this patch, every short non-looping animation state in my project floods the logs with warnings if I wait a while, even those animations that had never caused any issues.
Taobao
Aug 25, 2025 12:40
Adding error message spam as fix is not acceptable, it even ignores animator.logWarnings = false; flag and completely floods our projects. Please, revert this change.