[johnyzee]

Progress indicator spins forever. Console:

  webgpu-sponza-demo/:1 No available adapters.
  index-BeB41sTJ.js:2288 Uncaught (in promise) TypeError: 
  Cannot read properties of null (reading 'requestDevice')
    at yn.initialize (index-BeB41sTJ.js:2288:13559)
    at async index-BeB41sTJ.js:2288:13792

Newest Chrome on Win11.

[kgeist]

On my Firefox:

  Uncaught (in promise) ReferenceError: GPUShaderStage is not defined

On Chrome:

   TypeError: Cannot read properties of null (reading 'requestDevice')

It would be great if it showed some message, like, "your browser is not supported", instead of just showing an indicator which spins forever. At first I thought it was downloading a large WASM file and waited for a minute...

[vient]

For me fails on identical setup with

  GET https://gnikoloff.github.io/webgpu-sponza-demo/assets/Sponza.bin
  net::ERR_CONNECTION_CLOSED 206 (Partial Content)

[sterlind]

Do you have a GPU?

[zamadatix]

More than that, does chrome://gpu/ show "WebGPU: Hardware accelerated" (i.e. not only do you have a GPU but is Chrome finding it usable for WebGPU).

[Eduard]

Graphics Feature Status

=======================

* Canvas: Hardware accelerated

* Canvas out-of-process rasterization: Enabled

* Direct Rendering Display Compositor: Disabled

* Compositing: Hardware accelerated

* Multiple Raster Threads: Enabled

* OpenGL: Enabled

* Rasterization: Hardware accelerated

* Raw Draw: Disabled

* Skia Graphite: Disabled

* Video Decode: Hardware accelerated

* Video Encode: Software only. Hardware acceleration disabled

* Vulkan: Disabled

* WebGL: Hardware accelerated

* WebGL2: Hardware accelerated

* WebGPU: Disabled

* WebNN: Disabled

[zamadatix]

That "WebGPU: Disabled" can be anything from "Chrome considers the driver too buggy to enable WebGPU on by default for users" to "Chrome doesn't support that GPU/OS/Driver combo for WebGPU at all". You can try force enabling some various GPU flags in chrome://flags/ but whether that's successful will depend on the particular setup.

Until that switches from "Disabled", no WebGPU content or demos will load in your Chrome instance.

You can see overall user support https://web3dsurvey.com/webgpu. Particularly Safari on iOS/macOS and most browsers on Linux are still yet to start rolling out support by default.

[reaperducer]

Do you have a GPU?

If he didn't, he would get the message "This demo requires the modern WebGPU graphics API to run. Seems like your browser does not support it."

[zamadatix]

You don't need a dedicated graphics processing unit to display video from a computer! Back before GPUs were even a thing the framebuffer would just be a region of memory and the video controller would turn that into a signal. Nowadays the latter is assumed to be integrated with the GPU because "who wouldn't need dedicated graphics processing in a desktop"?

[stronglikedan]

I don't have a GPU and it runs fine for me with no errors or messages.