Assertion failure when only some ICDs have VK_KHR_surface support about vulkan-loader HOT 4 CLOSED

Looking into this issue (after it was assigned to me), this is definitely a valid issue.
Applications have no way to tell if the physical device they have will support functions VK_KHR_surface due to how instance extensions will be reported as supported when at least one ICD supports.
Unfortunately, this is not something that can be fixed very easily and requires an overhaul to the instance/physical device extension interface to support knowing which ICD supports what.

An alternative idea is to implement the logic necessary for the function, ie doing the ICD's job if the ICD doesn't support hte extension, but that is a can of worms in its own right.

from vulkan-loader.

This should be migrated to Vulkan-Docs, as there is nothing the Vulkan-Loader can do to fix this that doesn't require a new extension first.

from vulkan-loader.

After further inspection, while there may be a vulkan docs issue to create, the loader should proactively check if the extension is supported on the ICD before calling down into it.

from vulkan-loader.

In the pending autogen changes, we now have the ability to check this by modifying loader/wsi.c line 359 to:

    if (!icd_term->scanned_icd->inst_ext_support.khr_surface ||
        NULL == icd_term->dispatch.GetPhysicalDeviceSurfaceFormatsKHR) {

from vulkan-loader.