Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2019.3.0f1
2020.1
Issue ID
1204218
Regression
No
'Internal error communicating with the shader compiler process' error is thrown when large array of float4x4 is used
How to reproduce:
1. Open the attached 'InternalErrorCommunicatingWithShaderCompiler.zip'
2. Select 'InternalErrorCommunicatingWithShaderCompiler.shader' shader in the Project Browser
3. Click 'Compile and show code' button in the Inspector
Expected result: No errors or meaningful errors are thrown when the shader is compiled
Actual result: '<Unnamed Pass>, Fragment Program: Internal error communicating with the shader compiler process.' error is thrown to the Console
Reproducible with: 2017.4.36f1, 2018.4.15f1, 2019.2.18f1, 2019.3.0f5, 2020.1.0a19
Notes:
- Reproducible on Windows and macOS
- Reproducible with DirectX11, Metal, OpenGLCore, OpenGLES2, Vulkan
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2020.1.X):
This is a crash in fxc the back end shader compiler, this can not be fixed until we upgrade to dxc.