Unity Issue Tracker - [Android][OpenGLES3] "#version 310 es" is defined in compute shader instead of "#version 320 es" when writing a compute shader in HLSL for OpenGLES 3.2

Active

Under Consideration for 2021.3.X, 2022.3.X

Votes

0

Found in

2021.3.34f1

2022.3.17f1

2023.2.6f1

2023.3.0b3

6000.0.0b11

Issue ID

UUM-60833

Regression

No

[Android][OpenGLES3] "#version 310 es" is defined in compute shader instead of "#version 320 es" when writing a compute shader in HLSL for OpenGLES 3.2

--

-

Jan 17, 2024

Reproduction steps:
1. Open the attached project “ReproProject”
2. Ensure OpenGLES3 is used as the Graphics APIs (menu: Edit > Project Settings > Player > Other Settings > Graphics APIs)
3. In the Project Window, select the “Assets/Scenes/test.compute” file
4. In the Inspector Window, Press the “Show compiled code” button
5. Observe the line 4 of the code

Expected result: “#version 320 es” is stated
Actual result: “#version 310” es is stated

Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.6f1, 2023.3.0b3

Reproducible on: macOS(Intel) 14.2.1
Not reproducible on: No other environment tested

Note: This issue results in missing intrinsic functions supported in 3.2, like imageAtomicMax ([https://registry.khronos.org/OpenGL-Refpages/es3/html/imageAtomicMax.xhtml|https://registry.khronos.org/OpenGL-Refpages/es3/html/imageAtomicMax.xhtml]).

First few lines of the compute shader file:

1. **** Platform OpenGL ES 3:
2. Compiled code for kernel CSMain
3. keywords: <none>
4. #version 310 es
5. #extension GL_EXT_texture_buffer : require

Log in to vote on this issue

Search Issue Tracker

0