Baldur Karlsson

Yes the reason for the `supportedExtensions` array is because any extensions not in that array will likely either crash on capture, crash on replay, or if you're lucky then work...

Yes the extension is supported as it's part of Vulkan 1.1 core, but the physical device feature is marked as not available meaning you can't use ycbcr samplers. This is...

I don't know, the application is then breaking the vulkan spec by using features that are reported as unavailable and haven't been enabled. As I mentioned above this may crash...

I've pushed support for ycbcr conversion samplers and displaying YUV textures (in D3D as well as Vulkan), which addresses part of what you were asking for. I don't know when...

External memory itself is already supported, but on replay it just creates an equivalent image without external memory properties so for the most part the only support needed is to...

As I mentioned before I haven't looked at the extension so I don't know what's involved with supporting it, if there's special handling needed in `vkCreateImage` then you will need...

Yes external memory images should get their contents saved as normal at the start of the frame. Any changes to the image within the frame won't be reflected as there's...

As I said if you have a repro where the YUV texture isn't displayed and it's not using `VK_EXT_image_drm_format_modifier` then please share it so I can debug it. I have...

In my test program yes I create separate image views for planar formats to texelFetch directly, though I do create a couple of samplers with ycbcr conversion enabled to test...

I double-checked for clarification, nothing about the `VK_EXT_image_drm_format_modifier` requires disjoint memory binding. The memory planes you mentioned are just the planar data in the image, it doesn't mean they must...