Quoting: hilparaI didn't have to set wine version when using setup_dxvk.sh. I just set the WINEPREFIX and run the script.

That probably just got lucky. I was bitten by exact same problem as above. And if you analyze the script - it doesn't set the environment, pulling whatever wine is in the path.

Then I have been lucky multiple times with different games :)

Quoting: hilparaThen I have been lucky multiple times with different games :)

That depends on your wine setup / location / path, and presence of multiple wines in the system, not on your prefixes. In my setup - it didn't work, until I set all the variables properly.

I'll probably write a patch for setup_dxvk.sh to address this.

Why should it even matter which version you have? It will copy and symlink the dlls and then it will set the libraries to be native overridden. Next time you launch the game with different wine version it will configure your prefix again but the override stays and so will the symlinks.

No luck shmerl. with wine-staging i did it like hilpara. now i ran your script (all envs set correct) and installed sdk 1.1.70 - nothing. new wineprefix - sdk 1.0.51 no luck. everytime the error with cube.exe i tried for test only wine-vulkan without dxvk and cant start it

Quoting: hilparaWhy should it even matter which version you have?

Because it can set wine version incorrectly, and subsequent run doesn't always detect it. So essentially the key part is to have correct wine version set in the prefix (which also creates all the needed dlls there).

Quoting: maspeberNo luck shmerl. with wine-staging i did it like hilpara. now i ran your script (all envs set correct) and installed sdk 1.1.70 - nothing. new wineprefix - sdk 1.0.51 no luck.

I'm using latest SDK - 1.1.70.1 and running it with Wine master and Mesa master. Though I doubt it's an issue.

ok what git do you exactly clone?

Quoting: maspeberok what git do you exactly clone?

Regular Wine master. Then dxvk (branch direct-image-mapping): https://github.com/doitsujin/dxvk/tree/direct-image-mapping

Wine master became usable this morning, so I doubt that would change the result.

Also, use Mesa master. And I saw you are building something for 32-bit. Skip all that. TW3 doesn't need it.

Quoting: Shmerl

Quoting: hilparaWhy should it even matter which version you have?

Because it can set wine version incorrectly, and subsequent run doesn't always detect it. So essentially the key part is to have correct wine version set in the prefix (which also creates all the needed dlls there).

What do you mean set wine version incorrectly? Where is this information saved? By looking the script, if I don't define my own wine with env it will use the system one to find the correct path to 'C:\windows\system32' and set the register, but that's it. It should not have anything to do with the dlls.

Can you please give me the git clone ...?

I used all time

git clone https://github.com/roderickc/wine-vulkan.git

Here is my build script

#!/bin/bash

# Builds wine-vulkan
# Notes:
#


base=${HOME}/Sources/wine-stuff
wine_branch=${wine_branch:-"master"}
wine_src=${base}/wine-vulkan/source
wine_build=${base}/wine-vulkan/build
arch=${arch:-"native"}

dest_dir="/opt/wine-vulkan/${wine_branch}"

export CXXFLAGS="-O3 -march=${arch}"
export CFLAGS="$CXXFLAGS"

function prepare() {
   mkdir -p "$wine_build"
}

function update_wine_sources() {
   cd $(dirname "$wine_src")
   git clone https://github.com/roderickc/wine-vulkan.git $(basename "$wine_src")
   cd "$wine_src"
   git reset --hard HEAD
   git clean -df
   git checkout master
   git pull
   git checkout ${wine_branch}
   if (($? != 0)); then
      echo "Invalid branch or tag ${wine_branch}! Aborting"
      exit 2
   fi
}

function configure() {
   rm -rfv ${wine_build}/*
   cd $wine_src
   autoconf # to make sure configure is up to date with the vulkan patches
   cd $wine_build
   ${wine_src}/configure --enable-win64 --disable-tests --prefix=
}

function build() {
   cd $wine_build
   make -j$(nproc)
   if (($? != 0)); then
      echo "Build failed!"
      exit 2
   fi
}

function publish() {
   cd $wine_build
   mkdir -p ${dest_dir}
   rm -rfv ${dest_dir}/*
   DESTDIR=${dest_dir} make -j$(nproc) install
}

############################################

prepare
update_wine_sources
configure
build
publish

Quoting: hilparaWhat do you mean set wine version incorrectly? Where is this information saved? By looking the script, if I don't define my own wine with env it will use the system one to find the correct path to 'C:\windows\system32' and set the register, but that's it. It should not have anything to do with the dlls.

When wine runs against certain prefix, it should detect if prefix was used before with other wine version. If so, it should reconfigure the prefix (you sometimes see that small window popping up in such cases), and during that it creates various dll files inside the prefix, which map to the wine version that's running. If that step happens with wrong wine version, and then next step somehow will fail to detect the change, you'll have a mess with those dlls.

At least that's what I think happened to me, when I had a bunch of similar problems to the above. See https://www.gamingonlinux.com/forum/topic/2753/post_id=1477

Quoting: maspeberCan you please give me the git clone ...?

I used all time

git clone https://github.com/roderickc/wine-vulkan.git

Regular wine master. See my build script: https://gist.github.com/shmerl/bbd448bc2b579831a82df7bae3de8dc5

Actual clone part:

git clone git://source.winehq.org/git/wine.git

wine-vulkan is not needed anymore.

I also put all my wine settings scripts there. Try using them if you want:

https://gist.github.com/shmerl/a2867c5a675ed1795f03326b32b47fe7
https://gist.github.com/shmerl/edf230db5d4a24fd92aea16c31393d89
https://gist.github.com/shmerl/611b5b1670eb5963d0d99a4512ed8674

For setting up dxvk, I use:

tw3_dxvk_enable.sh
#!/bin/bash

export WINEPREFIX=/opt/games/wine/prefixes/witcher3
export wine_dir=wine-master
source $HOME/bin/wine_env.sh

/opt/games/wine/dxvk/bin/setup_dxvk.sh

tw3_dxvk_disable.sh
#!/bin/bash

export WINEPREFIX=/opt/games/wine/prefixes/witcher3
export wine_dir=wine-master
source $HOME/bin/wine_env.sh

/opt/games/wine/dxvk/bin/setup_dxvk.sh reset

Since Wine 3.4, vulkan support should already work with dxvk.

Quoting: ShmerlSince Wine 3.4, vulkan support should already work with dxvk.

The Wine development release 3.4 is now available.
[https://www.winehq.org/announce/3.4](https://www.winehq.org/announce/3.4)

Btw
View video on youtube.com

Quoting: malek69Btw

How much VRAM do you have? It seems dxvk benefits greatly from more VRAM. And also, which branch of dxvk are you using?

@Shmerl Don't remember version dxvk, maybe this https://haagch.frickel.club/files/dxvk/r765.1bfd37a/64/bin/ or next

nvidia 750 ti 2 gb

You should be using specific dxvk branch which improves TW3 performance (a lot). See: https://github.com/doitsujin/dxvk/tree/direct-image-mapping