Rua

> Wait, is continuing on failure the _**expected**_ behavior? It's what the script did before, at least. And there should be a way to skip over a problematic example so...

What that code is attempting to do, is figure out which display object belongs with the display handle that was returned from the `vkGetDisplayPlaneSupportedDisplaysKHR` API call. First it looks in...

As a way to confirm this, can you run your code with the Vulkan API dump layer enabled (via vkconfig or directly in your program)? Then specifically find the calls...

No, it's part of the Vulkan SDK.

An API dump of what your program is calling would be very helpful.

Ok, distilling out the important bits, the dump contains this sequence of calls related to displays: - `vkGetPhysicalDeviceDisplayProperties2KHR`. Returns 2 display handles `0xfab64d0000000002` and `0xfa21a40000000003`. - `vkGetPhysicalDeviceDisplayPlaneProperties2KHR`. Returns 6 display...

This error seems to happen when you present a swapchain and then submit a command buffer. You can probably work around it by waiting for a fence in between. Other...

I notice that quite a few of the types in the `video.rs` module have different names from their Vulkan counterparts. These should probably be renamed to match better. Also, am...

Vulkano doesn't expose those, but Ash (used by Vulkano) does. What do you need it for, though?

According to VUID-VkVideoSessionCreateInfoKHR-pStdHeaderVersion-07190, the extension name must match the one returned in the capabilities, and according to VUID-VkVideoSessionCreateInfoKHR-pStdHeaderVersion-07191, the spec version must not be greater than the one in the...