Hello, Yes, this is expected. There is a reason that the supported Vulkan version is hardcoded.
Newer Vulkan versions introduce new features and structures that we often cannot simply support with our existing tooling. In this case one structure can recursively chain to itself, and we cannot simply support that without additional effort. Regarding debian/patches/generate/vulkan.patch: * I would, first and foremost, strongly urge Debian to revert those changes, and instead use the vk.xml version that Wine is actually capable of processing. * If the build system cannot allow downloading, you will need to find a way to make the right vk.xml version ahead of time and pin it. Trying to use a later vk.xml will fail for this and other reasons. * In this case you do not need to patch make_vulkan. As running the script with --help demonstrates, you can instead use the -x and -X arguments from the compilation script to pass existing vk.xml and video.xml files. * Instead of manually adding #include statements, you should specifically download and pass the video.xml file. Wine's Vulkan infrastructure cannot simply use system headers, and headers are not the only thing we generate anyway. This is no less true of video.xml than it is of vk.xml. --Zeb
