Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
Issue ID
1103046
Regression
No
[Vulkan] Compute shader compilation failure with Vulkan + MSAA + Tex2DArray declaration/operation macros
Adding Tex2DMSArray declarations and operations to a compute shader causes it to fail to compile for Vulkan only
Steps:
1. Just import the attached compute shader from paulan to a project
2. switch to Vulkan and select the compute shader and observe error on it
Reproducible in :2019.1.0a12, 2018.3.1f1, 2017.4.13f1
Comments (1)
-
unity_W3rLGozcKkUuGg
Aug 02, 2019 10:56
Can we have this fix on LTS version?
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
- “Default state” name in Inspector is not truncated when given longer name for “New State” in Animator window
- Upgrading HDRP Project causes the Cloud Layer to warp when using the Global Volume with the Visual Environment enabled
- The Inspector does not shown SkinnedMeshRenderer Bounds when they are overriden by script
- Confusing validation message in Scoped Registries
- Compute shader is dispatched with unsupported workgroup size on multiple browsers when building the project for Web with WebGPU Graphics API
Resolution Note (fix version 2019.1):
Fixed in 2019.3.0a3 (91c086393aab)