Search Issue Tracker

Won't Fix



Found in


Issue ID




[Android] Horizontal graphical artifacts are visible in Player when using URP RenderGraph with fullscreen blit and using Vulkan Graphics API



How to reproduce:
1. Open the user-attached “RenderGraphGraphicsJobsIssue-6000.0” project
2. Open the Build Profiles window (File → Build Profiles)
3. Switch to the Android Platform
4. Build and Run on an Android device
5. Observe the Player

Expected result: The Player is rendering without graphical artifacts
Actual result: Horizontal graphical artifacts are visible in the Player

Reproducible with: 6000.0.4f1
Couldn’t test with: 2021.3.39f1, 2022.3.31f1 (Missing Rendering-related namespace references due to downgrading)

Testing environment: Windows 11
Not reproducible on: No other environment tested

Reproducible on these devices:
VLNQA00144, Samsung Galaxy S9 (SM-G960U1), Android 10, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630

Not reproducible on these devices:
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00134, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00287, Motorola moto g(7) power (moto g(7) power), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
VLNQA00411, Samsung Galaxy Z Fold3 5G (SM-F926B), Android 11, CPU: Snapdragon 888, GPU: Adreno (TM) 660
VLNQA00517, Oneplus OnePlus 10 Pro 5G (NE2213), Android 12, CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno (TM) 730
VLNQA00520, Samsung Galaxy S22 (SM-S901U), Android 14, CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno (TM) 730
VLNQA00531, Oneplus OnePlus 11 5G (CPH2449), Android 13, CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno (TM) 740

- Reproducible only with Vulkan Graphics API
- Not reproducible with OpenGLES3
- Not reproducible on Standalone Windows even with Vulkan Graphics API

  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. As this happens on a single older device, we cannot prioritize fixing this and it may be due to a driver issue. 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.