I guess something like this would make life much easier for people:
#!/bin/bash
printf "Please configure the intended environment variables to point to the right prefix!\n\t export WINEARCH=win32|win64 WINEPREFIX=\"/your prefix\"\n"
#Set dll redirection
wine reg add HKEY_CURRENT_USER\\Software\\Wine\\DllRedirects /v dxd11 /d dxd11_vk.dll /f
wine reg add HKEY_CURRENT_USER\\Software\\Wine\\DllRedirects /v dxgi /d dxgi_vk.dll /f
#Add dxvk library path to the prefix path
wine reg add HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Session\ Manager\\Environment /f /v PATH /d $(wine reg QUERY HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Session\ Manager\\Environment /v PATH | sed -n 's|^ *PATH *REG_EXPAND_SZ *C|z:\\usr\\lib\\dxvk\\lib;z:\\usr\\lib\\dxvk\\lib64;C|p')
OFC, there are checks that should be done before messing with the prefix registry, but if the environment is defined properly, this does the job, also replace the library path with yours in the sed pattern.
Sounds interesting. I'd recommend using a separate Wine prefix for this kind of stuff anyway so messing around with the registry should be okay. It's something I need to make clear in the README though.
If any of you want to build some sort of "setup" script I'd gladly accept it as a pull request.
I'm working on the script.
Setup script should work out of the box with 650170b1671e2a1049ac52d575e413388c2f13a4.
WINEARCH=win32|win64x1 2018-01WINEPREFIX=\"/yourx1 2018-01dxd11_vk.dllx1 2018-01dxgi_vk.dllx1 2018-01d3d11.dllx1 2018-01d3d11_vk.dllx1 2018-01
Hi, I was testing this out (just got black screens so far except for the triangle test).
I've found another way to have dlls load in wine, it's a little elaborate but guarantees dlls to load w/o copying them in the exec folder.
HKEY_CURRENT_USER\Software\Wine\DllRedirects\labelledd3d11with valued3d11_vk.dll. Likewise for dxgi.d3d11.dlltod3d11_vk.dll. Likewise for dxgi.HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment\PATH. You can add both 64 and 32 bit paths.