Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a1
2018.4.0f1
2019.2.0a1
2019.2.6f1
2019.3.0a1
2020.1.0a1
Issue ID
1187247
Regression
Yes
Debug.Log(p.frame) returns incorrect frame value after seeking to a frame
To reproduce:
1. Open attached project "SeekCompleted.zip"
2. Open "SampleScene.unity" scene
3. Enter Play mode
4. Press "Seek to frame 163" and observe in the console as Debug.Log("Seeked to frame #: " + p.frame); returns a random frame value
Expected: Debug.Log("Seeked to frame #: " + p.frame); returns the frame value that you seek to
Actual: Debug.Log("Seeked to frame #: " + p.frame); returns a random frame value
Reproduced on:
2018.3.0a1 2018.4.0f1 2019.2.7f2 2019.3.0b5 2020.1.0a7
Regression introduced in:
2019.3.0a1
Doesn't reproduce on:
2017.4.32f1 2018.2.21f1
Notes:
- On 2019.3.0a1 Debug.Log("Seeked to frame #: " + p.frame); only returns -1 value
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
- Bunch of "TargetParameterCountException" errors thrown in the Editor Console when opening the "Adaptive Probe Volumes" tab in the "Lighting" window
- Non-removable serialized data for a renderer feature still appears even when the renderer feature is deleted
- URP Cascaded Shadows do not have a falloff in Player when the Player is built not in Development Mode
- Grid in animation preview window is rendered on top of the object
- WebGPU Graphics.RenderPrimitives fails on MeshTopology.Quads with Validation errors when exceeding 64k vertices
Resolution Note:
VideoPlayer.time and VideoPlayer.frame now update only when a new frame appears. For continuous time updates (between frames, or after seek but before the new frame has been displayed), VideoPlayer.clockTime can be used.