-
Notifications
You must be signed in to change notification settings - Fork 873
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
Unexpected validation warnings #1390
Comments
@almarklein thank you for filing! Could you record an API trace reproducing the last validation error? |
About the PoolSizeCount warning: it appeared in an example (in wgpu-py) that is basically a port of the hello triangle. It seems related to #240. I made the warning disappear by not creating empty bind groups (and layouts). Incidentally, that example started crashing after the recent changes to wgpu-native, and the applied fix also made it work again. It could well be that the hello triangle in wgpu-native is also broken now. I'll have a look in a moment. |
Filed zakarumych/gpu-descriptor#14 upstream. |
Following up on the triangle example in wgpu-native: gfx-rs/wgpu-native#97 |
Patch for |
Thanks! |
I keep getting these two validation warnings for even the simplest of shaders. The code does run (no crash or panic).
This is on Win10 with Intel Graphics (things crash if enable the NVida GPU, but that's a different issue). Using wgpu-native from master (naga 25). LunarSDK 1.2.176.1 (05-May-2021). Shaders are provided to wgpu in WGSL.
ImageMSArray capability:
InterpolationFunction capability:
Also seeing this from time to time (poolSizeCount must be greater than 0):
The text was updated successfully, but these errors were encountered: