protonscr

DXVK 1.9.3 extremely poor performance on FFXIV

dxvkclosed
doitsujin/dxvk#2438 · opened 2022-01-15 by Raymyn · updated 2022-01-16 · 11 comments · github
RRaymyn 2022-01-15 github

When using DXVK 1.9.3 with Final Fantasy XIV, the game launches and is only able to run at 1-8 FPS with minimal CPU usage and 100% GPU usage. Running with 1.9.2 works flawlessly.

Visually comparing the log files between 1.9.2 and 1.9.3, I am only noticing the mention of info: DXGI: NvAPI workaround enabled, reporting AMD GPU as the difference. Everything else appears to be the same.

Software information

Game: Final Fantasy XIV

System information

  • GPU: NVIDIA RTX 3060 Laptop
  • Driver: 495.46.0
  • Wine version: 6.21
  • DXVK version: 1.9.3

Log files

I included both 1.9.2 and 1.9.3 log files for comparison.

Ddoitsujin maintainer 2022-01-15 github

Works flawlessly on my mobile 2060 as well as on my desktop, not sure what kind of problem you're having.

You seem to have d3d11.apitraceMode = True enabled, which shouldn't be causing such low performance but won't exactly help either, so please try disabling that.

I don't think there's a DXVK bug here but we'll need to at least figure out which change is causing the problem, so please bisect this if you can.

Visually comparing the log files between 1.9.2 and 1.9.3, I am only noticing the mention of info: DXGI: NvAPI workaround enabled, reporting AMD GPU as the difference. Everything else appears to be the same.

This did not change between the two releases, we've always reported Nvidia GPUs as AMD cards and the log message has always been there as well, unless you manually changed the configuration before.

RRaymyn 2022-01-15 github

Unfortunately, that setting was enabled after I noticed I had the issue. Was trying it per the recommendation of someone on a Discord I am part of. I attached the new log files below, with the setting disabled... Still extremely poor performance.
ffxiv_dx11_d3d11.log
ffxiv_dx11_dxgi.log

As for the error message, yeah, that's what I was told as well during troubleshooting, but that was the only discrepancies that I could see :(.

LLinuxDonald 2022-01-15 github

I have the same problem too with 1.9.3.
1.9.2 works.

I have an laptop with Intel gpu and nvidia 3060.

RRaymyn 2022-01-15 github

If I can figure out how to successfully install the mingw-w64 compiler on Fedora 35, I was going to try reverting commits. Since LinuxDonald has a 3060 as well, wonder if it is specific to the RTX 3060 Mobile and/or other 30-series cards?

RRaymyn 2022-01-16 github

So, interestingly, the issue for the extreme performance loss was the commit that implemented the fix for FFXIV.
[util] Shrink Nvidia HVV heap for Final Fantasy XIV

Removing this commit, FFXIV booted normally for me, with flawless performance on 1.9.3. I also tested setting dxvk.shrinkNvidiaHvvHeap = False in the dxvk.conf file, and FFXIV launched on the official released 1.9.3 without issue. Below is the attached logs for 1.9.3 with the override in the dxvk.conf file.

ffxiv_dx11_d3d11.log
ffxiv_dx11_dxgi.log

Ddoitsujin maintainer 2022-01-16 github

Weird, the game was working fine before Nvidia even had a HVV heap.....

I'm getting seriously annoyed with this, the game has extreme performance issues if we don't limit the HVV allocation size (#2210), and now on some other systems it has extreme performance issues if we do limit it. What the hell is going on here and what the absolute fuck am I supposed to do now?

Ddoitsujin maintainer 2022-01-16 github

Ah, wait a minute. Do you have resizeable BAR enabled?

If that works the same on Nvidia as it does on AMD then there's only one heap for your entire video memory and we're accidentally limiting that to 32 MiB. Derp.

Ddoitsujin maintainer 2022-01-16 github

Does https://github.com/doitsujin/dxvk/tree/hvv-rbar-fix resolve this? Build here (in progress at the time of writing).

RRaymyn 2022-01-16 github

Yep. That build does appear to work.
ffxiv_dx11_d3d11.log
ffxiv_dx11_dxgi.log

LLinuxDonald 2022-01-16 github

Thank you it works :)

Ddoitsujin maintainer 2022-01-16 github

Merged.

Nothing extracted yet.