Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
1
Found in
2019.4
2019.4.2f1
2020.2
Issue ID
1271421
Regression
No
[Mac] Video player jumps to keyframe when calling Play() if paused before a keyframe
Reproduction steps:
1. Open user's attached project and scene "SampleScene"
2. In Game View, enable Maximize On Play and enter Play Mode
3. Press "Seek near keyframe"
4. Observe frame number
5. Press "Play"
6. Observe frame number
Expected result: The video continues to play without skipping any frames
Actual result: The video skips to frame 300
Reproducible with: 2019.4.9f1, 2020.1.3f1, 2020.2.0a21
Could not test with: 2018.4.26f1 (console errors break project)
Note: On Windows, when the buttons are pressed, the frames do not match. When manually set to match, the issue still does not reproduce.
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
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a4. There was logic to tolerate a .5s skip-ahead when rate is changing. But when the original rate is 0 (meaning playback is paused), this skip-ahead should not happen.
Resolution Note (fix version 2020.2):
There was logic to tolerate a .5s skip-ahead when rate is changing. But when the original rate is 0 (meaning playback is paused), this skip-ahead should not happen.
Resolution Note (fix version 2020.1):
Fixed in 2020.1.13f1. There was logic to tolerate a .5s skip-ahead when rate is changing. But when the original rate is 0 (meaning playback is paused), this skip-ahead should not happen.
Resolution Note (fix version 2019.4):
There was logic to tolerate a .5s skip-ahead when rate is changing. But when the original rate is 0 (meaning playback is paused), this skip-ahead should not happen.