shame icon indicating copy to clipboard operation
shame copied to clipboard

A shader EDSL for writing render and compute pipelines in rust

Results 19 shame issues
Sort by recently updated
recently updated
newest added

I couldn't find a published crate for shame, but maybe it's under an unexpected name? Or is there some other plan for distribution or this just hasn't been done yet?

I see this is planned, but it's also clearly a lot of work. What would be the limiting factors in considering wgsl support as a first class output language? Great...

It didn't look to me like image types were supported yet? For example, I'd like to bind a render target for the shaded outputs of a compute level ray tracer...

This pr just rustfmt's the code. There were a few lines that rustfmt was having trouble with, I fixed those manually. This is in preparation for another pr. Merging this...

The diff for this will be hard to read until https://github.com/RayMarch/shame/pull/4 is merged. I suggest looking at that first. In this PR I run `cargo clippy --all-targets` and fix all...

## Storage/Uniform Buffer Any API rework The goal of this PR is twofold - Improve the user facing `Any` api for creating storage and uniform buffer bindings, mainly by making...

## `TypeLayout` Rework This PR reworks `TypeLayout` for two purposes: - Centralize all layout calculations into one place - the `type_layout` module. - Prepare for adding #20 support . -...

## Dynamic Vertex Buffer This PR adds dynamic vertex buffer support and changes the corresponding any api to allow extending vertex attributes to an already existing vertex buffer. Part of...

Right now, the WGSL storage layout is the default layout applied to structs when `#[derive(GpuLayout)]` is used. For consistency, and to allow maybe adding a `#[gpu_repr(uniform)]` in the future, the...

### Problem Dynamic types don't have a statically known shame type layout. For example you might not know which vertex attributes your meshes are going to have, however the current...