Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4.0f1
2019.2.0a1
2019.2.5f1
2019.3.0a1
2020.1.0a1
Issue ID
1186127
Regression
No
[Critical] Comparing a value from a multi-dimensional array in a frag shader causes the shader compiler process to crash
How to reproduce:
1. import the minimal shader attached in comment to any project (NewUnlitShader.shader (889 bytes))
2. Reimport the shader file
Expected results: The shader gets successfully compiled
Actual results: The shader compiler throws a "Fragment Program: Internal error communicating with the shader compiler process." error
Reproducible with: 2018.4.10f1, 2019.2.7f2, 2019.3.0b5, 2020.1.0a7
Note: The issue is caused by line 63 in the shader:
_VoxelArray[0][0][(int)i.objVertex.z];
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (2020.2.X):
The _Voxels array declared in the global scope takes more than 64KB of data. Please use a StructuredBuffer or a texture to access this data instead.