Found a significant bottleneck by the way. The game maps several images to host memory each frame, which currently forces a full CPU-GPU synchronization every single time. Not that easy to fix sadly, but I'll see what I can do.

Thing is, image mapping was already implemented properly in DXVK quite a while ago, but some games just ignore the returned row pitch and derp their data straight into the image memory with a single memcpy() call, which causes all sorts of trouble, so I decided to emulate it with a linear buffer. This works, but it's inefficient.

If I play the ESO with wine-pba (3.3) I have sound but also lot of graphic failures and I can't play it. (sorry about offtopic)

I think I found the problem. I don't have pulse-dev files installed. Just saw this in config.log:
configure:12707: checking pulse/pulseaudio.h usability
configure:12707: gcc -m64 -c -O3 -march=native   conftest.c >&5
conftest.c:175:10: fatal error: pulse/pulseaudio.h: No such file or directory
 #include <pulse/pulseaudio.h>
          ^~~~~~~~~~~~~~~~~~~~

Quoting: hilparaIf I play the ESO with wine-pba (3.3) I have sound but also lot of graphic failures and I can't play it. (sorry about offtopic)

I think I found the problem. I don't have pulse-dev files installed. Just saw this in config.log:
configure:12707: checking pulse/pulseaudio.h usability
configure:12707: gcc -m64 -c -O3 -march=native   conftest.c >&5
conftest.c:175:10: fatal error: pulse/pulseaudio.h: No such file or directory
 #include <pulse/pulseaudio.h>
          ^~~~~~~~~~~~~~~~~~~~

Hope you get that sorted soon :-)

I think I found my black screen issue. I was building Wine-Vulkan with 1.0.39, have now updated to 1.0.68 and recompiling. :)

Quoting: Avehicle7887

Quoting: hilparaIf I play the ESO with wine-pba (3.3) I have sound but also lot of graphic failures and I can't play it. (sorry about offtopic)

I think I found the problem. I don't have pulse-dev files installed. Just saw this in config.log:
configure:12707: checking pulse/pulseaudio.h usability
configure:12707: gcc -m64 -c -O3 -march=native   conftest.c >&5
conftest.c:175:10: fatal error: pulse/pulseaudio.h: No such file or directory
 #include <pulse/pulseaudio.h>
          ^~~~~~~~~~~~~~~~~~~~

Hope you get that sorted soon :-)

I think I found my black screen issue. I was building Wine-Vulkan with 1.0.39, have now updated to 1.0.68 and recompiling. :)

Sound works! :)

It seems I've hit a wall now, I've recompiled wine-vulkan against libvulkan-dev 1.0.68. Made a clean prefix, installed Vulkan SDK, applied the registry files and winevulkan.json and lastly I ran the dxvk_setup.sh.

Game launches, sound is ok but screen is black. Can anyone please share the correct procedure.

