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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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.