-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add utils for WebGPU support detection & Instance creation #6371
Conversation
Clarifies the docs on `wgpu::Instance` accordingly
9216f22
to
b77c64f
Compare
@rukai can you check if this solves the problem for you? I don't have a good repro setup for it right now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much clearer than before!
Co-authored-by: Teodor Tanasoaia <28601907+teoxoy@users.noreply.github.com>
Let's hold off with merging: Tried to test this myself now in Chromium on Wsl which seems to exhibit the issue, but I wasn't able to demonstrate it being fixed with using the new utility here |
phew! Figured it out quite quickly, |
I can confirm this successfully fixes webgl fallback on linux+chrome. |
Connections
Description
Targeting both WebGPU & WebGL at the same time works but is a pain right now. These new utilities and doc lines should make this a lot easier!
Would be nice to make use of this in the official examples, but don't quite know yet how - the examples on web today are geared towards explicit selection.
Testing
Testing done via https://github.com/Wumpf/minifb_wgpu_web_and_desktop/tree/better-webgpu-selection
navigator.gpu
navigator.gpu
no actual webgpu support (Chrome on Linux!)Checklist
cargo fmt
.cargo clippy
. If applicable, add:--target wasm32-unknown-unknown
--target wasm32-unknown-emscripten
cargo xtask test
to run tests.CHANGELOG.md
. See simple instructions inside file.