Search Issue Tracker
Fixed in 2021.3.31f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a4, future release
Votes
0
Found in
2021.2.14f1
2021.3.19f1
2022.2.9f1
2022.3.0f1
2023.1.0b6
2023.2.0a5
2023.3.0a2
Issue ID
UUM-30365
Regression
No
Shader generation on Vulkan throws gl_Layer error
Reproduction steps:
1. Open the attached “Test Project” project
2. Build the Project with “SampleScene” Scene
Expected result: The project builds without any errors
Actual result: The console prints out “Shader error in 'Valve/VR/Silhouette': glslang: 'gl_Layer' : identifiers starting with "gl_" are reserved at line 35 (on vulkan)” error
Reproducible with: 2021.2.14f1, 2021.3.19f1, 2022.2.9f1, 2023.1.0b6, 2023.2.0a5
Not reproducible with: 2020.3.45f1, 2021.2.13f1
Reproducible on: Ubuntu 22.04, Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Points Lights are getting culled prematurely when using Forward+ and Deferred+ rendering paths
- Search's Indexing settings in the Preferences window are not searchable
- Crash on block_locate_free when opening a specific project
- "Project connected" pop opens again after closing it
- Cloud Code Authoring logs "JsAssetHandler:OpenAsset (int,int) does not match any of [OnOpenAssetAttribute] expected signatures" when opening or switching scenes and having the Deployment Package Installed
Add comment