Quoting: ShmerlIs that correct? HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NodeKhronos\Vulkan\Drivers
Looks like it should be HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Khronos\Vulkan\Drivers

Also, using "C:\Windows\winevulkan.json" doesn't work with regedit. You need to use "C:\\Windows\\winevulkan.json"

Anyway, I built wine-vulkan as above, but no dice.

For me C:\Windows\winevulkan.json worked. And HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Khronos\Vulkan\Drivers is the correct one. I also compiled wine-vulkan with the same scripts you gave me for the wine staging. I just added the step to run autoconfig as in AUR PKGBUILD.

Quoting: hilparaFor me C:\Windows\winevulkan.json worked. And HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Khronos\Vulkan\Drivers is the correct one. I also compiled wine-vulkan with the same scripts you gave me for the wine staging. I just added the step to run autoconfig as in AUR PKGBUILD.

Yep, I used same scripts. Something is off though, possibly because I'm building inside a VM which has no vulkan installed.

Which Vulkan SDK did you install inside your prefix?

Anyway, the whole thing is a hack, and they probably didn't account for various use cases. Vulkan patches are progressing in Wine master, so hopefully it won't take long.

Ah. I see some problem in the configure step:

checking for -lvulkan... not found

I suppose it requires vulkan dev package?

Yep, this time it worked!

For the reference, when building wine-vulkan, make sure you have libvulkan-dev installed. Trying TW3 with dxvk now.

Ah, no. That wasn't the reason. Somehow running setup_dxvk.sh messes up the prefix. Before running it, vulkaninfo.exe works. Afterwards - not anymore.

Something must have messed up with my startup scripts. I reconfigured the prefix to use wine-vulkan, and now the result for d3d11-triangle.exe is like this:

info:  AMD RADV POLARIS10 (LLVM 6.0.0):
info:    Driver: 18.0.99
info:    Vulkan: 1.1.0
warn:  DxgiAdapter: DXGI_FORMAT_D24_UNORM_S8_UINT -> VK_FORMAT_D32_SFLOAT_S8_UINT
info:  D3D11CreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info:  D3D11CreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
warn:  Vulkan extension VK_KHR_maintenance2 not supported
info:  Enabled device extensions:
info:    VK_AMD_rasterization_order
info:    VK_KHR_maintenance1
info:    VK_KHR_shader_draw_parameters
info:    VK_KHR_swapchain
0009:err:d3dcompiler:compile_shader HLSL shader parsing failed.
Failed to compile vertex shader

VK_KHR_maintenance2 is supported by my radv for the reference.

It also has a lot of errors like:

0009:fixme:vulkan:wine_vkGetInstanceProcAddr Unsupported device or instance function: '"vkEnumeratePhysicalDeviceGroups"'

Do you have the necessary dlls? d3dcompiler_47.dll (and at least on my system I need cryptsp.dll too)

Ah, I see it's only needed for those demos. TW3 is starting now without it! Thanks for the hint.

You need the DLLs for the triangle sample. DXVK itself works without those DLLs.

Quoting: ScmerlVK_KHR_maintenance2 is supported by my radv for the reference.

RADV does, but wine-vulkan doesn't (yet). Unlike the old wine-staging code, wine-vulkan is actually smart enough to filter out any extension that it can't deal with, and sadly it has to deal with every single one of them explicitly due to differences in struct memory layouts between Windows and Linux.

Performance is similar to Wine with old buffer pool hack (i.e. GPU must be fully loaded):



Unlike OpenGL backend though, there are way more microstutters (I guess less of live shader caching is going on).

The water effects are messed up still. But very impressive progress overall.