-
Notifications
You must be signed in to change notification settings - Fork 949
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
Added support for MSAA(x2,x8) beyond WEBGPU restrictions for native a… #3140
Conversation
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.
PR on the whole looks good, but I think there's a cleaner strategy for the flags which will re-arrange things a bit
Hi @cwfitzgerald , let me know what you think! |
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.
This is great stuff, have some comments, mostly around feature querying.
Looking forward to having this in!
hey @cwfitzgerald, please take a look !. |
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.
Very close, some small stuff
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.
Thanks!
Checklist
cargo clippy
.RUSTFLAGS=--cfg=web_sys_unstable_apis cargo clippy --target wasm32-unknown-unknown
if applicable.Connections
Closes Can't set MSAA samples beyond 4 .
Description
Native adapters can now use MSAA x2 and x8 if it's supported , previously only x1 and x4 were supported .
Testing
Tested locally on chrome canary , macOS(intel) , win10