Simon Repp

I see what you're getting at, so basically `command.rs:1456` is not incorrectly interacting with its uniforms context, but the uniforms context it gets passed is faulty to begin with, if...

There's quite a few shaders involved so I'll post just the comparison for the smallest shader, and another one for the one shader I definitely know to be involved in...

And here's `xy_uv_translate.vert` (the one definitely involved in the error context) in its **original** form: ```vert #version 450 layout (push_constant) uniform Translation { vec2 vector; } translation; layout (set =...

> This looks wrong. The binding code will look for something at offset 8, while populating the uniforms starting with offset 0, which means the `code` will be registered at...

I have another suspicion, that maybe although `shaderc` and `SPIRV-Cross` do not complain about my shader definitions, something about them makes the latter trip up: If one of my **vertex**...

Or in other words, could it be that for SPIRV-Cross to make sense of this I have to explicitly account for the `4` bytes at offset `8` as well (e.g....

I see, thanks for the explanation! I have somewhat of an idea what's the issue and thanks to your last comment also where to look. I can offer to play...