Ready compiled DXVK files from almost every commit: [DXVK builds](https://haagch.frickel.club/files/dxvk/)

I managed to fix the synchronization issue in the latest commits, the game should run significantly faster than before. At least it manages to saturate my RX 480 most of the time now.

Quoting: Avehicle7887Game launches, sound is ok but screen is black. Can anyone please share the correct procedure.

What do you get from running vulkaninfo.exe from that prefix with wine-vulkan? Also, what version of SDK did you install? I took the latest one (for Vulkan 1.1).

One thing to note. When running setup_dxvk.sh, you need to make sure it picks up both correct wine and correct prefix. Setting just prefix alone is probably not enough. You need to set environment correctly, so your wine-vulkan will be picked instead of system wine.

I was bitten by this, and nothing worked because of it. One way to fix it, is to run wine vulkan explicitly afterwards for your prefix with something like regedit, to make sure it updates the prefix to itself.

And of course, when launching the game, you need to set all needed Wine variables to wine-vulkan locations too.

Quoting: hilparaIs it possible to share the witcher installation with different wine prefixes?

You can probably symlink it, so yes. But it might use registry stuff as well. The easiest way is just to make a copy of the whole prefix. I decided not to bother and to experiment in the existing prefix. You can always uninstall Vulkan SDK, and remove dxvk overrides as well.

Quoting: YoRHa-2BI managed to fix the synchronization issue in the latest commits, the game should run significantly faster than before. At least it manages to saturate my RX 480 most of the time now.

Just built latest dxvk - definitely some improvement! I'm hitting 45 fps in some places (where before it was 40).

Quoting: YoRHa-2BI managed to fix the synchronization issue in the latest commits, the game should run significantly faster than before. At least it manages to saturate my RX 480 most of the time now.

I'm now maxing out my GPU with a 980ti at 1440p and medium/high settings, and getting around 60-90fps typically. Before it was maxing out at 89% gpu utilisation. It's still slower than Windows though, I'd guess around 80% of Windows, but very much playable.

Quoting: YoRHa-2BI managed to fix the synchronization issue in the latest commits

By the way, if I understand correctly, dxvk translates D3D11 into Windows Vulkan (so the need to install Vulkan SDK), which is then translated into Linux Vulkan. What is the point in translating it into Windows Vulkan first? Shouldn't it be less indirect to translate into Linux Vulkan right away?

Heh, just tired to build amdvlk for a test with dxvk. Here is the result:

Quoting: Shmerl

Quoting: Avehicle7887Game launches, sound is ok but screen is black. Can anyone please share the correct procedure.

What do you get from running vulkaninfo.exe from that prefix with wine-vulkan? Also, what version of SDK did you install? I took the latest one (for Vulkan 1.1).

One thing to note. When running setup_dxvk.sh, you need to make sure it picks up both correct wine and correct prefix. Setting just prefix alone is probably not enough. You need to set environment correctly, so your wine-vulkan will be picked instead of system wine.

I was bitten by this, and nothing worked because of it. One way to fix it, is to run wine vulkan explicitly afterwards for your prefix with something like regedit, to make sure it updates the prefix to itself.

And of course, when launching the game, you need to set all needed Wine variables to wine-vulkan locations too.

It seems I did everything correctly, the driver though was running Vulkan 1.0.49 which wasn't enough for the game, Updated to 390.25 and game ran instantly.

------------------------------------------------
It seems with DXVK even the lowest of systems will be able to play this game on Linux now :-)


1280x720 / Medium Settings / SSAO+Light Shafts on.

System:

Core 2 Quad Q6600 @ 2.7GHZ
Nvidia GT1030
4GB DDR2 Memory

GPU usage easily hit 100% / CPU peaked 85% Max.

HLSL support is actually the most useless thing ever for a translation layer because D3D doesn't use raw HLSL, it uses Microsoft's own bytecode format, DXBC. Kind of like Vulkan, you don't pass GLSL to the driver but pre-compiled SPIR-V bytecode.

I think HLSL support in Vulkan can be useful for source level ports, not for static binary translation.

@YoRHa-2B: Did you have a chance to test rotfiends with radeonsi? Do you get that freeze?

Guys, how to enable dxvk's hud?
I know I should use the DXVK_HUD = 1 command but I do not know where

Quoting: ChrupaasGuys, how to enable dxvk's hud?
I know I should use the DXVK_HUD = 1 command but I do not know where

Set the environment variable before launching the game. I launch it from the terminal, so for me it looks like:

DXVK_HUD=1 wine_dir=wine-vulkan ./the_witcher3.sh

But that uses a bunch of my own scripts inside. How are you launching the game?

Example of the above script:

the_witcher3.sh

#!/bin/bash

mesa=${mesa:-true} # use custom built mesa
hud=${hud:-false}  # use GALLIUM_HUD

export wine_dir=${wine_dir:-"wine-master"}
export mesa_dir=${mesa_dir:-"mesa-master"}

if $mesa; then
   mesa_run="mesa_run.sh "
fi

if $hud; then
   hud_run="gallium_hud.sh "
fi

export WINEPREFIX=/opt/games/wine/prefixes/witcher3
export mesa_glthread=true
export WINEDEBUG=-all

cd $WINEPREFIX/drive_c/the_witcher_3/bin/x64

${hud_run}${mesa_run}wine_run.sh witcher3.exe #&>wine_run.log

Here are the key scripts that are referenced above:

[wine_env.sh](https://gist.github.com/shmerl/a2867c5a675ed1795f03326b32b47fe7) - Environment setting script.
[wine_run.sh](https://gist.github.com/shmerl/edf230db5d4a24fd92aea16c31393d89) - Wine launcher that uses wine_env.sh.
[winetricks_run.sh](https://gist.github.com/shmerl/d7d56eed0c689531542124c705d18091) - winetricks launcher that uses wine_env.sh.
[mesa_run.sh](https://gist.github.com/shmerl/611b5b1670eb5963d0d99a4512ed8674) - script to use custom Mesa.

You can get the idea from it, how to run custom Wine + custom prefix + custom Mesa.