Search Issue Tracker
Fixed in 2023.1.X
Votes
0
Found in
2019.4
2020.3
2021.1.19f1
2021.2
2022.1
2022.2
Issue ID
1376068
Regression
No
Video is displayed with one frame delay when videoPlayer.Play() is called
Reproduction steps:
1. Open the attached "1376068.zip" project
2. Open the "1_Frame_Delay" Scene
3. Enter the Play mode
4. Record the display in at least 60 fps
5. Press the "Play" button in the Game view
6. Stop the recording
7. Slow down the recording and observe the "Frame Count:" and "Play() called at:" values in the Game view
Expected result: The video appears at the same frame when the "Play" button is pressed
Actual result: The video appears one frame later after the "Play" button is pressed
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a4
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note (fix version 2023.1):
Fixed in 2023.1.0a13
Reworked the video module's player loop integration so it behaves more similarly in editor to how it does in builds. Also now triggering a texture update in PostLateUpdate if a call to VideoPlayer.Play/Pause/StepForward that causes a new frame to become available was made during the iteration. This way instant-start can be achieved rather than having to wait one frame.