Arch Linux User Repository

This package contains three patches which are not applied by default. Feel free to read the documentation inside the PKGBUILD on what they do and how to enable them.

Don't report issues with these patches enabled to the dxvk creator before posting here. If you do, please be aware that they will probably close your issue nevertheless.

@katt actually disabling lto was correct nonetheless as dxvk is unhappy with it performance-wise, at least the last few times I tried it (it was months, maybe a year ago).

You are correct, issues with these flags manifest in wine too, but for some reason, while they are the new makepkg.conf defaults, they have not made it in the makepkg.conf for building in a chroot. Probably I will hard-code some sane flags for it in the PKGBUILD similar to the ones used by proton.

Terribly sorry for the confusion, but it seems it wasn't LTO after all, but rather the new CFLAGS in makepkg.conf:

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
        -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security \
        -fstack-clash-protection -fcf-protection"

Seemingly everything in the 2 last rows makes x86_64-w64-mingw32-gcc unhappy, but building with LTO + -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions works. Not sure how I came to my previous conclusion.

Thanks for pointing it out. I don't build with lto, I would have missed it.

Doesn't compile with LTO, please add options=(!lto) or something similar.

==> Starting build()...
The Meson build system
Version: 0.58.0
Source dir: /build/dxvk-mingw/src/dxvk
Build dir: /build/dxvk-mingw/src/build/x64
Build type: cross build
Project name: dxvk
Project version: v1.8.1

dxvk/meson.build:1:0: ERROR: Compiler x86_64-w64-mingw32-gcc can not compile programs.

A full log can be found at /build/dxvk-mingw/src/build/x64/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /var/lib/aurbuild/x86_64/katt/build

Actually I just found a more pressing issue. The build doesn't seem to work. While trying to run it for the first time, I get:

info:  Required Vulkan extension VK_KHR_get_physical_device_properties2 not supported
info:  Required Vulkan extension VK_KHR_surface not supported

The only info I could find suggests not having all required drivers installed, that's not the case here. I have used DXVK for months, it's not that my gpu doesn't support it. Titanfall 2, the game I'm trying to run, has always used DXVK as well.

This package contains three patches which are not applied by default. Feel free to read the documentation inside the PKGBUILD on what they do and how to enable them.

Don't report issues with these patches enabled to the dxvk creator before posting here. If you do, please be aware that they will probably close your issue nevertheless.

That is the reason they are commented. They might work or they might need rebasing. Thank you for reporting it though, if I can find a proper version I will update it. I hope you have read the warning about async.

Applying the mango hud patch by uncommenting the patch line in the PKGBUILD causes an error

EDIT: Commenting out the HUD patch but leaving in the async patch builds without error, so it does seem to be an error with the HUD patch/PKGBUILD, but I don't know enough about patching to debug it. Here is the error when trying to use the patch:

 ==> Starting prepare()...
patching file meson.build
Hunk #1 succeeded at 103 (offset 2 lines).
patching file src/dxvk/dxvk_context.cpp
Hunk #1 succeeded at 570 (offset -36 lines).
Hunk #2 succeeded at 2606 (offset 173 lines).
Hunk #3 succeeded at 3837 (offset 185 lines).
Hunk #4 succeeded at 4093 (offset 124 lines).
Hunk #5 succeeded at 4114 with fuzz 1 (offset 126 lines).
Hunk #6 succeeded at 4348 with fuzz 2 (offset 138 lines).
Hunk #7 succeeded at 4799 with fuzz 1 (offset 329 lines).
patching file src/dxvk/dxvk_context.h
Hunk #1 succeeded at 1159 (offset 18 lines).
Hunk #2 succeeded at 1217 with fuzz 2 (offset 37 lines).
patching file src/dxvk/dxvk_graphics.cpp
Hunk #1 succeeded at 41 (offset -34 lines).
Hunk #2 succeeded at 60 (offset -34 lines).
Hunk #3 succeeded at 70 (offset -34 lines).
patching file src/dxvk/dxvk_graphics.h
Hunk #1 succeeded at 185 (offset -62 lines).
patching file src/dxvk/dxvk_image.h
Hunk #1 succeeded at 453 (offset 11 lines).
Hunk #2 succeeded at 492 (offset 11 lines).
patching file src/dxvk/dxvk_options.cpp
Hunk #1 succeeded at 5 with fuzz 2.
patching file src/dxvk/dxvk_options.h
Hunk #1 succeeded at 10 with fuzz 2.
patching file src/dxvk/dxvk_pipecompiler.cpp
patching file src/dxvk/dxvk_pipecompiler.h
patching file src/dxvk/dxvk_pipemanager.cpp
Hunk #1 succeeded at 10 (offset -35 lines).
patching file src/dxvk/dxvk_pipemanager.h
Hunk #2 succeeded at 96 (offset -12 lines).
patching file src/dxvk/meson.build
Hunk #1 succeeded at 83 (offset 1 line).
patching file README.md
Hunk #1 succeeded at 1 with fuzz 1.
patching file src/dxvk/dxvk_cpu.h
patching file src/dxvk/hud/dxvk_hud.cpp
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 60.
Hunk #3 FAILED at 82.
3 out of 3 hunks FAILED -- saving rejects to file src/dxvk/hud/dxvk_hud.cpp.rej
patching file src/dxvk/hud/dxvk_hud.h
Hunk #1 succeeded at 24 with fuzz 2 (offset -5 lines).
can't find file to patch at input line 335
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:


|diff --git a/src/dxvk/hud/dxvk_hud_config.cpp b/src/dxvk/hud/dxvk_hud_config.cpp
|index fe1745bd..020a394b 100644
|--- a/src/dxvk/hud/dxvk_hud_config.cpp
|+++ b/src/dxvk/hud/dxvk_hud_config.cpp

File to patch: