Search Issue Tracker
Fixed
Fixed in 6000.5.0a2, future release
Votes
17
Found in
2021.3.39f1
2022.3.33f1
6000.0.6f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-73639
Regression
No
Shader errors are logged in WebGL when building a URP project
How to reproduce:
1. Create a new empty URP project
2. Press File → Build and Run
3. In Player, press “CTRL+SHIFT+J“
4. Observe the browser console
Expected result: No shader errors are logged
Actual result: Shader errors are logged
Reproducible with: 2021.3.39f1, 2022.3.33f1, 6000.0.6f1
Reproducible on: Windows 10, Windows 11 (user’s device)
Not reproducible on: No other environment tested
Error messages:
ERROR: Shader
Hidden/CoreSRP/CoreCopy shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
ERROR: Shader
Hidden/Universal/HDRDebugView shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Note: Only reproducible in WebGL Player
Comments (4)
-
pichikala
Nov 08, 2025 16:13
I’m still seeing this issue in Unity 6000.0.60f1. The shader errors appear when building a URP project for WebGL, and the problem causes players using older 32bit browsers or lower end devices to be unable to run the game. Is there any known workaround or planned fix for this version?
-
LePaithon
Oct 09, 2024 20:18
Happens to me as well. The error disappears if I disable "cast shadows" option when building for WebGL.
-
KUnit6000
Sep 28, 2024 18:40
Can confirm. Broken with Unity 6000.20f1and freezes the browser (Chrome) on Windows 10 with an RTX2080Ti GPU.
However, the build does work on Android with the Firefox browser.
-
djonny_d
Aug 22, 2024 09:51
Repeats on macOS Sonoma 14.6.1. Here the WebGL player screen is black, the game does not launch on any browser.
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
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
- New Hierarchy visibility and pickability icon behavior differs from documentation
- [Usability] Selected node gets unselected when undoing changes in the Graph Inspector Node Settings tab
Resolution Note:
This is fixed in 6000.5.02, landed and verified.
Resolution Note (fix version future release):
This is fixed in 6000.5.02, landed and verified.
Resolution Note:
Postponing U7 ports