From: Henri Verbeet <hverbeet@gmail.com>
Subject: Re: [PATCH] d3d12: Check for VK_KHR_external_fence_capabilities before using VkPhysicalDeviceIDProperties.
Message-Id: <CAOsNvwxQKv7s506JfJpYC6=bXUTqr0-FXrUm7YBOa05tT_3Ouw@mail.gmail.com>
Date: Thu, 25 Feb 2021 13:05:39 +0100
In-Reply-To: <20210224205842.591939-1-z.figura12@gmail.com>
References: <20210224205842.591939-1-z.figura12@gmail.com>

On Wed, 24 Feb 2021 at 21:59, Zebediah Figura <z.figura12@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.