Battlefield 4, have issues going fullscreen due to DXGI Error

doitsujin / dxvk

Vulkan-based implementation of D3D8, 9, 10 and 11 for Linux / Wine

zlib License

13.19k stars 851 forks source link

Battlefield 4, have issues going fullscreen due to DXGI Error #1081

Closed Alexithymia2014 closed 5 years ago

Alexithymia2014 commented 5 years ago

I've been experiencing crash errors when Battlefield 4 goes fullscreen after clicking into it. It starts up windowed mode. The DXGI Error I receive is: https://i.imgur.com/riAwHKr.png

I've tried all different versions of DXVK (ranging from 0.90 to 1.2.1) and Wine ranging from 3.16 to 4.9 (anything above 4.6 crashes Origin which is not related I don't think).

It looks to be related to issue #153 but I thought that was merged in and fixed?

Software information

Battlefield 4 (and possibly 1, and V)

System information

GPU: AMD Radeon RX 580
Driver: Mesa 19.0 with LLVM 8.0 but also tried mesa-git and LLVM 9.0 svn on Arch Linux
Wine version: Tried different ones between 3.16 and 4.6 (anything above 4.6 crashes Origin)
DXVK version: Different versions 0.90 through 1.2.1

K0bin commented 5 years ago

Please record an apitrace so we can actually reproduce the issue.

doitsujin commented 5 years ago

Can you at least post the dxvk logs? Also, what are your display settings in game (resolution, refresh rate, ...)?

And yes, an apitrace would indeed be very helpful (even with dxvk enabled; just make sure to set the DLL overrides to native,builtin). Fullscreen mode has been working fine on my system just fine in BF1 and the open beta of BF5.

Alexithymia2014 commented 5 years ago

Hi,

Thanks for the response, I ended up fully reinstalling it through Lutris and it worked fine which I found a little bizarre. The settings were 2560x1440 at 144Hz. If it happens again I'll open a new issue with an apitrace if I can figure that out with Origin running and and the d3d11 log. The d3d11 log was rather sparse when I checked it last.

K0bin commented 5 years ago

The d3d11 log was rather sparse when I checked it last.

The dxgi log is the thing thats relevant here. (do post the d3d11 log as well though). And make sure its the games log, not the one created by origin.

doitsujin commented 5 years ago

The settings were 2560x1440 at 144Hz.

It's possible that wine doesn't enumerate the display modes correctly; wouldn't be the first time this happens (especially with 144 Hz displays). Unfortunately that's not something I can fix in DXVK.

Alexithymia2014 commented 5 years ago

I see, I regret opening this issue then! I'll keep an eye out for high refresh rates with any future games. Should I file a bug with Wine then if it doesn't already exist?

pchome commented 5 years ago

@doitsujin

Unfortunately that's not something I can fix in DXVK.

prelude

Since it is possible to use Wine's own DXGI implementation instead of the one provided by DXVK, more things going out of DXVK control, but Wine also have similar settings(via registry).

I'm not sure if those settings can be translated directly from the dxgi. configuration options, but the following ones looks like replacements:

VideoMemorySize for dxgi.maxDeviceMemory or dxgi.maxSharedMemory
VideoPciDeviceID/VideoPciVendorID for dxgi.customDeviceId/dxgi.customVendorId (dxgi.nvapiHack)

You could at least mentioned them on Wiki page, if it's true.

144 Hz displays


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Microsoft\DirectDraw] "ForceRefreshRate"=dword:00000090