Swoorup Joshi

> > The vertex_index you are specifying is built in and doesn't need to be specified. > > I understand that this is the intended behavior. However, the `vertex_index` should...

On second thought, generating `vertex_index` isn't necessary a bug. In places where this is used in eg: storage buffer, it will be treated as padding field, and the gpu fills...

> ## Disclaimer > I don't know if this is the right place to put this (it does seem to be related), if you want to I can move this...

Fixed by https://github.com/Swoorup/wgsl-bindgen/pull/67 Also alignment is correct as is, see demo files for example: - https://github.com/Swoorup/wgsl-bindgen/blob/main/example/shaders/vec3_vertex_demo.wgsl - https://github.com/Swoorup/wgsl-bindgen/blob/main/example/src/demos/vec3_vertex_demo.rs

Closing as fixed in https://crates.io/crates/wgsl_bindgen/0.19.1

I'll have to review each of these cases. IIRC those casing issues arises if some shaders don't confirm to rust naming convention standards. It was easier to keep everything in...

Doesn't look possible, at least we should look into a way to manually override the generation.

Currently a crude way is employed, ie if shader has fragment, vertex entries, just use them both. And isn't that granular. Think this is good enough, ensure that this also...

> @GNRSN The [determinate installer is maintained here](https://github.com/DeterminateSystems/nix-installer) and is not official (though most people recommend it over the official installer for good reason), so if this was an issue...

Are you using it as uniform buffer object or a storage buffer object? I'll have to recheck this later, but I think at the time I found that the alignment...