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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Resolution Note (fix version 2019.1):
Fixed in 2019.3.0a3 (91c086393aab)