Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2018.4
2019.4
2020.1
2020.2
2021.1
2021.2
Issue ID
1318555
Regression
No
Vulkan shader compilation fails when shader uses an array of structs
Reproduction steps:
1. Add the attached shader "vulkan_struct_array_issue.shader" to a project
2. Select the shader
3. In the shader's Inspector Window select the dropdown next to "Compile and show code" and set "Custom" and "Vulkan"
4. Click the "Compile and show code" button
Expected result:
Shader compiles for Vulkan without errors
Actual result:
The following errors are printed to the Console Window and are added to the Shader Inspector:
"Shader error in 'vulkan_struct_array_issue': glslang: '' : compilation terminated at line 33 (on vulkan)"
"Shader error in 'vulkan_struct_array_issue': glslang: '[' : array index out of range '4' at line 33 (on vulkan)"
Reproducible in: 2021.2.0a7, 2021.1.0b9, 2020.2.6f1, 2020.1.17f1, 2019.4.21f1, 2018.4.32f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment