WebGPU is a new standard coming to browsers, and the primary reason for switching to using wgpu as it's more performant than WebGL and aligns with modern graphics APIs. Firefox is behind in supporting it and stability is still a bit shaky across platforms.
Enabling it is super simply:
Add the webgpu feature flag to wgpu in tetanes/Cargo.toml
Change Renderer::create_painter back to using the default wgpu::Backends
An attempt was made to have this enabled previously, but some issues were encountered when trying to load in Chrome on Linux. Worth another go and seeing how it performs across different platforms.
One possible solution if there are still issues is to try and catch any errors creating the Painter when using the BROWSER_WEBGPU backend, and trying to fallback to GL, similar to how it's currently falling back if the default adapter limits aren't supported on the platform.
WebGPU is a new standard coming to browsers, and the primary reason for switching to using
wgpuas it's more performant than WebGL and aligns with modern graphics APIs. Firefox is behind in supporting it and stability is still a bit shaky across platforms.Enabling it is super simply:
webgpufeature flag towgpuintetanes/Cargo.tomlRenderer::create_painterback to using the defaultwgpu::BackendsAn attempt was made to have this enabled previously, but some issues were encountered when trying to load in Chrome on Linux. Worth another go and seeing how it performs across different platforms.
One possible solution if there are still issues is to try and catch any errors creating the
Painterwhen using theBROWSER_WEBGPUbackend, and trying to fallback toGL, similar to how it's currently falling back if the default adapter limits aren't supported on the platform.See: https://developer.mozilla.org/en-US/docs/Web/API/WebGPU_API#browser_compatibility