Search Issue Tracker

Won't Fix

Votes

0

Found in

6000.0.17f1

6000.1.0a7

6000.2.0a1

6000.3.0a1

6000.4.0a1

6000.5.0a1

Issue ID

UUM-79031

Regression

No

[Android][Vulkan] Skybox flickers when using the Vulkan Graphics API on certain devices

-

Reproduction steps:
1. Open the attached “ASDQWE” project
2. Build and run the Player (File > Build And Run)
3. Wait for the Player to run for a while and observe it

Expected result: The Player runs smoothly and no visual artifacts are seen
Actual result: The skybox flickers ad hoc

Reproducible with: 6000.0.17f1
Not reproducible with: 2022.3.44f1
Could not test with: 2021.3.43f1 (The required packages are not available for this stream)

Reproducible environment: Windows 11 (user’s), MacOS Sonom 14.5 (Intel, M2)
Not reproducible environment: No other environment tested

Reproducible on:
VLNQA00499 - Google Pixel 7 (Pixel 7), CPU: Google Tensor G2, GPU: Mali-G710, OS: 15
VLNQA00500 - Google Pixel 7 (Pixel 7), CPU: Google Tensor G2, GPU: Mali-G710, OS: 14
VLNQA00498 - Google Pixel 7 (Pixel 7), CPU: Google Tensor G2, GPU: Mali-G710, OS: 13
Pixel 7, Pixel 7 Pro (user’s)

Not reproducible on:
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00372, Samsung SM-G991U (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Samsung Galaxy S22 (user’s)
MacOS Buildtime (Metal)

Could not test on:
VLNQA00175, Samsung Galaxy Note9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 6.0, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00146, Htc 10 (HTC 10), Android 8.0.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
(The application would not launch)

Workaround: Use the OpenGLES3 Graphics API

Notes:
- The issue does not appear constantly and often the application crashes
- Could not find the exact regressed version as the reproduction is not consistent and differs for tested devices

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.