Unity Issue Tracker - Binding a mipmap as UAV to a compute shader causes validation errors with WebGPU

Fixed

6.5.X

6.4.X

6.3.X

6.0.X

6000.0.65f1

WebGPU: Fix for setting mip level for writable textures bound to compute shaders.

Steps to reproduce:

Open attached project WebGPUMipBug.zip.
Open SampleScene.unity.
Make sure that Web platform is selected in the build window, and that the graphics library is set to WebGPU.
Build and run.
Open the browser console and observe validation errors.

Error message:

mipLevelCount (4) of [TextureView of Texture (unlabeled 8x8 px, TextureFormat::RGBA8Unorm)] expected to be 1.
 - While validating entries[0] against { binding: 0, visibility: ShaderStage::Compute, storageTexture: {format: TextureFormat::RGBA8Unorm, viewDimension: TextureViewDimension::e2D, access: StorageTextureAccess::WriteOnly} }.
 - While validating [BindGroupDescriptor] against [BindGroupLayout "TestCompute.CSMain_BindGroupLayout[0]_693"]
 - While calling [Device].CreateBindGroup([BindGroupDescriptor]).

(index):1 [Invalid BindGroup "TestCompute.CSMain_BindGroup[4]_696"] is invalid.
 - While encoding [ComputePassEncoder (unlabeled)].SetBindGroup(0, [Invalid BindGroup "TestCompute.CSMain_BindGroup[4]_696"], 0, ...).
 - While finishing [CommandEncoder (unlabeled)].

Actual results: Validation errors, shader fails to execute.

Expected results: No validation errors, shader works.

Reproduced on 6000.5, Windows 11

Binding a mipmap as UAV to a compute shader causes validation errors with WebGPU

Unity: WebGPU

Fixed

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Binding a mipmap as UAV to a compute shader causes validation errors with WebGPU

Unity: WebGPU

Statuses

Fixed

Resolution Notes

6.5.XFixedWebGPU: Fix for setting mip level for writable textures bound to compute shaders.

6.4.XFixedWebGPU: Fix for setting mip level for writable textures bound to compute shaders.

6.3.XFixedWebGPU: Fix for setting mip level for writable textures bound to compute shaders.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?