Arch Linux User Repository

To enable DXVK in a wineprefix, do the following (with the WINEPREFIX variable properly set):

setup_dxvk install

In order to uninstall DXVK from a wineprefix:

setup_dxvk uninstall

Hi, is there a reason that this package installs dxvk with the new --without-dxgi flag enabled by default? Or rather, I do understand the reason somewhat (probably so it can work out of the box without breaking synergy with vkd3d, dxup et al) but it's actually not really recommended by the developer because it breaks (or at least underperforms in) many games, especially when one's using an nvidia card. And even worse is that I can't see any way of installing WITH dxgi without modifying the provided script and removing the flag.

I think it'd be preferable if users could choose to install with or without dxgi themselves; maybe by creating a flag in your own script (e.g. --dxgi) which if present would serve to disable the --without-dxgi flag of the upstream script, which could then remain the default as it is now.

@ssorgatem Thanks for your help. have the old setup methode use for now.

then the setup script should work when using the non-proton wine, and then you can go back to using proton's wine

"WINEPREFIX="/EXTRA/.steam/steamapps/compatdata/271590/pfx" wine winepath -u 'C:\windows\system32'"

brings

"/EXTRA/.steam/steamapps/compatdata/271590/pfx/dosdevices/c:/windows/syswow64"

@damachine have you tried using it with non-proton wine on a proton prefix?

The older scripts had many limitations which this script solves (like being able to uninstall, for example). It also relied on winetricks and a winetrick verb... which I'm not too fond on mantaining.

But you are free to use an older version of this package, but replacing the DXVK files...

You can also just manually set it up; it's just symlinking or copying a couple files.

In any case, Proton should include this version of DXVK in a short time.

And last time I tried, whenever I started a game with Proton, it overwrote the manually installed DXVK with its own... so little point with the setup script supporting that.

@ssorgatem Is it possible to use the old setup script as a lagacy setup methode like setup_dxvk_legacy.sh that works for proton use. sorry that i repeat when it works before so fine.

@damachine the setup script won't work with proton's wine, because proton's wine is missing some parts in which it relies.

Try using your system's wine, it should work that way.

Yes, the old method worked 2 days ago.... but now there's a new setup script, which requires wine to work (actual wine, not just the part of wine that proton has).

@ssorgatem i use steam beta with proton last beta of proton is installed i think its a wine 3.16 i see with protontricks under winecfg. local i have installed wine-staging 4.2-1 from arch repo with some prefix with dxvk. the old install methode works 2 days before from the dxvk-master git clone.

@damachine that means either your WINEPREFIX or your wine installation are missing parts of wine, that is, winemenubuilder.exe

What wine are you using? I don't think it's going to work with the one from Proton.

@ssorgatem the command brings me "wine: cannot find L"C:\windows\system32\winemenubuilder.exe" wine: configuration in '/EXTRA/.steam/steamapps/compatdata/271590/pfx' has been updated. /EXTRA/.steam/steamapps/compatdata/271590/pfx/dosdevices/c:/windows/syswow64" i have test it with a non steam prefix i become the same. thanks for your work