Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
2021.3.50f1
2022.3.60f1
6000.0.45f1
6000.1.0b13
6000.2.0a8
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).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Tags and Layers sections go out of the "Project Settings" window
- The word “Template” is not capitalised consistently throughout the “Insert a template into current VFX Asset” window
- UI Document gets stuck in the original state when the UI GameObject is disabled and re-enabled
- “AsyncGPUReadback - NativeArray does not have read/write access” error is thrown when using the AsyncGPUReadback:RequestIntoNativeArray after scheduling a job
- Editor freezes when entering the Play Mode after code changes
Add comment