Search Issue Tracker
Fixed
Fixed in 2022.3.26f1, 2023.2.20f1, 6000.0.0b14
Votes
1
Found in
2022.3.21f1
2023.2.13f1
6000.0.0b11
Issue ID
UUM-66728
Regression
Yes
The Video Player does not play the video after seeking back to frame 0 when Loop and Skip On Drop are enabled and the video has looped once
Reproduction steps:
1. Open the attached "ReproProj" project
2. Open "Assets/Scenes/SampleScene" scene
3. Enter the Play mode
4. Wait for the video to loop once
5. Press the middle button to rewind the video and then the bottom button to play the video again
6. Observe the results
Expected results: The video does not play
Actual results: The video plays
Reproducible with: 2022.3.16f1, 2022.3.21f1, 2023.2.5f1, 2023.2.13f1, 2023.3.0a14, 6000.0.0b11
Not reproducible with: 2021.3.36f1, 2022.3.15f1, 2023.2.4f1, 2023.3.0a13
Reproducible on: Windows 11 Pro, MacOS 12.7.3 (user's)
Not reproducible on: No other environments tested
Notes:
- Reproducible in Editor and Standalone Player
- Does not reproduce if Loop or Skip On Drop is disabled in the Video Player
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
- Nested Canvases with the same Order in Layer ignore Z position for render order when sharing parent Canvas
- ShaderGraph Material subasset loses texture reference when reimporting all assets while using a scripted importer
- Values changed on a prefab are not retained when entering Play Mode
- Shadow Caster 2D shadows partially disappear in specific spots when used with Composite Collider 2D in the Game view
- Hierarchy and Library parts in UI Builder are inaccessible when UI Builder window is resized and these elements no longer fit in the window
Resolution Note (fix version 6000.0.0b14):
The VideoPlayer manages an internal presentation time offset which compensates for monotonic increase of current time when looping. But when seeking, this offset needs to be reset because accumulated time increases due to looping is also reset. Not having this reset caused the VideoPlayer to wait indefinitely for frames with timestamps too far in the future.