I don't see a reason why this should be explicitly unsupported. We can pass it through to the host validation layers.
Signed-off-by: Georg Lehmann dadschoorse@gmail.com --- dlls/winevulkan/make_vulkan | 2 -- 1 file changed, 2 deletions(-)
diff --git a/dlls/winevulkan/make_vulkan b/dlls/winevulkan/make_vulkan index 72b0adf0c97..2ef44338d40 100755 --- a/dlls/winevulkan/make_vulkan +++ b/dlls/winevulkan/make_vulkan @@ -86,8 +86,6 @@ EXT_BLOCK_SIZE = 1000
UNSUPPORTED_EXTENSIONS = [ # Instance extensions - "VK_EXT_validation_features", - "VK_EXT_validation_flags", "VK_KHR_display", # Needs WSI work. "VK_KHR_surface_protected_capabilities",
I think this makes sense. Looking back through history in Git it appears that these lines were introduced when the list was inverted from explicitly supporting, to explicitly forbidding, extensions. It's probably the case that there wasn't explicitly a reason to forbid these extensions, but rather a lack of motivation to support them.
Signed-off-by: Liam Middlebrook lmiddlebrook@nvidia.com
On 10/31/20 1:12 PM, Georg Lehmann wrote:
I don't see a reason why this should be explicitly unsupported. We can pass it through to the host validation layers.
Signed-off-by: Georg Lehmann dadschoorse@gmail.com
dlls/winevulkan/make_vulkan | 2 -- 1 file changed, 2 deletions(-)
diff --git a/dlls/winevulkan/make_vulkan b/dlls/winevulkan/make_vulkan index 72b0adf0c97..2ef44338d40 100755 --- a/dlls/winevulkan/make_vulkan +++ b/dlls/winevulkan/make_vulkan @@ -86,8 +86,6 @@ EXT_BLOCK_SIZE = 1000
UNSUPPORTED_EXTENSIONS = [ # Instance extensions
- "VK_EXT_validation_features",
- "VK_EXT_validation_flags", "VK_KHR_display", # Needs WSI work. "VK_KHR_surface_protected_capabilities",