Search Criteria
Package Details: dxvk-bin 2.6.1-1
Package Actions
| 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.14 |
| First Submitted: | 2018-03-02 07:39 (UTC) |
| Last Updated: | 2025-04-23 19:55 (UTC) |
Dependencies (2)
- vulkan-icd-loader (vulkan-icd-loader-gitAUR)
- lib32-vulkan-icd-loader (lib32-vulkan-icd-loader-gitAUR) (optional) – 32-bit Windows application support
Required by (4)
- aio-creator-neo (requires dxvk)
- arch-gaming-meta (optional)
- dxvk-nvapi-mingw (requires dxvk)
- dxvk-nvapi-mingw-git (requires dxvk)
Sources (2)
UnicornDarkness commented on 2019-09-14 08:13 (UTC)
ssorgatem commented on 2019-06-17 20:56 (UTC)
@alexzk it behaves like upstream, which is, by default, it copies the DXVK libraries to your prefix, which means they are not automatically updated when you update the package.
If you want that, use the "--symlink" argument.
Namarrgon commented on 2019-06-15 16:58 (UTC)
$pkgdir needs to be quoted properly or the build will fail in directories that contain whitespace.
alexzk commented on 2019-06-10 21:45 (UTC)
Can you elaborate in pinned comment, if I must repeat 'setup_dxvk install' after package upgrade for each wineprefix i have, or it implies automatically. Because early 0.xx versions were doing copies of itself = need repeat.
grawity commented on 2019-05-25 21:31 (UTC)
The conflict with dxvk-bin<1.0-1 is redundant, as a package already cannot be co-installed with itself... however, it does cause trouble for AUR helpers which don't support versioned deps. It should probably be removed.
ssorgatem commented on 2019-04-16 14:33 (UTC)
No, putting $pkgdir there will break the link when installed.
That whole chmod line needs to be removed. It should be fixed now.
JIgnacioTG commented on 2019-04-16 06:57 (UTC)
I resolved the "chmod: cannot operate on dangling symlink 'setup_dxvk'" bug editing too the PKGBUILD file but adding the variable $pkgdir in the line of the symbolic link:
ln -s $pkgdir/usr/share/dxvk/setup_dxvk.sh "$pkgdir/usr/bin/setup_dxvk"
I don't know if this breaks something.
mallgrab commented on 2019-04-15 23:49 (UTC) (edited on 2019-04-15 23:50 (UTC) by mallgrab)
It cries about "chmod: cannot operate on dangling symlink 'setup_dxvk'"
Editing the PKGBUILD and adding "cd $pkgdir/usr/bin"
below "mkdir -p $pkgdir/usr/bin"
fixed the problem for me.
ssorgatem commented on 2019-04-07 16:01 (UTC)
The 1.1 release has been pulled out because it was buggy (reportedly caused GPU hangs), so this package hasn't included it.
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