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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2019.1):
Fixed in 2019.3.0a3 (91c086393aab)