Search Issue Tracker
Feature Request
Votes
0
Found in
2020.2.0a13
2020.3.34f1
2021.3.3f1
2022.1.1f1
2022.2.0a14
Issue ID
UUM-709
Regression
Yes
Compute Shader with RWBuffer<> type throws an error when it is compiled with Vulkan API
Reproduction steps:
1. Open the user's attached "Buffer and RWBuffer dont work in Vulkan.zip"
2. In the Project window select Assets/Resources/NewComputeShader.compute
3. In the Inspector click "Show compiled code"
Expected result: No errors appear in the Inspector
Actual result: "The resource 'Result_origX0X' uses an unsupported type/format at kernel TESTKernel" error appears in the Inspector
Reproducible with: 2020.2.0a13, 2020.3.34f1, 2021.3.3f1, 2022.1.1f1, 2022.2.0a14
Not reproducible with: 2019.4.39f1, 2020.2.0a12
Reproducible on: Windows 10, Windows 11
Could not test on: macOS (Intel) 12.2.1, Vulkan API is not available
Note: Not reproducible with Direct3D11, Direct3D12, and Metal APIs
Workaround: Error does not appear if RWBuffer<> is changed to RWStructuredBuffer<>
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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note:
This is not a bug, but rather because right now our Vulkan backend only accepts single float/int/uint as RWBuffer formats. The work to extend the support for more formats is underway.