Warhammer End Times: Vermintide (235540)

[Zlopez]

Game is running with PROTON_NO_ESYNC enabled.

However if the resolution is changed to fullscreen you get black screen, but after killing the game and starting it again it works without issue.

System: Fedora 28 x86_64 GPU: GeForce GTX 960 Drivers: 396.54

[kek91]

Did you manage to actually play co-op online with real players?

I read a thread on reddit earlier stating it wouldn't work because of Easy AntiCheat, but playing with bots is fine if I recall correctly.

Vermintide 2 is the last game holding my main gaming rig on Windows, crossing my fingers to be able to migrate for good soon :)

[Zlopez]

Didn't tried online game. It is possible, that this isn't working, I will try it later today.

[Zlopez]

Today I finished one game with other player without any issue. Can confirm, that the online co-op is working.

[kek91]

Wow, that's fantastic. Thanks for your quick response!

[tingvarsson]

What part is it that needs esync disabled? Didn't need to add it when I tested it now. (unless overrides like these have been added elsewhere for known issues??)

[Zlopez]

@tingvarsson It depends what system are you using. I need this esync disabled for most games on Fedora. For more information try ulimit -a and look for Maximum number of open file descriptors. This value is only 1024 on Fedora and esync needs much more.

[tingvarsson]

@Zlopez Ahaa that's why. But like you say, then it isnt a game specific requirement (which NO_ESYNC sometimes is, i.e. games doesnt work properly with ESYNC at all). But rather a requirement for your system. Btw, suggest changing the value cause the gains from esync when working properly is wanted. :)

[kisak-valve]

@Zlopez, keep in mind, the hard limit for file descriptors is the value that matters for esync (ulimit -Hn), not the soft limit.

[Zlopez]

@kisak-valve Thanks for info, I wasn't sure about this. However it's still low on Fedora:

$> ulimit -Hn
4096

[kisak-valve]

There is a guide to increasing this limit at https://github.com/zfigura/wine/blob/esync/README.esync.

[Zlopez]

Thanks, but I already know how to increase this. I'm just waiting till Fedora do this in upstream.

[mati865]

@Zlopez it's probably going to take long time, see RHBZ#1338760 and RHBZ#1233595. You can file a new bug for Steam though, maybe it gets more attention.

[YellowOnion]

Is there a regression? I can't get my game to launch with v5.13-6

[kisak-valve]

Hello @YellowOnion, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[YellowOnion]

@kisak-valve hey sorry late reply: https://gist.github.com/YellowOnion/ca67b9069b834a5f70ce359d7a257810

[kisak-valve]

This looks like the line of interest from your log: err:module:import_dll Loading library DINPUT8.dll (which is needed by L"Z:\\home\\daniel\\.local\\share\\Steam\\steamapps\\common\\Warhammer End Times Vermintide\\binaries\\vermintide.exe") failed (error c0000020).

The library, dinput8, should be provided by Proton, so it's odd that the game doesn't see it.

On my system, there's <steamapps>/common/Proton 5.13/dist/share/default_pfx/drive_c/windows/system32/dinput8.dll and <steamapps>/common/Proton 5.13/dist/share/default_pfx/drive_c/windows/syswow64/dinput8.dll along with it being in per-game wineprefixes.

[YellowOnion]

Thanks for your help I think I solved the issue:

[eNTi]

The game crashes for me. Seems to be a known issue: https://www.protondb.com/app/235540

It is kind of pointless to even try to play the game if it crashes before the end and you lose all your progress in a map.

[WildPenquin]

There indeed are frequent crashes. The game is practically unplayable. If one is lucky, one might get trough one mission.

[WildPenquin]

The game is actually much more stable with PROTON_NO_FSYNC=1 (on many Proton versions). Should I ping #2922?

[p-himik]

It was crashing for me as well with out of memory errors - lowering the resolution and playing on the lowest settings has helped, even though I have more than a decent PC and the game with Proton never manages to load CPU/GPU to 100%.

The best performance for me seems to be when I run it with dxgi.nvapiHack = False in dxvk.conf, with Proton 6.3-8 or 6.8-GE-1, and via the launcher. The launcher seems to work only with those particular Proton versions - as long as you don't press Settings. Even mods seem to work just fine, and I was able to set the resolution to the native one and up the settings a bit.

Running it with kernel 5.15.0, RTX 2070S with proprietary driver 470, and with CPU governor set to performance.

[doogie544]

Not the point of my post but I will mention that the game was having random crashes for me with fsync enabled. I have not done enough testing yet to be sure but it looks like disabling fsync fixed the crashes.

Now to my point.

It would appear there is a bit of a regression in proton 7.0 for Vermintide.

If you use proton 6.3 you can launch the game using the launcher.

If you use proton 7 you must launch it with the option to "Run Without the Launcher"

The gameplay does not seem to be affected. (had random crashes on both with fsync enabled but the performance was the same)

System Information

``` Computer Information: Manufacturer: ASUSTeK COMPUTER INC. Model: TUF GAMING X570-PLUS Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: AuthenticAMD CPU Brand: AMD Ryzen 7 3800X 8-Core Processor CPU Family: 0x17 CPU Model: 0x71 CPU Stepping: 0x0 CPU Type: 0x0 Speed: 4909 Mhz 16 logical processors 8 physical processors HyperThreading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Supported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported AVX2: Supported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: "Arch Linux" (64 bit) Kernel Name: Linux Kernel Version: 5.17.1-arch1-1 X Server Vendor: The X.Org Foundation X Server Release: 12101003 X Window Manager: KWin Steam Runtime Version: steam-runtime_0.20220119.0 Video Card: Driver: AMD AMD Radeon RX 6800 XT (sienna_cichlid, LLVM 13.0.1, DRM 3.44, 5.17.1-arch1-1) Driver Version: 4.6 (Compatibility Profile) Mesa 22.0.0 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 144 Hz VendorID: 0x1002 DeviceID: 0x73bf Revision Not Detected Number of Monitors: 2 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 3840 x 1080 Primary Display Size: 20.91" x 11.77" (23.98" diag) 53.1cm x 29.9cm (60.9cm diag) Primary VRAM: 16384 MB ```

Mesa 22

[kisak-valve]

Hello @doogie544, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

[doogie544]

Hello @doogie544, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

I started the game in 6.3 and let the launcher open. I didn't start the game from the launcher as that would just add more lines to the log that are probably not relevant, and I know the game launches from the launcher just fine. I closed the launcher by the X on the launcher window, not by the stop button in Steam

I then switched to Proton 7 and tried to launch the game with the launcher option. I let the launcher fail and then waited about another 30 seconds past when the launcher should have appeared. I then used steam to kill the game with the stop button

Proton6.3.log

Proton7.0.log

I did not delete and recreate the prefix before switching between the 2 proton version as it did not make any difference last time.

I was trying to avoid having to reset all my settings again but if you need a log for proton 7 with a clean prefix I can do so.

I should also mention that as far as I can tell the only buttons that work on the launcher in 6.3 are the "Play" and the X in the top right corner to close the launcher. If you try to use any of the other buttons it will freeze completely and you have to close the game with the steam stop button. I didn't do that while the launcher was open in 6.3 as it might add additional log errors and make identifying the changes causing the issue in 7.0 harder to narrow down

[kisak-valve]

Thanks, some possible lines of interest from the log:

fixme:nsi:ipv6_forward_enumerate_all not implemented
[...]
fixme:wtsapi:WTSQuerySessionInformationW Unimplemented class 8
[...]
[00000218:] EXCEPTION handling: System.Net.WebException: The operation has timed out.

[doogie544]

Thanks, some possible lines of interest from the log:

fixme:nsi:ipv6_forward_enumerate_all not implemented
[...]
fixme:wtsapi:WTSQuerySessionInformationW Unimplemented class 8
[...]
[00000218:] EXCEPTION handling: System.Net.WebException: The operation has timed out.

If it's of any relevance I have IPv6 completely disabled on my system.

[WildPenquin]

I have IPv6 enabled and the launcher has never worked for me. I don't remember all the Proton versions I've tried.

FWIW I believe the launcher is buggy even on Windows.