[PATCH] d3d12: Check for VK_KHR_external_fence_capabilities before using VkPhysicalDeviceIDProperties.

[Joshua Ashton]

There is no reason to. This is core in Vulkan 1.1.

You should just use a newer API version.
There is no relevant driver that doesn't support this.

- Joshie 🐸✨

On 2/25/21 12:05 PM, Henri Verbeet wrote:
> On Wed, 24 Feb 2021 at 21:59, Zebediah Figura <z.figura12 at gmail.com> wrote:
>> @@ -331,6 +333,7 @@ HRESULT WINAPI D3D12CreateDevice(IUnknown *adapter, D3D_FEATURE_LEVEL minimum_fe
>>       };
>>       static const char * const optional_instance_extensions[] =
>>       {
>> +        VK_KHR_EXTERNAL_FENCE_CAPABILITIES_EXTENSION_NAME,
>>           VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2_EXTENSION_NAME,
>>       };
> I suppose this is fine, although as a principle I would prefer using
> the slightly older VK_KHR_external_memory_capabilities extension for
> this.
>