Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.2.5f1
Issue ID
1096091
Regression
No
[Android][VideoPlayer] First frame is skipped after resetting VideoPlayer's time value to 0
Repro steps:
1. Open user attached project
2. Build and Run on Android
3. Press the ">" button until you get to "TU 411"
4. "Download Video" -> "Prepare Video"
5. Memorize the first frame
6. "Play" and after a few frames "Pause"
7. "Replay"
8. ">"
Expected: After pressing the ">" button the first frame is seen
Actual: After pressing the ">" button the second frame is seen, going back with "<" doesn't show the first frame
Reproducible with: 2017.4.15f1, 2018.2.16f1, 2018.3.0b9, 2019.1.0a8
DUT:
Reproduced on:
VLNQA00155, Meizu PRO 7 Plus (PRO 7 Plus), Android 7.0, CPU: MediaTek Helio X30 MT6799, GPU: PowerVR Rogue Marlowe
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 5.0.2, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00001, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00039, Htc One mini 2 (HTC One mini 2), Android 4.4.2, CPU: Snapdragon 400 MSM8226, GPU: Adreno (TM) 305
VLNQA00028, Samsung Galaxy Note4 (SM-N910F), Android 6.0.1, CPU: Snapdragon 805 APQ8084, GPU: Adreno (TM) 420
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2019.3.X):
This appears to work in Unity 2019.3. Several bug fixes for the Android video player have gone in since this bug was originally filed and I'm guessing that one of those must have also fixed this bug.