Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X, 6000.3.X
Votes
0
Found in
2022.3.62f1
6000.0.50f1
6000.1.5f1
6000.2.0b3
6000.3.0a1
Issue ID
UUM-108144
Regression
Yes
Display issues in VideoPlayer when using Screen.SetResolution on certain Google Pixel devices
How to reproduce:
1. Open the attached "IN-102629" project
2. Build the project and run it on the Android platform
3. In the Android Player, alternate between “Scene A”, “Scene B” and “Scene C” by pressing the buttons at the bottom labeled after each Scene repeatedly
4. While executing step 3, also alternate between “LowResolution”, “MiddleResolution”, and “HighResolution” buttons
5. Observe “Scene A” while repeating steps 3 and 4
Expected result: VideoPlayer is not affected by screen resolution changes
Actual result: Android Player exhibits visual corruptions
Reproducible in: 2022.1.0b1, 2022.2.9f1, 2022.3.62f1, 6000.0.50f1, 6000.1.5f1, 6000.2.0b3
Not reproducible in:2021.3.0f1, 2021.3.52f1, 2022.2.8f1
Could not test with: 2021.2.19f1, 2022.1.0a16 (build errors, unable to run on affected devices)
Reproducible on:
VLNQA00627, Google Pixel 8 (Pixel 8), Android 15, CPU: Google Tensor G3, GPU: Mali-G715
Google Pixel 8a, Android 15 (reporter)
Google Pixel 6, Android 14 (reporter)
Google Pixel 7, Android 15 (reporter)
Not reproducible on:
VLNQA00175, Samsung Galaxy Note 9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00333, Nokia 7 Plus (Nokia 7 plus), Android 10, CPU: Snapdragon 660, GPU: Adreno (TM) 512
VLNQA00341, Samsung Galaxy Note20 Ultra (SM-N986B), Android 11, CPU: Exynos 990, GPU: Mali-G77
VLNQA00472, Samsung Galaxy A52 (SM-A525F), Android 12, CPU: Snapdragon 720G, GPU: Adreno 618
VLNQA00498, Google Pixel 7 (Pixel 7), Android 13, CPU: Google Tensor G2 , GPU: Mali-G710
VLNQA00566, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
Galaxy S25 (SC-51F), Android 15 (reporter)
Galaxy S10 (SM-G973N), Android 12 (reporter)
LG V60 ThinQ 5G (A001LG), Android 11 (reporter)
Notes:
* The issue might be caused by a combination of hardware + os version (specifically reproducible only on Android 14 and 15), speculated to be the case because of the reproduction inconsistencies between VLNQA00498 Google Pixel 7 and the reporters' Pixel 7.
* Could not pinpoint exact fixed/regressed version in 2021 because of build errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment