Search Issue Tracker
Active
Under Consideration for 6000.6.X
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}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment