Search Issue Tracker
Fixed
Fixed in 6000.0.71f1, 6000.3.12f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1
Votes
0
Found in
6000.4.0b10
6000.5.0a7
6000.6.0a1
Issue ID
UUM-134978
Regression
Yes
Shader compiler and Shader errors are thrown in the Console when building Web platform with WebGPU (Experimental) enabled in Auto Graphics API
Steps to reproduce:
1. Create a new Unity project
2. Open Build Profiles window
3. Switch to Web Platform
4. Go to Edit -> Project Settings -> Player -> Other Settings
5. Find and uncheck Auto Graphics API
6. Select WebGPU (Experimental) Graphics API
7. Go back to to Build Profiles window
8. Build the project
Actual results: Shader compiler and shader errors are thrown in the Console window after project is built
Expected results: No errors are thrown in the Console window after project is built
Reproducible with versions: 6000.4.0b9 (74e5d09f9bc7), 6000.4.0b10
Not reproducible with versions: 6000.3.10f1, 6000.5.0a7, 6000.4.0b8 (f3f87a02ba54)
Tested on (OS): Ubuntu 24.04 (repro), macOS Silicon Tahoe 26.2 (M1) (no repro)
Notes:
- Building on Web Platform might take ~15 minutes.
{code:java}
Shader error in 'TraceVirtualOffset': Compiling MainRayGenShader: Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log. Error code 0x80000004 (Not connected).
{code}
{code:java}
Shader compiler: Compile TraceVirtualOffset - MainRayGenShader: Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log. Error code 0x80000004 (Not connected).
{code}
{code:java}
Shader error in 'InstanceWindDataUpdateKernels': Compiling WindDataCopyHistoryMain: Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log. Error code 0x80000004 (Not connected).
{code}
{code:java}
Shader compiler: Compile InstanceWindDataUpdateKernels.compute - WindDataCopyHistoryMain: Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log. Error code 0x80000004 (Not connected).
{code}
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a9):
Fixed in 6000.5.0a9
Resolution Note (fix version 6000.4.0f1):
Fixed in 6000.4.0f1
Resolution Note (fix version 6000.3.12f1):
Fixed in 6000.3.12f1
Resolution Note (fix version 6000.0.71f1):
Fixed in 6000.0.71f1