On Fri Jan 19 11:36:52 2024 +0000, Jan Sikorski wrote:
Ah, we should either also add `|| vk_info->api_version >= VK_API_VERSION_1_1` , or set the supported flag somewhere - in `wined3d_adapter_vk_init_d3d_info`? It's a little counter intuitive to me that those bits don't get set in `wined3d_adapter_vk_init_device_extensions` if they're core to our version..
Right. Initially I had made a patch for automatically marking extensions as supported if their core version was reached, but Zeb reminded me that it's not so easy: even if an extension is promoted to core, it might still be unsupported (except via a different flag) or need to be explicitly enabled. This is not the case of KHR_maintenance1, so I'll just add the check here.