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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
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.