Seeking for a WebGPU integration sample

[juj]

In WebGPU, to load a PNG/JPG/WebP texture that the browser supports built-in, one will do

function downloadTexture(url, webGpuDevice) {
  return fetch(url)
    .then(r => r.blob())
    .then(blob => createImageBitmap(blob, { colorSpaceConversion: 'none', premultiplyAlpha: 'none' }))
    .then(bmp => {
    var texture = webGpuDevice.createTexture({
      size: [bmp.width, bmp.height],
      format: "rgba8unorm-srgb",
      usage: GPUTextureUsage.COPY_DST | GPUTextureUsage.COPY_SRC | GPUTextureUsage.RENDER_ATTACHMENT
    });
    webGpuDevice.queue.copyExternalImageToTexture(
      { source: bmp },
      { texture },
      [bmp.width, bmp.height]
    );
    return texture;
  });
}

I am seeking to find a replacement of the above function, i.e. a downloadBasisTexture(url, webGpuDevice) that would be a drop-in replacement for the above function. Does such a code example exist that would be a breeze to integrate?

What I'd like the function to do, is to encapsulate downloading the basis_transcoder.js/.wasm on demand on first texture download, if the transcoder hasn't been downloaded yet, and then examine the passed webGpuDevice handle to find out what the best target to transcode to is.

Before I start digging to develop such an API, I wonder if this might have been done yet already - that I'd be re-doing something that already exists?

[richgel999]

A WebGPU example is on our TODO list, but it's not a super high priority at the moment.

[Ben-Mack]

@richgel999 I'm also highly interested in WebGPU support, given that three.js, playcanvas and other major engines already have WebGPU supported as first class.
Hope to see official WebGPU support soon.
In case it is not in near term plan, if possible, can you give me some guidance so i can try patching with Codex?

@juj Did you success with using Basisu in WebGPU? Can you share some info?

[juj]

Unfortunately I did not. The large size of the BasisU transcoder in WebGL samples turned me away from using Basis. Many of my use cases contained small mobile optimized textures, and there I found that it was smaller to directly serve directly ASTC compressed textures.

In my tests I got Basis textures to be about ~25% smaller than ASTC, but the +1MB size overhead of the Basis transcoder did not outweigh the individual texture size win. So I concluded that on size optimized web sites it was smaller to serve separately DXT and ASTC compressed textures from the CDN.