Search Issue Tracker
Fixed in 2021.2.X
Votes
5
Found in
2017.4
2018.3
2018.4
2019.2
2019.2.0f1
2019.3
2020.1
Issue ID
1196250
Regression
No
[Playables] The first frame of the Animation Playable is delayed when entering Play Mode causing a delay by one frame
How to reproduce it:
1. Open the project "animationProject"
2. Open the scene "SampleScene"
3. Press the Pause button
4. Press the Play button
5. Press the Step button a few times
6. Observe the first lines in the Console window
Expected result: after the first execution of Update method the local time of the Playable changes
Actual result: after the first execution of Update method the local time of the Playable is the same
Reproducible with: 2017.4.33f1, 2018.3.14f1, 2018.4.12f1, 2019.2.12f1, 2019.3.0b10, 2020.1.0a12
Note: it is not reproducible in versions between 2017.4.0f1 and 2018.2.0b7 when entering the Play Mode without pausing it at first
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
- Flickering orbs appear when using RenderTargetHandle
- UsePass for ShaderLabShader is ignored and GameObjects are not rendered when SRPBatcher is enabled
- Animated model translated down when interrupting a transition
- UI Toolkit text splits when changing PanelSettings scale
- Error "NullReferenceException" is thrown when selecting folders from the folder panel or closing the folder panel with EditorUtility.OpenFolderPanel() in use
Resolution Note (fix version 2021.2):
As we update the time of the playables in the PreLateUpdate method callback, it is normal to always have a difference of time of one frame between the Update and LateUpdate methods (see : https://docs.unity3d.com/Manual/ExecutionOrder.html).
The documentation was updated for the SetTime and GetTime of playables