https://bugs.winehq.org/show_bug.cgi?id=43935
--- Comment #71 from oscarbg rtfss1@gmail.com --- (In reply to winebugs from comment #67)
FWIW this is what I get on an Intel HD Graphics 530 (Skylake GT2) with mesa 17.2.2 on Fedora 26:
trace:vulkan:vkEnumerateInstanceExtensionProperties ((nil), 0x5b04980, (nil)) trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xcb_surface" for VK_KHR_win32_surface support trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xlib_surface" for VK_KHR_win32_surface support trace:vulkan:vkEnumerateInstanceExtensionProperties ((nil), 0x5b04980, 0x6763be0) trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xcb_surface" for VK_KHR_win32_surface support trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xlib_surface" for VK_KHR_win32_surface support trace:vulkan:vkCreateInstance (0x5b04a00, (nil), 0x1438df6c0) trace:vulkan:convert_VkInstanceCreateInfo (0x5b04840, 0x5b04a00) trace:vulkan:convert_VkAllocationCallbacks (0x5b04810, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) trace:vulkan:release_VkInstanceCreateInfo ((nil), 0x5b04840) trace:vulkan:vkEnumeratePhysicalDevices (0x7f04580d63a0, 0x5b04ac8, (nil)) trace:vulkan:vkEnumeratePhysicalDevices (0x7f04580d63a0, 0x5b04ac8, 0x66a6770) trace:vulkan:vkEnumerateDeviceExtensionProperties (0x7f045807c0f0, (null), 0x5b04400, (nil)) trace:vulkan:vkEnumerateDeviceExtensionProperties (0x7f045807c0f0, (null), 0x5b04400, 0x6763be0) trace:vulkan:vkGetInstanceProcAddr (0x7f04580d63a0, "vkGetPhysicalDeviceProperties2KHR") trace:vulkan:vkGetPhysicalDeviceProperties2KHR (0x7f045807c0f0, 0x5b04710) trace:vulkan:vkGetPhysicalDeviceProperties (0x7f045807c0f0, 0x5b04720) trace:vulkan:vkGetPhysicalDeviceMemoryProperties (0x7f045807c0f0, 0x1438df6d8) trace:vulkan:vkGetPhysicalDeviceFeatures (0x7f045807c0f0, 0x1438dfc38) trace:vulkan:vkGetPhysicalDeviceQueueFamilyProperties (0x7f045807c0f0, 0x5b04ac0, (nil)) trace:vulkan:vkGetPhysicalDeviceQueueFamilyProperties (0x7f045807c0f0, 0x5b04ac0, 0x66a6970) trace:vulkan:vkCreateDevice (0x7f045807c0f0, 0x5b04510, (nil), 0x1438df6c8) trace:vulkan:convert_VkAllocationCallbacks (0x5b042e0, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) trace:vulkan:vkDestroyDevice ((nil), (nil)) trace:vulkan:convert_VkAllocationCallbacks (0x5af9360, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) trace:vulkan:vkDestroyInstance (0x7f04580d63a0, (nil)) trace:vulkan:convert_VkAllocationCallbacks (0x5af9360, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil))
just posted on my twitter that to one of the Wolf2 devs (slightly edited):
Wolfenstein 2 runs via Wine with Nvidia propietary driver, AMDGPU Pro Vulkan driver and Mesa RADV Vulkan.. and even on Intel HD 530 GPU on Windows but not with Anvil Vulkan Mesa drv.. making a diff of VK features (using vulkan.gpuinfo DB) by drv seems Wolf2 requires variableMultisampleRate unconditionally?
so as said doesn't run on Intel Vulkan Mesa drv (Anvil).. will be nice to know what feature Anvil is missing vs RADV that allows it to run.. as said seems variableMultisampleRate is that missing feature that all others drivers present.. just wanting to request to mesa devs implement that if that's the missing feature missing..
thanks..