DXVK, the Vulkan compatibility layer for Direct3D 11 and Wine has a fresh release reducing CPU overhead

Pompesdesky

cRaZy-bisCuiTThere is a Lutris script, for example for Battlefield 4.


On the other hand I don't get why people claim it's hard to install DXVK. It's actually, as mentioned before, pretty easy. Create a Wine Prefix and either install DXVK via script in that or just copy over the two DLLs. Nothing hard about that.

You just can't say that's easy. For any average Windows user for whom everything has always been just a double click away this can be a show stopper. Even for me that's not easy, I consider myself an advanced user as I used to handle Windows very well and have managed to game on Linux for more than 2 years now.

But when you say "create a Wine Prefix" I know that will require me to search the Web to find out how to do it, it'll most likely take me half an hour or more to understand and do that. Then I'll have to install DXVK via script, which again is not easier than a double click, and then again copy 2 DLLs and put them in a probably hidden folder.

Maybe you're in there for so long that you don't see why people claim some things are hard to do in Linux

Oh lord, please don't get me wrong, this message is not exactly targeted at you or someone specific, but as mentioned before it's easy. It will take you less than a minute. And if you consider yourself an advanced windows user, you should have knowledge about the cmd / power shell, thus not being afraid of the terminal. Even if you google for "How to create a wine prefix." the first result will already tell you. This will take you 5 minutes of googling on how to create one and maybe 5 more on how to make use of it.

Assuming you use a debian based distro (Debian, Ubuntu, some more...) open a terminal (CRTL + T) you could do it like this:

How to deploy a wine prefix & install DXVK

1. Create Wine-Prefix (64bit / x64 in this case)
WINEPREFIX="$HOME/.dxvk" wine wineboot

Note: The prefix is named "dxvk" like this. You could name it however you so desire.

2. Download dxvk-Release (0.42 in this case)
wget https://github.com/doitsujin/dxvk/releases/download/v0.42/dxvk-0.42.tar.gz

3. Extract the archive and change into the x64 directory
tar -xvf  dxvk-0.42.tar.gz && cd dxvk-0.42/x64/

4. Install dxvk in your desired Wineprefix
WINEPREFIX="$HOME/.dxvk" ./setup_dxvk.sh

At this point you are already done. Now you can execute e.g. .exe-files in this prefix:
WINEPREFIX="$HOME/.dxvk" wine BLAHBLAH.exe

If you don't want to type the prefix in all the time, just do:
export WINEPREFIX="$HOME/.dxvk"

...and as long as the terminal is open you will always refer to this prefix.

How to deploy a wine prefix & install DXVK in one command
WINEPREFIX="$HOME/.dxvk" wine wineboot && wget https://github.com/doitsujin/dxvk/releases/download/v0.42/dxvk-0.42.tar.gz && tar -xvf  dxvk-0.42.tar.gz && cd dxvk-0.42/x64/ && WINEPREFIX="$HOME/.dxvk" ./setup_dxvk.sh


...which will only take a few seconds.


Last edited by cRaZy-bisCuiT at 16 April 2018 at 11:42 pm UTC

cRaZy-bisCuiTOh lord, please don't get me wrong, this message is not exactly targeted at you or someone specific, but as mentioned before it's easy. It will take you less than a minute. And if you consider yourself an advanced windows user, you should have knowledge about the cmd / power shell, thus not being afraid of the terminal. Even if you google for "How to create a wine prefix." the first result will already tell you. This will take you 5 minutes of googling on how to create one and maybe 5 more on how to make use of it.

Assuming you use a debian based distro (Debian, Ubuntu, some more...) open a terminal (CRTL + T) you could do it like this:

How to deploy a wine prefix & install DXVK

1. Create Wine-Prefix (64bit / x64 in this case)
WINEPREFIX="$HOME/.dxvk" wine wineboot

Note: The prefix is named "dxvk" like this. You could name it however you so desire.

2. Download dxvk-Release (0.42 in this case)
wget https://github.com/doitsujin/dxvk/releases/download/v0.42/dxvk-0.42.tar.gz

