FFXIV poor performance outlier on new Radeon 9070 XT cards!?

[s32ialx]

I had a friend who owns a 9070 try this in-game today and he saw an increase from ~51 FPS to ~65 FPS in Limsa (1440p) - that is massive but no-where near the numbers claimed here. I also tried it with my trusty old 980Ti and for me it was slightly worse. In both cases a logfile was written confirming that Vulkan was used.

I then tried to run the same benchmark as described in the quoted post - stock and with DXVK - and noticed that with DXVK the benchmark tool would only render in a small window on my screen. Regardless of whatever window setting you set... resolution, windowed, fullscreen, it did not matter, it only renders into a small window. So that's likely where this > 2x uplift likely comes from(?)

I will also note that my friend very sadly is one of those dreaded plugin-users and that he saw no performance-lift whatsoever when he had the plugin-system enabled (both ~50fps).

So just to explain that yes it is in a small window but it's still rendering at the scale you set, as well because it's a window and not full screen not only is it rendering at the resolution you set but it's also having to do extra workload of drawing the desktop, taskbar and everything else open in the background... AND IT STILL PREFORMS BETTER. D: please square fix this.

And yes those magic users unless the people who made those magics update them to support the 9070 they will not see any stable uplift in performance

[selmon]

So just to explain that yes it is in a small window but it's still rendering at the scale you set, as well because it's a window and not full screen not only is it rendering at the resolution you set but it's also having to do extra workload of drawing the desktop, taskbar and everything else open in the background... AND IT STILL PREFORMS BETTER. D: please square fix this.

That is not true, you can set arbitrary resolutions, and the window it renders in will always be the same size and the benchmark result the same. The benchmark is just bugged with DXVK. It's also not the behaviour you get with regular DX11 on the benchmark.