Search Issue Tracker
Third Party Issue
Votes
0
Found in
6000.0.48f1
6000.1.2f1
6000.2.0a10
Issue ID
UUM-104429
Regression
No
WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
Reproduction steps:
1. Open the attached “IN-100384.zip“ project
2. Go to File > Build Profiles
3. Make sure “ShinySSRR” Scene is included in the Scene List
4. Go to Player Settings
5. Make sure Graphics API is “WebGPU (Experimental)”
6. Build and Run for WebGL (File > Build and Run)
7. Observe the Player in the browser
Expected result: The Scene is rendered in the Player
Actual result: The Player is black, nothing is rendered
Reproducible with: 6000.0.48f1, 6000.1.2f1, 6000.2.0a10
Couldn’t test with: 2022.3.48f1 (WebGPU not available)
Reproducible on: macOS 13 (M1), macOS 14.5 (M1 Ultra) (User reported)
Not reproducible on: Windows 11, macOS 15.3 (M2 Ultra)
Notes:
- The issue appears to be specific to M1 GPUs
- Does not reproduce with WebGL 2 Graphics API
- The custom Renderer Feature is on the “PC_Renderer” asset
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Tested macOS 15.5 with a M1 Macbook with Chrome and it renders correctly. The video shows the browser being used as Firefox. Firefox is still behind on their WebGPU implementation and it currently is only supported by Firefox Nightly after enabling the experimental WebGPU flag. The same will be true of Safari, which can be tested with Safari Technology Preview after enabling the WebGPU flag. It is recommended to use Chrome or a Chromium based browser for now, until Firefox and Safari have officially shipped WebGPU support.