Search Issue Tracker

Won't Fix

Votes

0

Found in

6000.0.41f1

6000.1.0b9

6000.2.0a6

Issue ID

UUM-100112

Regression

Yes

GameObjects that contain the MeshRenderer component are not rendered in Android Player when using URP 2D Lit/Unlit Material Shaders

-

How to reproduce:
1. Open the attached "IN-94654" project
2. Open the "SampleScene"
3. Build and run the project on the Android Platform
4. Observe the Android Player

Expected result: GameObjects are rendered regardless of if they use Sprite Renderer or Mesh Renderer component
Actual result: GameObjects that use the Mesh Renderer component disappear

Reproducible in: 6000.0.0b12, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Not reproducible in: 2022.3.59f1
Could not test with: 2023.1.0a1, 6000.0.0b11 (Build finishes but the Player window is not viewable on the affected device)

Reproducible on:
VLNQA00285, Samsung Galaxy J4 Core (Galaxy J4 Core), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno 308
LG K22, Android 10, CPU: Snapdragon 215, GPU: Adreno 308 (reporter)

Not reproducible on:
VLNQA00566, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00333, Nokia 7 Plus (Nokia 7 plus), Android 10, CPU: Snapdragon 660, GPU: Adreno (TM) 512
VLNQA00294, OPPO Reno Z (PCDM10), Android 11, CPU: Mediatek MT6779 Helio P90, GPU: PowerVR Rogue GM9446
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00498, Google Pixel 7 (Pixel 7), Android 13, CPU: Google Tensor G2 , GPU: Mali-G710

Notes:

* Reproducible using Vulkan and OpenGLES3 Graphics APIs
* On OPPO Reno Z, the lighting inside the project does not function as expected, the intensity of the light seems to set to its maximum. This is speculated to be due to an unrelated issue and does not impact reproduction.
* Could not pinpoint regression point because of project corruptions inside the Player when downgraded to 6000.0.b11 and below

  1. Resolution Note:

    Hi,

    Thank you for bringing this to our attention and for your patience while we investigated.

    After extensive testing we’ve found that the issue only occurs on a very narrow hardware stack — specifically Android phones with an Adreno 308 GPU. Unfortunately, this is not a very common GPU, so our engineers don’t have access to it in-house. The fact that it doesn't reproduce on other devices we've tested suggests a defect in the hardware or driver rather than in Unity code.

    Because

    the problem is confined to a single, low-volume hardware setup, and

    a true fix would likely require changes from the GPU-vendor’s driver team,

    we’re unable to address this on our side and will be closing the ticket.

    I understand this isn’t the resolution you were hoping for, and I’m sorry for the inconvenience. If you manage to reproduce this on a device with a different GPU, feel free to reopen the ticket.

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.