3. Extract the archive and change into the x64 directory
tar -xvf  dxvk-0.42.tar.gz && cd dxvk-0.42/x64/

4. Install dxvk in your desired Wineprefix
WINEPREFIX="$HOME/.dxvk" ./setup_dxvk.sh

At this point you are already done. Now you can execute e.g. .exe-files in this prefix:
WINEPREFIX="$HOME/.dxvk" wine BLAHBLAH.exe

If you don't want to type the prefix in all the time, just do:
export WINEPREFIX="$HOME/.dxvk"

...and as long as the terminal is open you will always refer to this prefix.

How to deploy a wine prefix & install DXVK in one command
WINEPREFIX="$HOME/.dxvk" wine wineboot && wget https://github.com/doitsujin/dxvk/releases/download/v0.42/dxvk-0.42.tar.gz && tar -xvf  dxvk-0.42.tar.gz && cd dxvk-0.42/x64/ && WINEPREFIX="$HOME/.dxvk" ./setup_dxvk.sh


...which will only take a few seconds.

Thanks a lot for the detailed explanation, I'll try this tonight. Could help as I tried installing Lutris yesterday and something's wrong, altough I have Wine installed (checked in terminal via wine --version ^^) Lutris doesn't see it in the list of Wine runners.

When I say I'm an advanced user it's just that I'm able to look for solutions when I get into a problem, which average Joe won't bother doing, but when I find a solution I'm just stupidly copy/pasting what I found, I have no idea what the instructions you just gave exactly do for example. It's nearly black magic and I could as well paste a code telling my computer to wipe itself clean without knowing it

And by the way I don't Google for information as Google is more evil than Microsoft to me. I think any Linux user should use Qwant or other more privacy friendly search engines ;)

I do use ecosia most of the time, obviously this other very well-known search engine married the devil ages ago.

Have fun installing DXVK!

PS: I could really advice to start to think about what you do with your computer and why - one the one hand it will make your life much more easier, on the other hand you learn something about the system you use.


Also, there are many Wikis and tutorials, in addition, you can check what a command does with...

 man COMMAND

By the way, the best Ubuntu-Wiki I know is by Ubuntuusers.de - it's in German but I never found a better one.


Last edited by cRaZy-bisCuiT at 17 April 2018 at 10:09 am UTC

I tried it on Fedora 27 and didn't have any luck. The vulkaninfo just saying VK_ERROR_INCOMPATIBLE_DRIVER.
I know that the vulkan is working outside wine without any issue.
I also tried the wine-staging 3.5 build provided by lutris, but had the same output.

Pompesdesky

cRaZy-bisCuiTOh lord, please don't get me wrong, this message is not exactly targeted at you or someone specific, but as mentioned before it's easy. It will take you less than a minute. And if you consider yourself an advanced windows user, you should have knowledge about the cmd / power shell, thus not being afraid of the terminal. Even if you google for "How to create a wine prefix." the first result will already tell you. This will take you 5 minutes of googling on how to create one and maybe 5 more on how to make use of it.

Assuming you use a debian based distro (Debian, Ubuntu, some more...) open a terminal (CRTL + T) you could do it like this:

How to deploy a wine prefix & install DXVK

1. Create Wine-Prefix (64bit / x64 in this case)
WINEPREFIX="$HOME/.dxvk" wine wineboot

Note: The prefix is named "dxvk" like this. You could name it however you so desire.

2. Download dxvk-Release (0.42 in this case)
wget https://github.com/doitsujin/dxvk/releases/download/v0.42/dxvk-0.42.tar.gz

3. Extract the archive and change into the x64 directory
tar -xvf  dxvk-0.42.tar.gz && cd dxvk-0.42/x64/

4. Install dxvk in your desired Wineprefix
WINEPREFIX="$HOME/.dxvk" ./setup_dxvk.sh

At this point you are already done. Now you can execute e.g. .exe-files in this prefix:
WINEPREFIX="$HOME/.dxvk" wine BLAHBLAH.exe

