Search Issue Tracker
Third Party Issue
Votes
0
Found in
6000.0.62f1
6000.2.13f1
6000.3.0f1
6000.4.0a5
6000.5.0a1
Issue ID
UUM-127804
Regression
No
"Compiling CSMain: Internal error communicating with the shader compiler process." error when compiling a shader
Reproduction steps:
1. Open the attached “IN-121194.zip” project
2. From the Project window, search for “02_Whitted_BVH.compute” asset and select it
3. In the Inspector, click “Show compiled code”
4. Observe the Inspector or the Console
Expected result: No errors
Actual result: “Compiling CSMain: Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log. Error code 0x80000004 (Not connected).” error is shown
Reproducible with: 2023.1.0b1, 6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a1
Reproducible on: Windows 11
Not reproducible on: no other environments tested
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Compiler crash seems to be due to a bug in FXC.
Workarounds:
- Compile shader with DXC (#pragma use_dxc)
- Refactor the body of the 'if (hitL && hitR)' condition in SceneTrace.hlsl to the following:
uint v0, v1;
if (tNL < tNR) { v0 = right; v1 = left; }
else { v0 = left; v1 = right; }
stack[sp++] = v0;
stack[sp++] = v1;