Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2020.2.0b9
Issue ID
1302657
Regression
No
[Vulkan] Linux Editor throws a SPIR-V validation error when returning OpArrayLength in Compute shader
How to reproduce:
1. Open the user attached project (spirv-arraylength-test.zip) with the "-force-vulkan-layers" argument
2. Enter Play Mode
3. Observe the Console output
Expected result: the Console produces no output
Actual result: a validation error is thrown in the Console
Reproducible with: 2020.2.0b9
Notes:
1. Couldn't provide additional reproducible versions due to the issue not being reproducible on any available tester machines using the Nvidia GTX 1060 or AMD GPUs
2. Reproducible on Ubuntu 18.04 using the Nvidia GTX 1080ti GPU
3. Not reproducible on Windows 10
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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Resolution Note (fix version 2021.2):
Fixed in 2022.1.0a6
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b15