-
Notifications
You must be signed in to change notification settings - Fork 193
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
Issues with textureGather on texture_2d<u32> #2135
Comments
@teoxoy this commit 9ddf38e turned out to be necessary for my shader https://github.com/JMS55/bevy/blob/gtao/crates/bevy_pbr/src/ssao/denoise_ssao.wgsl#L25. The tests I wrote just didn't catch it :/. |
What is the error exactly? |
Ah sorry, the error is:
|
This looks like it's caused by this validation error over in wgpu: https://github.com/gfx-rs/wgpu/blob/f14bee6740b8755afa362c3be6ef4b225209871a/wgpu-core/src/validation.rs#L1071 I think we should allow those through if the Please open an issue/PR on the wgpu repo. |
Edit: Can't reproduce on naga master. However, now a different validation error is produced in wgpu:
Caused by the following match ignoring the gather field in naga:
naga/src/valid/analyzer.rs
Lines 571 to 594 in df4e403
According to the spec, this should be a valid operation. However, I get the following error in my project:
Taking a look at naga's source code, it looks like this is an
InvalidImageClass
Err. There's only 3 places it's created, of which the following seems most likely:naga/src/valid/expression.rs
Lines 382 to 389 in 2a11d83
It looks like originally this match statement assumes a float texture only, which is a valid assumption when this was originally used for only regular samples, but when gathers were added, this assumption was broken.
The text was updated successfully, but these errors were encountered: