| Git Clone URL: | https://aur.archlinux.org/dxvk-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | dxvk-bin |
| Description: | A Vulkan-based compatibility layer for Direct3D 9/10/11 which allows running 3D applications on Linux using Wine (Windows DLL binary files) |
| Upstream URL: | https://github.com/doitsujin/dxvk |
| Keywords: | dxvk |
| Licenses: | zlib/libpng |
| Conflicts: | d9vk, dxvk |
| Provides: | d9vk, dxvk |
| Submitter: | ssorgatem |
| Maintainer: | ssorgatem (kekonn) |
| Last Packager: | kekonn |
| Votes: | 229 |
| Popularity: | 1.44 |
| First Submitted: | 2018-03-02 07:39 (UTC) |
| Last Updated: | 2025-01-14 08:30 (UTC) |
With the recent changes in Wine, namely this commit, the packaged setup_dxvk script fails for regular wine too now, not only wow64. I am currently aware of two scripts that should work with current Wine, this is the one I use and this one from dxvk-msvc-git.
Feel free to use whichever you prefer, but please update it.
They are correct that the old upstream script doesn't work if wine has been built using the new wow64 wine mode. Feel free to take the updated script from dxvk-mingw AUR package.
@Piroro-hs the setup script is working as expected for me, both with and without the "--symlink" option. The x32 libraries are put in c:/windows/syswow64/
The setup_vxdk script plays poorly with wow64 wine. It copies x64 dlls to C:\windows\system32 then overwrite those with x32 dlls.
@Lili1228: should be fixed now
Please update setup_dxvk to include d3d8.dll that was added in 2.4.
@markboston, isn't it marked out of date because this is 2.3-1 not 2.3.1-1?
not sure why this was marked out of date. somehow i think the dates got messed up because 2.3.1 only just came out.
Proposal:
p̶k̶g̶b̶a̶s̶e̶, license: zlib-acknowledgement, source for setup_dxvk.sh (last commit before it got removed), 17->16, package_dxvk-bin -> package
@ssorgatem
The moment a change needs to be done to it (which will eventually come)
That script has largely remained the same for the lifetime of the dxvk project. There have been updates, some contributed by myself, but there all were improving robustness. None of them has changed the functionality itself. Given this history, I find it highly unlikely for it to require any change that isn't as simple as a sed command.
But it leads to code duplication between the several DXVK packages.
You are substituting a 2-line addition to 5 package, with the creation of a new package and the updating of the same 5 packages to list it as a dependency. Even if I don't elect to use that -common, because of fear that the maintainer of it might not respond in time when the aforementioned need for changes might occur, I will still need to update my packages to conflict with the -common package. Therefore I still believe it is unnecessary inconvenience and pollution.
-common packages in repos are usually reserved for larger size assets, not 5KiB scripts.
Pinned Comments
ssorgatem commented on 2018-03-27 06:47 (UTC) (edited on 2019-02-26 12:20 (UTC) by ssorgatem)
To enable DXVK in a wineprefix, do the following (with the WINEPREFIX variable properly set):
setup_dxvk installIn order to uninstall DXVK from a wineprefix:
setup_dxvk uninstall