SMG

It should work if you disable the background and floor in render settings.

Make sure you use the screenshot button that supports transparency. Check the wiki for details.

Signed and unsigned normalized types use floating point in WGSL like `vec2`. This makes it impossible to detect if data should use unorm, snorm, or float purely based on WGSL....

GIF rendering is more involved, so it probably won't be in the next update.

The only thing left to be implemented for this is saving with a transparent background when rendering as an image sequence with a format that supports transparency like PNG.

Using bytemuck won't always produce the expected results for uniform buffers and storage buffers since the corresponding WGSL types can have different sizes and alignments than the corresponding type in...

Another challenge to address is whether these memory layout requirements also apply to vertex buffers. Some desktop applications tightly pack elements in a vertex buffer as described in #24. It's...

Using encase for vertex buffers may produce slightly different field offsets than the offsets currently being generated using memoffset. This can potentially cause issues when using the same vertex buffer...

> > But this code works ✅ (with [teoxoy/encase#23](https://github.com/teoxoy/encase/pull/23)) : encase is writing the data using a custom writer implementation for each type that manages padding and alignment. bytemuck is...

> It would be great if the generator explicitly disallowed vec3, or automatically added padding, because this seems like a very common pitfall. I think disallowing vec3 completely is overly...