Search Issue Tracker
Fixed
Fixed in 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Votes
0
Found in
6000.0.65f1
6000.3.2f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131803
Regression
No
Compute shader is dispatched with unsupported workgroup size on multiple browsers when building the project for Web with WebGPU Graphics API
1. Open the attached project "IN-128143"
2. Go to Project Settings
3. Change Graphics API to WebGPU
4. Build and run using the Web Build Profile
5. Observe the Browser
Actual result: Object stutters, flashes and moves erratically. Screen also sometimes flashes rapidly
Expected result: Object ping-pongs left to right smoothly
Reproducible with: 2023.1.0a1, 6000.0.65f1, 6000.3.2f1, 6000.4.0b3, 6000.5.0a4
Reproducible on: Windows 11 Enterprise (Chrome, Firefox), MacOS (Firefox, Safari)
Not reproducible on: No other environments tested
Notes:
-This happens when using VFX Graph in the provided example project
-Errors also thrown in the console
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note (fix version 6000.4.0b5):
Fixed in 6000.4.0b5
Resolution Note (fix version 6000.3.5f1):
WebGPU: Fix maxComputeWorkGroupSize limit, which was previously set too high and could cause compute shaders to fail on some browsers.
Resolution Note (fix version 6000.0.66f1):
Fixed in 6000.0.66f1