Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a1
2018.3.0f1
2019.1.0a1
2019.2.0a1
Issue ID
1120441
Regression
No
VideoPlayer.time gets stuck and cannot be changed when increasing it multiple times a second
How to reproduce:
1. Open attached project "Piano.zip"
2. Enter Play mode
3. In Game View, press "STOP!" panel/button
4. In Game View, press "+1" panel/button 10 times fast (the press amount does not need to be 10)
5. Observe Console window
Expected result: every time the "+1" button is pressed videoPlayer.time changes
Actual result: after a few "+1" button presses videoPlayer.time cannot be assigned
Reproducible with: 2018.3.5f1, 2019.2.0a4
Could not test with: 2017.4 due to VideoPlayer.lenght being not present
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note:
When changing VideoPlayer.time, this triggers an asychronous seek. You must wait for this seek to finish before you can again read and set the time value with deterministic behaviour. You can use the seekCompleted event to detect this.