-
Notifications
You must be signed in to change notification settings - Fork 964
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
Attachments only support sample counts 1 and 4 #1832
Labels
Comments
kvark
added
area: api
Issues related to API surface
type: enhancement
New feature or request
labels
Aug 19, 2021
That's what WebGPU exposes today. We can think of a way to expose this in a non-portable native-only way. |
To avoid further confusion, it might be a good idea to throw a more specific error which states that only 1 and 4 are valid values. Or you can go down Vulkan path of defining enums for sample counts, and only allowing for 1 and 4 for example. |
bors bot
pushed a commit
to bevyengine/bevy
that referenced
this issue
Oct 29, 2021
Adds support for MSAA to the new renderer. This is done using the new [pipeline specialization](#3031) support to specialize on sample count. This is an alternative implementation to #2541 that cuts out the need for complicated render graph edge management by moving the relevant target information into View entities. This reuses @superdump's clever MSAA bitflag range code from #2541. Note that wgpu currently only supports 1 or 4 samples due to those being the values supported by WebGPU. However they do plan on exposing ways to [enable/query for natively supported sample counts](gfx-rs/wgpu#1832). When this happens we should integrate
Is this not fixed by #3140? |
It was! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
When starting a render pass which has multisampling enabled, I get this validation error:
Sample counts 1 and 4 work, while 2 and 8 do not, even though my GPU definitely supports those. I looked around and I suspect this condition is the problem:
wgpu/wgpu-core/src/command/render.rs
Lines 679 to 681 in 0b1657f
The text was updated successfully, but these errors were encountered: