Far Cry 4 sometimes hang during startup with dxvk

[Blisto91]

When launching Far Cry 4 with dxvk it will freeze between 1/3 - 1/2 of the time at the loading screen before the company logos.
Launching with WINED3D i was able to get to the main menu each of the around 25 times i tried.

Software information

Far Cry 4 steam

System information

• GPU: AMD R9 380
• Driver: mesa 22.1.1
• Wine version: Proton 7.0-2 & 7.0-3RC
• DXVK version: 1.10.1, master and every other older versions I've tried back to 1.5

Apitrace file(s)

I was trying to get a couple API traces with dxvk both where it would freeze and where it wouldn't but the game wouldn't start with it.
If you think a WINED3D or windows trace will have value for this then i will make one.

Log file

FarCry4_d3d9.log
FarCry4_d3d11.log
FarCry4_dxgi.log

These are from a time where it froze.

Edit: i do realize #2666 is with the same game, but i'm not really sure it's the same issue so made a new one for now.

[LeSmoothOperator]

It might be the same issue I encountered with Warband. Just need to limit the VRAM recognized by DXVK by adding/editing this line in dxvk.conf:

d3d9.maxAvailableMemory = x
d3d9.memoryTrackTest = True

Fill x with your dedicated VRAM if using dGPU or shared VRAM if using iGPU (do not use dedicated + shared).

[LeSmoothOperator]

For d3d11, I did not see the setting to do it. For dxgi, I saw:

dxgi.maxDeviceMemory = x
dxgi.maxSharedMemory = x

which you can try to change the values accordingly. I did not have the chance to try it out.

[LeSmoothOperator]

For the general settings outside VRAM, just change them to a more generally compatible option for most games. For example, dxgi.deferSurfaceCreation = True and/or d3d11.dcSingleUseMode = False.

[Blisto91]

It's not the same issue but thanks for the input 😁

I have already tried all conf settings and asked the devs in the discord if i might be missing anything. Just making the issue so it isn't forgotten.

[LeSmoothOperator]

Ok, all good.

[Blisto91]

Made a mesa issue. Updated findings can be read there https://gitlab.freedesktop.org/mesa/mesa/-/issues/7050

Tho this could still just be some weird dxvk or game bug.

[Blisto91]

Closing this as i still believe it is likely some weird driver issue.