If you don't want to type the prefix in all the time, just do:
export WINEPREFIX="$HOME/.dxvk"

...and as long as the terminal is open you will always refer to this prefix.

How to deploy a wine prefix & install DXVK in one command
WINEPREFIX="$HOME/.dxvk" wine wineboot && wget https://github.com/doitsujin/dxvk/releases/download/v0.42/dxvk-0.42.tar.gz && tar -xvf  dxvk-0.42.tar.gz && cd dxvk-0.42/x64/ && WINEPREFIX="$HOME/.dxvk" ./setup_dxvk.sh


...which will only take a few seconds.

Thanks a lot for the detailed explanation, I'll try this tonight. Could help as I tried installing Lutris yesterday and something's wrong, altough I have Wine installed (checked in terminal via wine --version ^^) Lutris doesn't see it in the list of Wine runners.

When I say I'm an advanced user it's just that I'm able to look for solutions when I get into a problem, which average Joe won't bother doing, but when I find a solution I'm just stupidly copy/pasting what I found, I have no idea what the instructions you just gave exactly do for example. It's nearly black magic and I could as well paste a code telling my computer to wipe itself clean without knowing it

And by the way I don't Google for information as Google is more evil than Microsoft to me. I think any Linux user should use Qwant or other more privacy friendly search engines ;)

Did you install the wine version via lutris or via command line it may explain why it cant see it

Pompesdesky

cRaZy-bisCuiTThere is a Lutris script, for example for Battlefield 4.


On the other hand I don't get why people claim it's hard to install DXVK. It's actually, as mentioned before, pretty easy. Create a Wine Prefix and either install DXVK via script in that or just copy over the two DLLs. Nothing hard about that.

You just can't say that's easy. For any average Windows user for whom everything has always been just a double click away this can be a show stopper. Even for me that's not easy, I consider myself an advanced user as I used to handle Windows very well and have managed to game on Linux for more than 2 years now.

But when you say "create a Wine Prefix" I know that will require me to search the Web to find out how to do it, it'll most likely take me half an hour or more to understand and do that. Then I'll have to install DXVK via script, which again is not easier than a double click, and then again copy 2 DLLs and put them in a probably hidden folder.

Maybe you're in there for so long that you don't see why people claim some things are hard to do in Linux

You are right if someone is coming from windows linux seems very complicated bc as you say they are used to double clicking and just pressing next when prompted. The closest linux gets to that are deb files but that is pretty much for basic productivity software rarely games.

Whitewolfe80You are right if someone is coming from windows linux seems very complicated bc as you say they are used to double clicking and just pressing next when prompted. The closest linux gets to that are deb files but that is pretty much for basic productivity software rarely games.

No, the closest Linux gets is installers of course. In fact I'd assume most new Linux gamers install their games through Steam nowadays, just as they did on Windows. For the rest, I think GOG has mojosetup-based graphical installers for all of their Linux releases, and itch has a client and so on. Which means you're still pretty much spreading FUD.

Remember, "Linux isn't like Windows" isn't the same as "Linux is complicated". That would make MacOS just as complicated, and ChromeOS as well. For basic users Linux is no harder than Windows. Of course, getting used to something new always takes time, especially if it's something non-trivial like an operating system. Even if you're switching to something better.

tuubiLinux is no harder than Windows.

In many cases it's even easier.

What's harder is people trying to run bleeding edge development code. But that stuff is not supposed to be easy.

Ehvis

tuubiLinux is no harder than Windows.

In many cases it's even easier.

What's harder is people trying to run bleeding edge development code. But that stuff is not supposed to be easy.

I'd say that's usually easier on Linux than Windows as well.

tuubi

Ehvis

tuubiLinux is no harder than Windows.

In many cases it's even easier.

What's harder is people trying to run bleeding edge development code. But that stuff is not supposed to be easy.

I'd say that's usually easier on Linux than Windows as well.

Well, it's harder than not having to do it.


Last edited by Ehvis at 18 April 2018 at 2:47 pm UTC