Search Issue Tracker
Fix In Review for 14.0.3
Votes
0
Found in [Package]
12.1.6
Issue ID
1410886
Regression
Yes
[URP][GLES2] Shader errors are thrown when compiling the Scaling Setup Shader for GLES20
How to reproduce:
1. Open the user-submitted project
2. In the Project window, select the Shader "ScalingSetup" (Packages/com.unity.render-pipelines.universal/Shaders/PostProcessing/ScalingSetup.shader)
3. In the Inspector window, in the "Compiled code" dropdown, enable "GLES20"
4. Click "Compile and show code"
5. Inspect the Console window (Window > General > Console)
Expected result: No errors are seen in the Console
Actual result: Shader errors are seen in the Console
Reproducible with: 12.1.6 (2021.2.16f1), 14.0.1 (2022.2.0a8)
Could not test with: 7.7.1 (2019.4.36f1), 10.8.1 (2020.3.31f1), 12.1.5 (2021.2.15f1), 12.1.6 (2022.1.0a1), 13.1.7 (2022.1.0b12), 14.0.0 (2022.2.0a7) (Scaling Setup Shader is unavailable)
Errors:
Shader error in 'Hidden/Universal Render Pipeline/Scaling Setup': 'SampleTexture2DArrayBicubic': function must return a value at gles2/Library/PackageCache/com.unity.render-pipelines.core@14.0.1/ShaderLibrary/Filtering.hlsl(135) (on gles)
Shader error in 'Hidden/Universal Render Pipeline/Scaling Setup': syntax error: unexpected token '#' at gles2/Library/PackageCache/com.unity.render-pipelines.core@14.0.1/ShaderLibrary/Filtering.hlsl(135) (on gles)
Shader error in 'Hidden/Universal Render Pipeline/Scaling Setup': syntax error: unexpected token '#' at gles2/Library/PackageCache/com.unity.render-pipelines.core@14.0.1/ShaderLibrary/Filtering.hlsl(137) (on gles)
Shader error in 'Hidden/Universal Render Pipeline/Scaling Setup': SV_VertexID semantic is not supported on GLES 2.0 at line 63 (on gles)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment