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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
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.