Chip Davis

That's probably because MoltenVK doesn't support Vulkan 1.3 yet. We're still working on that; see #1930. Perhaps the better question is: why *weren't* you getting a validation error before? It...

> * Not sure I like this that much I don't like it either, considering that the whole point of the new memory requirements functions is that you *don't* have...

> I am sorry for the question, but what exactly is meant by the "name equal to the basename of the DLL"? In Windows (and DOS and OS/2) jargon, the...

> * Images with transient usage (so lazily allocated memory) seem to have different memory types depending on the image usage flags. (one has `INPUT_ATTACHMENT_BIT`, while the other has `COLOR_ATTACHMENT_BIT`)...

While I'm pretty sure Metal already has support for hardware-accelerated video encoding/decoding, until Apple exposes it publicly, there isn't much I think we can do until then.

Actually... we might be able to use the VideoToolbox framework to support this.

> Any chance to push this forward? It's held up on KhronosGroup/SPIRV-Cross#2204, and from what I've read lately, H-K probably thinks that's too invasive (i.e. it doesn't belong in SPIRV-Cross)....

So in other words, `vkCmdBindDescriptorSets()`. The Vulkan standard [says][1] only that, if a pipeline with a new layout is bound, and descriptor set *n* is then bound when there are...

What kind of AMD device? Some AMD devices support 32-invocation subgroups.

~~This is probably a bug in Metal.~~ ~~SPIRV-Cross translates `BuiltInSubgroupSize` (`gl_SubgroupSize` in GLSL) to Metal's `threads_per_simdgroup`. The wrong values of this parameter are thus coming from the Metal shader compiler...