Search Issue Tracker
Fixed in 2020.3.43f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0a13
Votes
0
Found in
2020.3.39f1
2021.3.10f1
2022.2.0b8
2023.1.0a11
Issue ID
UUM-15543
Regression
No
Video is displayed with one frame delay when videoPlayer.Play() is called
Copied from original fogbugz item 1376068:
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2023.1):
Reworked order of execution of the various phases of the video playback.