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
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
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).