Skip to content
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

v0.13 - BrowserWebGpu - AutoNoVSync does not properly fallback #2840

Closed
simbleau opened this issue Jul 3, 2022 · 13 comments · Fixed by #2842 or #2843
Closed

v0.13 - BrowserWebGpu - AutoNoVSync does not properly fallback #2840

simbleau opened this issue Jul 3, 2022 · 13 comments · Fixed by #2842 or #2843

Comments

@simbleau
Copy link
Contributor

simbleau commented Jul 3, 2022

Description
AutoNoVSync appears to not fall-back correctly.

Repro steps
https://github.com/simbleau/nbody-wasm-sim/tree/4cd3b2fadb0bed6b71ef3253f3989d78fd5d2020
wasm-pack build --target web
python -m http.server
http://localhost:8000/

Expected vs observed behavior
Error stack forwarded to the console via WASM:
panicked at 'Error in Surface::configure: requested present mode AutoNoVsync is not in the list of supported present modes: [Fifo]'

This seems like a bug because the AutoNoVSync documentation says it will fallback to Fifo, but clear it is not, and detects Fifo as a supported present mode.

Extra materials
2022-07-02_20-17

Platform
wgpu 0.13
linux, ubuntu 20.04 LTS

@seabassjh
Copy link
Contributor

I also get this bug.

Platform
wgpu 0.13
Windows 11

@cwfitzgerald
Copy link
Member

D'oh, easy fix - I'll fix it and launch a backport

@simbleau
Copy link
Contributor Author

simbleau commented Jul 3, 2022

I can do the PR as well if you want. :)
Haven't contributed yet and I wouldn't mind.

@simbleau simbleau changed the title AutoNoVSync does not work on WASM v0.13 - BrowserWebGpu - AutoNoVSync does not properly fallback Jul 3, 2022
simbleau added a commit to simbleau/wgpu that referenced this issue Jul 3, 2022
@cwfitzgerald
Copy link
Member

Sorry didn't reply fast enough, I wanted to refactor bit of code a bit too - but let's merge your change first, then I'll merge mine in so you still get credit :)

@simbleau
Copy link
Contributor Author

simbleau commented Jul 3, 2022

Awesome! Still working on the PR/Changelog ceremony. Thanks!

@simbleau simbleau mentioned this issue Jul 3, 2022
3 tasks
@simbleau
Copy link
Contributor Author

simbleau commented Jul 3, 2022

PR is ready.

@cwfitzgerald cwfitzgerald mentioned this issue Jul 3, 2022
3 tasks
cwfitzgerald pushed a commit that referenced this issue Jul 3, 2022
cwfitzgerald pushed a commit that referenced this issue Jul 3, 2022
@simbleau
Copy link
Contributor Author

simbleau commented Jul 3, 2022

Hey, necromancing because this appears to still be an outstanding issue. I thought we fixed it, but I guess not?
2022-07-03_15-50

@cwfitzgerald
Copy link
Member

Is wgpu-core at 0.13.1?

@simbleau
Copy link
Contributor Author

simbleau commented Jul 3, 2022

Yes

wgpu = { version = "0.13.1", features = ["webgl"] }

@cwfitzgerald
Copy link
Member

That's wgpu, cargo won't update transitive dependencies unless you force it to, try cargo update -p wgpu-core -p wgpu-hal

@simbleau
Copy link
Contributor Author

simbleau commented Jul 3, 2022

It works! Sorry for the necromancing. :P

@cwfitzgerald
Copy link
Member

All good!

@simbleau
Copy link
Contributor Author

simbleau commented Oct 11, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants