Search Issue Tracker
Fixed
Fixed in 6000.5.0a3
Votes
0
Found in
2021.3.50f1
2022.3.60f1
6000.0.45f1
6000.1.0b13
6000.2.0a8
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-102039
Regression
No
Shader error is thrown when using a Compute Shader with a second kernel
How to reproduce:
1. Open any project
2. Import the attached “Compile DepthPyramidComputeShader.compute“ compute shader
3. Observe the Console
Expected result: No errors are thrown
Actual result: Internal shader error is thrown
Reproducible with: 2021.3.50f1, 2022.3.60f1, 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Error: Shader error in 'DepthPyramidComputeShader': Compiling CSCombine: Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log. Error code 0x80000004 (Not connected).
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
- UI Toolkit World UI Text Field unfocuses immediately when clicking on it using XR Controller
- Crash on CallWindowProcW when entering Play mode for the second time and running the Editor in the background while using System.Windows.Forms functions
- 2D Freeform Light shadows disappear when light center is offset from shape bounds
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
- Crash on CollectAllSceneManagerAndObjectIDs when opening a specific Scene
Resolution Note (fix version 6000.5.0a3):
The source of the issue seems to be a bug in FXC, and unfortunately we can't do anything about it. Could try using DXC which may not contain the bug.
For now, I've improved the error message reported to more clearly indicate that the shader compiler crashed due to FXC (as opposed to a crash caused by code Unity owns).