Search Issue Tracker
By Design
Votes
2
Found in
2021.3.38f1
2022.3.30f1
6000.0.3f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-72690
Regression
No
[GLES] The material isn't rendered when using Graphics.RenderPrimitives
Steps to reproduce:
1. Open the attached “RenderPrimitivesTest” project
2. Build And Run the project on the device
3. Observe the devices screen
Expected result: The material is rendered
Actual result: The material isn’t rendered
Reproducible with: 2021.3.38f1, 2022.3.30f1, 6000.0.3f1
Testing environment: macOS Sonoma 14.4.1 (Intel), Windows 10 (by user)
Not reproducible on: No other environment tested
Reproducible with these devices:
VLNQA00567 - Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4, OS: 9
VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 14
VLNQA00231 - HUAWEI Mate 20 Pro (LYA-L29), CPU: HiSilicon Kirin 980, GPU: Mali-G76, OS: 9.0.0
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: Exynos 9 (9820), GPU: Mali-G76
Not reproducible with devices:
VLNQA00344 - Note20 Ultra 5G USA (SM-N986W), CPU: Snapdragon 865 SM8250, GPU: Adreno 650, OS: 11
VLNQA00472 - samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11
Note: Isn’t reproducible with Vulkan, but reproducible with OpenGLES3
Comments (1)
-
XMAKE_DTF
Jun 17, 2024 11:18
Also Graphics.DrawMeshInstancedIndirect and Graphics.RenderMeshIndirect doesn`t work as expected on specified hardware. Seems like an issue with buffers in shaders.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
- Solid gray or black areas are present when using ShaderGraph with Custom Function nodes without manual reimport
- The Multiplayer Play mode tool doesn't see the list of Play Mode scenarios when using 6000.3.x
- Input field does not update when selecting the same input field after previous input was canceled
- No warning thrown when modifying array size while editing multiple objects
Resolution Note:
Thank you for reporting a bug to Unity.
After investigation, we’ve confirmed the behavior is in line with current design and hardware limits. The custom vertex shader uses `StructuredBuffer` (compute buffers), which require vertex‑stage buffer support. On the affected Mali OpenGLES3 devices, `SystemInfo.maxComputeBufferInputsVertex` returns 0, meaning vertex compute buffers are not supported, so the shader cannot link and the material is not rendered. Projects should check this capability before using such shaders on GLES.
We will close this case as 'As Designed.' 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 of this issue.
Resolution Note:
Thank you for reporting a bug to Unity.
After investigation, we’ve confirmed the behavior is in line with current design and hardware limits. The custom vertex shader uses `StructuredBuffer` (compute buffers), which require vertex‑stage buffer support. On the affected Mali OpenGLES3 devices, `SystemInfo.maxComputeBufferInputsVertex` returns 0, meaning vertex compute buffers are not supported, so the shader cannot link and the material is not rendered. Projects should check this capability before using such shaders on GLES.
We will close this case as 'As Designed.' 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 of this issue.
Resolution Note:
Postponing U7 ports..