Search Issue Tracker
By Design
Votes
2
Found in
2019.3
2019.3.12f1
2020.1
2020.2
Issue ID
1248714
Regression
No
[Android][Vulkan] Video stutters and stops completely after a few frames
Repro steps:
1. Open either of the attached projects
2. Make sure a video clip is assigned on the Plane GameObject's Video Player component
3. Build and Run on Android
Actual: Video stutters and stops after a few frames
Tested and reproduced on these devices:
VLNQA00294, Oppo Reno Z 中国版 (PCDM10), Android 9, CPU: Mediatek MT6779 Helio P90, GPU: PowerVR Rogue GM9446
N/A, Xiaomi Mi A3 (Mi A3), Android 9, CPU: NOT FOUND, GPU: Adreno (TM) 610
Oculus (Quest), Android 7.1.1, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Didn't reproduce on:
VLNQA00317, Vivo V1924A (V1924A), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00001, Google Pixel 2 (Pixel 2), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00225, Qualcomm (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00128, Samsung Galaxy Note8 (SM-N950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00229, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (2020.2.X):
super high-resolution videos like this one are going to be slower on Vulkan because we have to decode-to-memory, then copy the video data up to video memory. With GLES, we can decode more directly to video memory via GLES extensions that may still not be widely available on Vulkan (even if we implement support for this path).
Since Vulkan is still experimental on the Quest / Quest 2, I would recommend using GLES for now. This will also give the user better performance on super high-res video playback. The the videos just need to be trans-coded to H.264 or to a lower-resolution to reach the intended performance target.