Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.17f1
2021.2
2022.1
Issue ID
1369255
Regression
No
Animation is delayed when transitioning between States
How to reproduce:
1. Open the attached project (LegacyAnimationTest.zip)
2. Open scene Scenes/SampleScene
3. Press the Play button and go to the Game view
4. Click anywhere into the Game view and observe the upward Animation until it has been completed
5. Click anywhere into the Game view and observe the downward Animation
Expected result: the downward Animation starts immediately after the click, simultaneously with the changing of the color
Actual result: the downward Animation starts delayed and is not simultaneous with the changing of the color
Reproducible with: 2019.4.32f1, 2020.3.22f1, 2021.1.28f1, 2021.2.2f1, 2022.1.0a14
Notes: when the simultaneous "Make red" Animation is not triggered by code, the "Move down" Animation sometimes starts immediately, but not always
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 dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
- The build size is larger when Models have Animation Type set to Generic
- Error "ArgumentException: Both 'ok' and 'cancel' strings are null or empty" logged when User is trying to create circular dependencies in UI Builder Hierarchy
- "SupportsRandomWriteOnRenderTextureFormat()" shows "False" when executed on 2023.2 and 6000.0 streams
Resolution Note:
State machine states will continue to tick an internal timer even when a non-looping animation is held at its final frame. This means inside the state it is still ticking and the 'exit time' condition is looping. The reason we see the delay in this case is that the transition in the test project is only possible to occur every 1 second, so usually when the user clicks there will be some random time delay between 0 and 1 second before the transition will occur.
I managed to adjust the data in the test project to make this case work without delay by adding an additional state at the upper position which holds the cube at the top.
It's unfortunate that we don't have debug to show the internal state timer, which could help understand this. We will take this into consideration for future development.