Search Issue Tracker
Active
Under Consideration for 2022.3.X
Votes
1
Found in
2022.3.50f1
Issue ID
UUM-84460
Regression
Yes
[Android] Artifacts appear when instantiating a prefab on a PowerVR Rogue GPU device
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Build and run the Player (File > Build And Run)
3. Inside the Player, press the “Button” button
4. Observe the Player
Expected result: A big white square appears in the middle of the screen
Actual result: A big white square does not appear and the environment appears inverted, and when rotating the device visual artifact blocks appear
Reproducible with: 2022.3.43f1, 2022.3.50f1
Not reproducible with: 2021.3.44f1, 2022.3.42f1, 2023.1.0b10, 6000.0.23f1
Could not test with: 2023.1.0a1 - 2023.1.0b9 (various compilation or asset migration issues)
Reproducible environment: MacOS 14.6.1 (Intel), 14.3 (M1 (user’s))
Not reproducible environment: No other environment tested
Reproducible on:
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 6.0, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
Samsung Galaxy A03s, GPU: PowerVR GE8320
Not reproducible on:
VLNQA00175, Samsung Galaxy Note9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00146, Htc 10 (HTC 10), Android 8.0.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00372, Samsung SM-G991U (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Pixel 5, GPU: Adreno 620
MacOS Buildtime, Runtime
Notes:
- The Player freezes on the Samsung Galaxy A03s device
- With 2022.3.50f1 and Htc One M9+, the environment appears gray and the visual artifacts are only visible during the rotation
- Reproducible with:
both Release and Development type builds
both graphics APIs
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment