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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2021.2):
Fixed in 2022.1.0a6
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b15