-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Updated to wgpu 0.16.0, wgpu-hal 0.16.0 and naga 0.12.0 #8446
Conversation
Rollback TextureSampleType::Float filterable setter Fix Error when using a filterable on a multisample
Welcome, new contributor! Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨ |
Could you also update naga to 0.12? You may have to change a few other things for examples to work, don't hesitate to run them all on your computer ( |
Okay, I will update naga and then run the examples to verify. Emmm, but
|
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.
Hey cool! I was working on the same changes. I don't have any knowledge at all in the specifics of that domain and I was struggling at a few places. Can you maybe clarify a few changes?
Feel free to ignore my comments if they get in the way.
Just a heads up for the changelog, this update also fixes this issue 5732 🙂 |
Be warned that 0.16.0 is a breaking change, so the release notes will need to include some sort of migration guide for changing keywords like |
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.
LGTM. Changes match what's in the wgpu changelog.
It looks like your PR is a breaking change, but you didn't provide a migration guide. Could you add some context on what users should update when this change get released in a new version of Bevy? |
There are some code to fix behind features, and some formatting to update. |
FYI, just a small warning: We found some crashes with the update to wgpu 0.16. It only happens when compiling to wasm, running the app on MacOS and changing the perspective of the camera. It crashes not only the app, but the browser. We tested this on several browsers and it happened everywhere everytime. The App was running normally when compiled for native use. It's most likely some issue with MacOS + the new version of wgpu and isn't caused by bevy directly. We are still investigating it and are working on a minimal repro example to test if it might be related to that specific machine or if it's really related to MacOS in general. Update: Apparently it also happens with Update 2: There is an issue for this now, it's #8481 |
Please run with |
@superdump I have revised your question over these commits. Please see if there are any other items that need to be modified. |
Could you also compile with feature |
@mockersf Thanks to suggestion, the related CI problem has been fixed. I need your help to take a look at the version of the |
I've looked at the |
* Update the bevy example to wgpu 0.16 After bevyengine/bevy#8446 * Remove inaccurate README warning
# Objective Since #8446, example `shader_prepass` logs the following error on my mac m1: ``` ERROR bevy_render::render_resource::pipeline_cache: failed to process shader: error: Entry point fragment at Fragment is invalid = Argument 1 varying error = Capability MULTISAMPLED_SHADING is not supported ``` The example display the 3d scene but doesn't change with the preps selected Maybe related to this update in naga: gfx-rs/naga@cc3a8ac ## Solution - Disable MSAA in the example, and check if it's enabled in the shader
Objective
Changelog
TextureSampleType::Float
on a multisampleBindingType::Texture
. (reject binding type multisampled when on a float filterable sample type gfx-rs/wgpu#3686)