Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
A little bit of context: I am working on translating https://observablehq.com/@flimsyhat/tdse-simulation / https://davidar.io/post/quantum-glsl to a wgpu based implementation. So far, I have adapter the triangle example by adding a buffer that can be read to and written to by both the render shader and a compute shader. However, when I try to initialize the values in the buffer inside of a compute shader ( which I know can be done on the CPU as well, but I need to write to the buffer on the GPU eventually ), I get the error "The pipeline layout, associated with the current compute pipeline, contains a bind group layout at index 0 which is incompatible with the bind group layout associated with the bind group at 0". The only reference of this error I saw online was https://github.com/sotrh/learn-wgpu/issues/40, where the buffer was not initialized before it the compute shader attempted to write to it, however I don't think that is the case with mine.
Why is the hello-compute example able to write to a buffer without a layout the compute pipeline ( https://github.com/gfx-rs/wgpu/blob/trunk/wgpu/examples/hello-compute/main.rs )?
Adding a layout to the compute shader is now causing the program to throw the error "Buffer (0, 1, Metal) is still mapped", even without using the buffer in the shader ( https://github.com/AlistairKeiller/quantumv2/tree/e3907711df134dab0693682ffb80622d69cc9745 ).