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
- [macOS] Project fails to load when Virtual Artifacts are Corrupted
- Long scheduler times on main thread when using InstantiateAsync with a singular massive Prefab
- The project hangs upon opening it when importing the "discrete_rank2_vector_v2_0.onnx" file
- Opening the Look Dev hangs the Editor when the window is opened for the first time in the project or after deleting the Library folder
- Look Dev has blurry icons on 4k monitors
Add comment