Things to add: System Information Gist

Symptoms

• EAC will not be installed/will not work even if its setup is launched manually in "SteamLibrary/steamapps/common/Warhammer Vermintide 2/installers/EasyAntiCheat/"
• due to bypassing the launcher (and EAC not being usable), progression is not saved on the game servers and trying to retrieve or save information from/to the game servers will give an in-game prompt to quit the game.
• tinted screen after loading in (not affecting the HUD) pitch black (does not resolve itself most of the time, workaround by changing FOV, changing FOV while everything looks as expected in turn turns everything black), green and pink tints or dense "fog" resolve itself after a couple seconds, as do graphical glitches/artifacts/stripes after loading in.

just another confirmation here at what @lorce said. game doesnt save progress and you cant join online matches due to easy anti-cheat

Are any of these issues fixable on the Proton side? I found a thread on the fatshark forums that shed some light on the issue with EasyAntiCheat. I'm ok with setting up a VM to run this game, but if it's possible I'd like to stay away from windows.

Also, I was never able to get it to launch properly. I enabled the skip launcher option and it displayed the various splash screens, but when it's supposed to show the menu it crashes. I doesn't really matter if a fix isn't possible, but it was a bit frustrating for me.

There's a thread about it in #1468 and there should be more information about the issue.

Edit:
Hmm... maybe I should keep this open as the issue isn't solved... The game doesn't work as intended either...

Looks like Valve is working to get EasyAntiCheat to work on linux! I'm pretty excited for this, V2 is one of my favorite games.

So, no solution for anticheat yet.

An update for the interested:
https://www.reddit.com/user/Guy1524/comments/hc3o1y/eac_progress_update/

So, no solution for anticheat yet.

No longer true, some crazy frogs did it.

https://drive.google.com/file/d/1KWETkDj89ZCG8p5PHPqLAtgMd4X77gk6/view?usp=sharing

Might take a little while until it comes all the way to Proton though.

What is the last file linked?Whats the file provided? Does that allow this game to work multiplay?

@Gibbz After EAC updated, it no longer works.

What is the last file linked?Whats the file provided? Does that allow this game to work multiplay?

@Gibbz, as @Patola said, it no longer works since the later EAC-patches.

It was a Wine-tree with EAC specific patches. As such only relevant for those of us with the knowledge and time at hand to compile wine.

Discussion takes place at #easy-anti-lobster-dev in the VKx-discord (https://discord.gg/mjWm8DK should work, it used to be the official invite link AFAIK). But to be honest, the discussion has been quite dead most of the fall and the winter so far.

Is it possible to play this via lan multiplay without using EAC in its current state?

Is it possible to play this via lan multiplay without using EAC in its current state?

AFAIK you can play on the modded realm. I.e. without progress, but it should be playable.

The game closes itself a minute after starting. During this time, you can have time to go into the settings and run the benchmark.

Demonstration: https://youtu.be/tN83gdJ35eE

System Information

• GPU: AMD Radeon 6900XT
• Driver/LLVM version: Mesa 21.3-git/12.0.0
• Kernel version: 5.13-rc3
• Link to full system information report as Gist
• Proton version: experimental-6.3-20210604

steam-552500.log

If you hurry up and press "Play", then after the splash with the shark, the message "Backend rejected the challenge response" will be displayed.

steam-552500.log

@NTMan The launcher did not work a while back, so they have apparently changed something (or proton / wine includes more dependencies than before). Does modded realm work for you? What is your performance compared to Windows?

@flindeberg I recently delete my Proton prefix, and booted up the game. The launcher worked, but it will crash after ~10 seconds. Just long enough to hit the modded realm check box, and boot up the game.

It performs extremely well. ~80fps on maximum graphics at 1440p. Never goes lower than 65 fps, even when a huge horde is attacking. Highest peaks are 90.

Fedora 34 Kernel 5.13
Ryzen 2700 4ghz oc
Radeon 5700xt

Enabling mods can be done by opening the config file located at steamapps/compatdata/552500/pfx/drive_c/users/steamuser/AppData/Roaming/Fatshark/Vermintide 2/user_settings.config and setting each mod to enabled = true

That folder also has a launcher.cfg where you can set SendCrashReports to false and DisableAntiCheat to true.

Technically, you can only progress on the Official Realm, BUT there is a mod known as "Casual Mode". Which allows you to unlock everything straight up, or use a progression system similar to the Official Realm. It uses xp gained from the missions. It's pretty much perfect.

I found some mods were unstable, and crashed the game, so I cut it down to only the Vermintide Mod Framework, Penlight Lua Libraries, and Casual Mode (I assume load order is from top to bottom). I haven't used it very much, but it seems to work pretty well.

Work is being done, we'll see when it will be enabled and working https://steamdb.info/depot/552503/history/?changeid=M:5995370140976663476

Looks like they have been trying to reach out for enabling EAC support: https://steamcommunity.com/app/552500/discussions/0/2960544187643622408/?ctp=26#c3419936604888208895

Seems like people are having some working EAC on the Steam forums https://steamcommunity.com/app/552500/discussions/0/2960544187643622408/?ctp=30#c3457094584911997892 and a dev even replied even if he still didn't confirm they changed something the past days. So far on my end, no luck, can't have anything to work. Will update if I find my issue and a fix.

It's working here on Nobara + GE-Proton7-28. Clean install, clean prefix. Multiplayer works.

Proton Experimental allowed me in.

I simply verified the game files -> Made sure Proton Experimental and the Proton EAC Runtime downloaded (I hit the queue download now) -> Bam the game let me in, I collected the daily reward.

i reinstalled proton eac runtime and now instead of "eac not running it says "insufficient resources"

some progress I guess.

Yep that's where I am (see link above, I posted screenshot) since two days, I tried everything possible (I did not do a full reinstall of the 100GB files of the game, I tried at some point to delete everything but the Bundle folder, and verify the files in Steam to re-acquire the missing binaries and other files). I Tested Proton GE, Experimental (and its Bleeding Edge beta), I reset prefix all the time, I also tried to force reinstall EAC in the prefix, tried the various game beta options, tried with or without various launch options in game properties. But it seems my setup is doomed, when some other people can simply make sure to use Proton Experimental and have EAC Runtime installed, and they are all good instantly.

Maybe this is related to network and EAC can not communicate or download something, this is where my thoughts are now that I think I virtually tested everything on the Proton/game side. I might need to fully reinstall the game but to me that makes no sense when the game files verification should have made sure all files were good.

//EDIT: also, it seems it only works when you host the game as the Proton user, if you join other people's game it will kick you out after the usual EAC check.

I managed to get it running once with Proton GE 7-28 and since testing Proton Experimental, even replicating the method with Proton GE again, I get the State: Untrusted error.

@Zorrototo you might be on to something. I never confirmed this when it was working but at this point in time, if I examine the loader.log file in the prefix' AppData\Roaming\EasyAntiCheat\226 folder, there are attempts to connect to anticheat servers (for wine64) and fails. If I run the URL in a browser, it downloads a file. I'm curious if placing this file in the appropriate folder would get it working again (although I don't know which folder this file is meant to go into or how it's processed).

Edit: Nevermind about the latter...each download is randomized, so it would make sense that each game instance opened up would download a unique file for that specific session.

Edit 2: Seems I was looking at the wrong folder. The correct folder is ~/.cache/com.epicgames.easyanticheat/226/ and the loader.log shows a successful connection to the server.

There might be hope for me, I did not try yet but it smells like a good lead. https://github.com/ValveSoftware/Proton/issues/6051#issuecomment-1207123916

Will report when I can test, I actually deleted the game a few hours ago :1st_place_medal:

//EDIT: doesn't seem to help me.

Sorry to read that, @Zorrototo . I'm running Fedora 36 KDE and glibc is 2.35. What's strange is that it worked once but not since (and it seems I'm not the only one; comment # 493).

Sorry to read that, @Zorrototo . I'm running Fedora 36 KDE and glibc is 2.35. What's strange is that it worked once but not since (and it seems I'm not the only one; comment # 493).

I'm also running Fedora 36 and KDE. I just played a round perfectly fine. It was a private match, but I got items afterwards and everything.

I was able to play an entire game with glibc-eac and GE-Proton7-28.

What worked:

• Hosting my own match
• Playing with others, other players successfully joining mid-game
• Playing an entire match without getting kicked

What didn't work:

• Joining someone else's game. I could only host my own without getting kicked.
• Experienced a crash on DX12 mode. I only tested this once before going back to DX11. DX12 is desirable for VT2 since it is very CPU heavy.

Other things I noticed:

• DX11 mode requires you to reenable Fullscreen after alt-tab even with "Minimize on Alt-tab" disabled. This behavior was not observed in DX12 mode.
• DX12 (VKD3D) still runs better than DX11 (DXVK) just like on Windows (from what I noticed at Taal's Horn Keep)

System:
CPU: 5900x
GPU: Radeon RX 6900 XT
Mesa: mesa-git (mesa-tkg-git 22.3.0_devel.157575.446d2039cb7-1)

after the proton experimental update yesterday/today the game wont launch for me anymore. both official and modded (-eac-untrusted). BUT changing to proton 7.0-4 (release candidate) works. including hosting games in official realm

system:
Ubuntu 20.04.4 lts
kernel: 5.15.0-43-generic
cpu: AMD Ryzen 9 PRO 3900
gpu: NVIDIA rtx 2070 (mobile?) Driver Version: 470.141.03 (i know its outdated)

i looked into logs of EAC and windows version asks for https://download.eac-cdn.com/api/v1/games/226/client/wow64_win64/download/?uuid={uuid goes here but seems irrelevant}
while running on proton it asks for
https://download.eac-cdn.com/api/v1/games/226/client/wine64/download/?uuid=...

The first yields a 13.8MiB file that is placed in same directory where loader.log is, named easyanticheat_wow64_x64.eac but wine64 file is a 0 byte file.

Game ran great, updated glibc to 2.36 along with numerous other system updates, game no longer gets beyond the "Preparing to launch Warhammer: Vermintide II..." screen on Steam. Both for steam-native and Steam Flatpak.

Hello @Green-Sky, DXVK and VKD3D-Proton in Proton experimental now requires NVIDIA 510.47 or newer. This minimum driver requirement bump is not a bug.

so i updated to 515, and had to re-restart steam. also switched to proton experimental. now it works again.

I don't know if this actually helped getting the game working or not but I've repeated this multiple times when the state: untrusted error kicked in and has worked thus far. In the launcher, set it to modded realm and start the game. It gets stuck at the loading screen (after the warning) so I alt+F4, restart the launcher, set it back to the official realm, start the game and it worked. Just F.Y.I, if anyone uses the launcher bypass branch, the desktop shortcut ignores it (so the game needs to be started within the Steam client itself).

The game was hosted on my side, so I can't confirm being kicked when joining a game, and it ran pretty good in DX12. However, I noticed a few glitches which occurs with both DX11 (DXVK) and DX12 (VKD3D-Proton) running on a RX 6800M w/ Mesa 22.3.0-devel drivers.

When adjusting the camera, it can be positioned to expose gaps in the walls/floors (as well as a glitch with a waterfall and geometry of an arrow disappearing when being pulled):

Hey @kisak-valve . Here's the Proton Log and system information you requested.

steam-552500.log
System Information

Concerning the graphics issue, I could create a ticket on the Mesa git and provide an apitrace, if it will help.

@r2rX Can you try again after pulling Mesa main again? It might be related to the regression kisak pointed out. Thanks!

Hi @kisak-valve . Your deduction/intuition was on point so I wanted to let you and @hakzsam know that the dccd6f49 commit in the mesa driver did indeed fix the culling issue! Great job! (The waterfall shader/rendering is still slightly off).

restarted the game and now it works?

although running dx12 version + going to quests tab in okri's book hanged my X11 or something, had to restart sddm.

ok that dx12 hang was one of a kind freak accident, although game didn't want to start at first, complained again about "insufficient resources" even though only 32% of memory (total 32GiB available) was used.

I experience random crashes when running the game (no eror messageis provided, it just closes back to desktop). They may happen within the first five minutes of gameplay or after half an hour - seems random.

Changing graphical settings or dx api (11/12) does not seem to have an effect. Only tried proton stable an experimental and the crashes happen with both.

sysinfo.txt
steam-552500.log

@pprotonrep Try skipping the launcher. I.e. use the "Bypass launcher" option when launching the game from steam.

The log-entries mentioned by @kisak-valve concern components only used in the launcher as far as I know.

@flindeberg thanks for the suggestion

I've been switching back and forth between the "bypass launcher" branch and the release branch to see if it made any difference. I get crashes with both, although they may not have the same root cause :shrug:

This is the log from a crash while running the "bypass launcher" branch on dx12 mode.
steam-552500.log

I could successfully run through a couple of acts on dx11 mode - but at this point I'm not sure if this was just pure coincidence. I'll do more testing on dx11 mode and report back, in case this helps anyone with similar problems in the future.

I've run the game several times now, experiencing the same crashes, regardless of dx version.
This would be a log of a crash while running on dx11, practically identical to the other one besides from the vkd3d entries.

If this is not a widespread problem maybe it's just something about my system - i wont spam the tread anymore. I'd happily help with further analysis if more users seem to be affected by this.

I continue to get the state untrusted error. I was recently able to enter the game, but after minute or so the game crashed. Upon restarting I get the state untrusted error. Deleting steamapps/compatdata/552500 and verifying integrity seemed to reset the issue, allowing me to join once again for a minute or so. But that seems to have stopped working.

system info
most recent log
steam-552500.log

For all those with the Untrusted / Insufficient Resources issue, did one of you try to wipe everything including game files and start over? I usually am an advocate of never doing that instead of verifying files, but I'm leaning towards a full wipe/cleaning/reinstallation now, but for me this is a week long project due to my connection so I would prefer to gather information from others first.

i can say that i did NOT wipe all game data to get it working, i only ever deleted proton's wineprefix

insufficient resources seems a bit random, i feel like EAC wants to have certain amount of memory/disk space free or something, or it gets misreported somehow

Had the insufficient resources message when I tried to play with Proton 7.0-3.
The message disappeared when I changed to Proton Experimental.
Had the same symptoms of everyone: connecting to a random game works but disconnects after 1-2 minutes. Hosting the game works. Hope they fix it quickly.

fun fact - i had "insufficient resources" error once, then i started the game again without changing proton version and it worked fine.

fun fact - i had "insufficient resources" error once, then i started the game again without changing proton version and it worked fine.

If that was recent, it might be due to the upgrade to 7.0-4 that's just out. It seems it's currently the same as Proton Experimental. 7.0-3 was automatically upgraded to it.

a week ago or so

fun fact - i had "insufficient resources" error once, then i started the game again without changing proton version and it worked fine.

Proton (or rather Wine) does a lot of automagics when loading from a prefix with a different version. It is entirely possible, although impossible for me to tell without logs, that the automagics somehow broke for the first try and the second try skipped the automagics because it was not the first run with the prefix with that particular version of Wine.

Also remember that EAC does quite a bit of automagics as well, for example updating the required dlls "sometimes" :tm: .

If in doubt, try again or restart your computer (seriously).

For all those with the Untrusted / Insufficient Resources issue, did one of you try to wipe everything including game files and start over?

I've tried this - no luck. Consistently getting the error.

Have tried everything suggested in this thread, and cannot get past the error no matter what I try. I've attached my specs and proton log in the hope someone can see something obvious!

specs
steam-552500.log

Thanks for reporting. I had little hope for that but now I'm wondering what we could test to find what's wrong. Hope devs work on it more anyway as it still doesn't work properly anyway for those who can play.

I don't know if this will help everyone trying to get around this resource issue but the following are the steps I have repeated reliably to get it working:

1. Ensure the Proton EasyAntiCheat Runtime is already installed.
2. Delete the Verminitide prefix (folder 552500) in .local/share/Steam/steamapps/compatdata/
3. Start the game. At this point, Steam should be installing the Windows libraries required for the game (i.e EasyAntiCheat, VC Redist, DirectX etc). Once completed, the launcher should pop up so select official realm and it goes in-game. It will eventually show the resource error...this is to be expected. Close the game (alt-F4).
4. Now run the file verification process and, assuming all goes well, it will report that one file for the game had an issue and it should download this file (around 65kb) as well as refreshing the Proton EasyAntiCheat Runtime, Steam Linux Runtime - Solder and maybe even the Proton version you're using.
5. Start the game after completion, launch into the official realm and it should work.

Whenever there is a Proton update, the prefix will either crap out and not update properly (hangs) or I need to redo steps 3 to 5. Assuming it's the former, I start from step 2.

1. Start the game after completion, launch into the official realm and it should work.

Thank you for the suggestion, I followed your steps and it did re-download a file, however on trying the official realm I had the same error and still unable to get past this. Other EAC games, i.e. Apex work fine.

Hmm. The last thing I can suggest, @Hellhound1 , is to enable the 'Bypass Launcher' branch under the 'Beta' properties, launch the game within Steam and run Bypass Launcher.

@Montagge What are the filesystems of the two drives?

@flindeberg Both filesystems are ext4

Proton experimental of 20/9/2022 claims the game is now playable. can someone verify this statement pls?
https://github.com/ValveSoftware/Proton/wiki/Changelog

Proton experimental of 20/9/2022 claims the game is now playable. can someone verify this statement pls?

It worked perfectly a couple of weeks ago, and unless they have broken it, it should still work.

It should work, but it doesn't for some people so test yourself.

Proton experimental of 20/9/2022 claims the game is now playable. can someone verify this statement pls? https://github.com/ValveSoftware/Proton/wiki/Changelog

Still not working for me on Ubuntu 20.04 LTS

Now I am experiencing a crash when other players join in-mission. Someone was able to join the hub and launch a mission just fine.
steam-552500.log

Yeah, I have no issue running the game but EAC sure hates us Linux folks. As others have said, if you aren't hosting it will yeet you out of there within a minute. I also notice that it is very quick to crash if it thinks resources are tight in any way. I had to turn down graphics settings even though I was getting no stutters nor frame drops.

Yeah, I have no issue running the game but EAC sure hates us Linux folks. As others have said, if you aren't hosting it will yeet you out of there within a minute. I also notice that it is very quick to crash if it thinks resources are tight in any way. I had to turn down graphics settings even though I was getting no stutters nor frame drops.

I'm not certain if the issue, of being kicked after joining a game, is strictly due to EAC because I experience the same issue when joining a game in the modded realm as well.

Proton 7.0-4:
Launcher crashes as soon as I mouse-over the Play button in the Warhammer launcher.

Proton experimental:
Can launch the game but it crashes randomly a few minutes in with a crash dialog window popping up. First time during some cage transport intro, second during character creation.

Ubuntu 22.04.1 LTS
Nvidia GTX 1070, driver 515.65.01.

Hosting issue still persists in latest Proton RC as date of 24 hours before this comment.

For me I can play Kingdom modded from Proton 6.3, cant play from Kingdom official because EAC dont run and cant reach the server. For Proton 7 version I cant play, he run but eac say :"Insufficient ressource, cannot continue".

In case you have a high core count CPU and you are experiencing (frequent) crashes, go into the launcher settings and limit worker threads to 6 at most! This is recommended by the developers and at the very least made crashes way less likely for me. Haven't crashed in 1h+ of gameplay vs. every 3 minutes before

Edit: I played for a bit more today and I can say that it's exactly what I expected. It just crashes less frequently than before. It crashed like a few minutes after completing one mission just now. Looks to be some kind of race condition between these "worker threads". Could very well be a bug related to Proton/Wine because otherwise Windows players would complain all day and call it unplayable.

the launcher uses msedge webview and the updater of the webview runtime, that starts with the launcher in the background, crashes or doesn't finish and prevents the start of the game/launcher. (1)
if I kill the process, the launcher opens just fine, but it spawns another update process in the background. (2)
the game will start and no issues then, but if I close the game, there is that update.exe in the background which prevents the shutdown. (3)
After killing the process the game shuts down as it should.

edit: tested with proton-next, proton-experimental and GE-Proton7-41

(1)

(2)

(3)

the launcher uses msedge webview and the updater of the webview runtime, that starts with the launcher in the background, crashes or doesn't finish and prevents the start of the game/launcher.

It's look like the bug that I described here: https://bugs.winehq.org/show_bug.cgi?id=53925

Has anyone looked into running sanctioned mods on the official realm? The game boots normally and does not have any mods active when booting the official realm with mods enabled.

Has anyone looked into running sanctioned mods on the official realm? The game boots normally and does not have any mods active when booting the official realm with mods enabled.

seems what EAC problem

09:47:32.864 warning: [ModManager] Mod with id 1395655171ll and path Z:\home\exnt\.local\share\Steam\steamapps\workshop\content\552500\1395655171\mod.bin can't be added as mod hash catalog to EAC, skipping
09:47:32.864 warning: [ModManager] Mod with id 1389872347ll and path Z:\home\exnt\.local\share\Steam\steamapps\workshop\content\552500\1389872347\mod.bin can't be added as mod hash catalog to EAC, skipping
09:47:32.865 warning: [ModManager] Mod with id 1397265260ll and path Z:\home\exnt\.local\share\Steam\steamapps\workshop\content\552500\1397265260\mod.bin can't be added as mod hash catalog to EAC, skipping
09:47:32.865 warning: [ModManager] Mod with id 1369573612ll and path Z:\home\exnt\.local\share\Steam\steamapps\workshop\content\552500\1369573612\mod.bin can't be added as mod hash catalog to EAC, skipping
09:47:32.865 warning: [ModManager] Mod with id 1445717962ll and path Z:\home\exnt\.local\share\Steam\steamapps\workshop\content\552500\1445717962\mod.bin can't be added as mod hash catalog to EAC, skipping
09:47:32.871 [Lua] <mod_handles>
09:47:32.871 [Lua] </mod_handles>
09:47:32.871 [Lua] user_setting.mods =>
09:47:32.871 [Lua] [ModManager][warning] Mod "Vermintide Mod Framework" with id 1369573612 was not found in the workshop folder.
09:47:32.871 [Lua] [ModManager][warning] Did you try loading an unsanctioned mod in Official?
09:47:32.871 [Lua] [ModManager][warning] Mod "Simple UI (Abandoned)" with id 1389872347 was not found in the workshop folder.
09:47:32.871 [Lua] [ModManager][warning] Did you try loading an unsanctioned mod in Official?
09:47:32.871 [Lua] [ModManager][warning] Mod "Numeric UI" with id 1397265260 was not found in the workshop folder.
09:47:32.871 [Lua] [ModManager][warning] Did you try loading an unsanctioned mod in Official?
09:47:32.871 [Lua] [ModManager][warning] Mod "Bot Improvements - Combat" with id 1395655171 was not found in the workshop folder.
09:47:32.871 [Lua] [ModManager][warning] Did you try loading an unsanctioned mod in Official?
09:47:32.871 [Lua] [ModManager][warning] Mod "Loadout Manager" with id 1445717962 was not found in the workshop folder.
09:47:32.871 [Lua] [ModManager][warning] Did you try loading an unsanctioned mod in Official?

I just installed the game and get the "backend rejected the challenge response" error message right after starting.
It seems that EAC isn't running, do I have to start/install it manually?

@darman96 there is a problem if EAC runtime gets installed automatically by the game. What I do to work around this issue consistently is:

1. Exit Steam (make sure no process is living)

2. Uninstall manually the EAC runtime using the command:

   # DO NOT COPY-PASTE RANDOM COMMAND OF RANDOM PEOPLE ON THE INTERNET
   # this depends on your installation, you need to correct the paths
   # rm -fR ~/.local/share/Steam/steamapps/appmanifest_1826330.acf ~/.local/share/Steam/steamapps/common/Proton\ EasyAntiCheat\ Runtime/
   

3. Restart Steam

4. Show tools

   

5. Install Proton EasyAntiCheat Runtime.

6. Verify game files of Vermintide 2

7. (Run game with bypass launcher)

(I think you need to do that every time there is an update of Proton... so once in a while)

Replying to https://github.com/ValveSoftware/Proton/issues/1528#issuecomment-1367318785

In my experience, uninstalling Proton EasyAntiCheat isn't necessary. As long as it's installed, that's fine at least. I'm leaning to the issue being related to the Windows binary of EAC. When a prefix is updated, the Windows EAC binary needs to be reinstalled (that's why it's assumed the file integrity check fixes it...it's because the Windows EAC binary being re-installed in the process).

The game works fine when hosting for me currently, when joining a friend it tries to host migrate after... even if it's linux host aswell.

Found a line in a log where host breaks object, that he owns, and it removes the object (host) and server disconnects... from my client.

13:12:32.972 [Lua] [GameNetworkManager] game_object_destroyed_player, game_object_id=0 owner_peer_id=110000101a4646d peer_id=110000101a4646d
13:12:32.972 [Lua] PlayerManager:remove_player peer_id=110000101a4646d 1
13:12:32.974 [Lua] [GameNetworkManager] removing peer_id=110000101a4646d local_player_id=1
13:12:32.974 [Lua] [GameNetworkManager] game object was destroyed id=0 with type=player, object_destroy_func=game_object_destroyed_player, owned by peer=110000101a4646d
13:12:32.974 [Lua] [GameNetworkManager] Game session disconnected, leaving game...

It happens 4 times in same log, 4 times I probably connected to that game friend hosted.

console-2022-12-31-11.58.36-47cc66d4-37e8-4961-b299-0282e7656b15.zip

Edit: I suppose it should work like that once it goes wrong...?
Edit2: Ah forgot to mention... when getting kicked out, client tries to reconnect, but it tries to connect to one of the other users and not the host of that session. The host id seems to go nil the moment it's deleted or smt...

If someone is interested the DC bug still happens.

Maybe if we look at the Source code? The game has a avid mod scene for the modded realm and the Source code of the game is public so modders have a easier time making mods. Maybe someone will have a clue?

https://github.com/Aussiemon/Vermintide-2-Source-Code

Anyone found out why the game works only if you host the match? If you join someone's game, EAC kicks you out.

This is probably because of the implementation they made (on the dev side) of EAC / Proton. They probably didn't do it right.

//EDIT: for me it doesn't even work at all, I can't even reach my lobby.

This is probably because of the implementation they made (on the dev side) of EAC / Proton. They probably didn't do it right.

But they are the same devs from Darktide. In Darktide it works normally.

This is probably because of the implementation they made (on the dev side) of EAC / Proton. They probably didn't do it right.

But they are the same devs from Darktide. In Darktide it works normally.

darktide uses a different networking model, and there's a number of other engine changes; wouldn't be surprised if the eac connected parts of things were different between the games.

Someone dig into the lua and figure it out.

Recently swapped from EndeavorOS to Manjaro and trying to run the launcher returns a large error window. Bypassing the launcher results in a EAC issue.

@LuxLucian did you make sure to install the EAC runtime on your new install?

@LuxLucian did you make sure to install the EAC runtime on your new install?
I am pretty sure it's installed, I also deleted the folder and verified files.

EDIT:
Vermintide 2 claims that EAC is not running, I'll get a proton log and upload it in another edit

EDIT2: Proton logs
Log from bypass launcher (DX11)
https://pastebin.com/1x4VDRvL

Log from trying to start the launcher
https://pastebin.com/faqsNvht

Check this, it might help https://github.com/ValveSoftware/Proton/issues/1528#issuecomment-1367318785

Check this, it might help [#1528 (comment)](https://github.com/ValveSoftware/Proton/issues/1528#issuecomment-1367318785)

It didn't work (I think) but another post seems to have fixed it.

I ran the launcher and tried starting the modded realm. The game would hang on the load screen and I closed it. After running the official realm worked without the EAC issue.

EDIT: It stopped working again and this fix no longer works for me

GPU: AMD 5700 XT
Drivers: Mesa 24.0.2-2
Kernel:Zen 6.7.8
Proton: GE, though 9.0 (Beta) and 8.0-5 do not work either

New update seems to have broken the game again for me.
I get a popup saying "EAC state: untrusted" and it either hangs at the new login/load screen or gives a backend error and prompts me to quit the game.
I'm using these launch args

%command% : ./fix.sh

Which runs this script

#!/bin/bash
awk -i inplace '{if ($1 ~ /StateFlags/) sub(/4/, "100"); print;}' ../../../appmanifest_552500.acf

steam-552500.log

It seems deleting the EAC folder in the game directory, verifying files, and resetting the prefix sometimes works.

Had it partly working in the tutorial with experimental and temporary_launcher_workaround. I didn't get to test multiplayer. After crashing in the tutorial and relaunching I am experiencing the hanging login.

Was able to play one long session (hosting) on first install with no problems besides killing Edge installer during startup.

On second session received the following error:

after which loading would hang on "Stocking Emporium" and go no further.

I tried all of the following:

• Switch to temporary_launcher_workaround beta. I tried both "Skip Launcher" and "Skip Launcher (DX12)".
• Apply fix.sh script from above
• Uninstall and reinstall Proton EAC runtime
• Verify files before and after each attempt
• Delete EasyAnticheat files from game folder and recreate prefix
• Completely uninstall and redownload game

Additionally I tried every combination of these steps with each other, as well as every combination while verifying files before/after and deleting/recreating prefix each time. Nothing worked; I am completely unable to play the game anymore.

Recently swapped from EndeavorOS to Manjaro and trying to run the launcher returns a large error window. Bypassing the launcher results in a EAC issue.

Trying the boot the game with the launcher gives me this issue. I cannot get EAC to work and I have no way of starting the modded realm.

A friend of mine I regularly play with moved from Windows to Linux, (I've been on Linux all this time) and to play together I always hosted. Now that we are both on Linux, we can't play together.

Any resolution or insight into this weird issue?

No, the person on Linux MUST host.
Nothing has changed since the initial "compatibility" with Proton, it was broken and will stay broken.

Unfortunately, it's still not working properly and the only ones who can fix it are the game devs (Fatshark) themselves....and it doesn't look like they will.

That's unfortunate.

So what if I just want to play on the modded realm? The Launcher is not functional for me on GE Proton 9.37. I can't click anything. I want to play with someone on macOS where EAC is not available at all (otherwise the game runs fine on macOS on modded realm).

Fyi, Fatshark updated the game to use epic online services for the easy anti cheat solution, which finally fixes the linux user must host problem.

The launcher is still barely functional, and the launcher bypass beta should still be used.

I played a game with one linux user as host and both a windows and linux user as clients, worked like a charm.

Even with the new EAC update I am still getting EAC untrusted errors when booting the game.

If the untrusted state happens on an existing installation, I would suggest trying to remove the proton prefix and letting a new one be created (by removing/renaming the prefix or just switching to and from a different proton version).

One of my friends had the same issue on an existing install after the update, and making a new prefix seems to have solved it (he did also verify game files, but this did not seem to fix anything)

I did try both things, file verifying and prefix deletion. I'll try different proton versions next.

EDIT: No dice, wiping prefix and swapping proton versions does nothing.

EDIT 2: Using the skip launcher beta seems to have worked, and I can also play on the modded realm is EAC doesn't work. I did close both vesktop and my browser just in case too. Never seen a game work so inconsistently on linux.

If you have a connection error to the lobby due to a supposedly disabled anti-cheat, first try the solutions listed on ProtonDB. If they don't help, enter ping modules-cdn.eac-prod.on.epicgames.com in the console, copy the IP address from the output, and add a line like <IP-address> modules-cdn.eac-prod.on.epicgames.com to /etc/hosts. This method helped me solve the problem with the lobby host/connection to other lobbies. The solution was found on the game's forum.

The only inconvenience is that other games with EAC, for example, The First Descendant (2074920), can only be launched with 0.0.0.0 modules-cdn.eac-prod.on.epicgames.com in /etc/hosts. I would like to see some kind of launch parameter (?) or a complete fix for the error. For now, I'm just using a simple script to switch the entry in /etc/hosts.

The game fails to start, displaying a "corrupted files" message from Easy Anti-Cheat.

I tested the game again these days (on PC on SteamOS) because I haven't play for a while.

Last time (2022), I could only host otherwise I would get kicked by the EAC, I cannot use mods at all, can't even start modded realm. The launcher is not working at all.

Now (2025) the game has new launch settings in the beta version "skip launcher". I can now run the modded realm if I want to or select DX11 or DX12 easily. I don't get kicked by EAC anymore when join other's session. So there is improvement.

I tried to remove the skip launcher and enable some mods. Nowadays the launcher works better, it's glitched but quite usable. I can enable sanctioned mods and get into the settings and all. Unfortunately if I start the game with sanctioned mod I get the message "corrupted file something something the the "verify files" process" and the game quits.

Replying to https://github.com/ValveSoftware/Proton/issues/1528#issuecomment-3625638538

Update from 01Zanon01

I finally managed to get Warhammer: Vermintide 2 running on Nobara Linux, including online play with Easy Anti-Cheat.
Here are the steps that solved the issue for me:

1. Select a stable Proton version

In Steam → Properties → Compatibility, I forced the game to use Proton 9.x instead of Proton Experimental.

1. Opt into the “skip launcher” beta

In the Betas tab, I selected the beta branch that provides the new Bypass Launcher options.

1. Launch using the bypass launcher (no mods)

From the Steam launch menu, I chose:

Bypass Launcher
(the non-modded option, without using the official game launcher)

With these three steps, the game launched correctly and I was able to play an online session without being blocked by EAC.

Special thanks to @cecton
Your explanation about improvements in the skip launcher beta and the issues with mods/EAC helped me understand what was going wrong. Using the bypass launcher without mods solved the problem on my system.

Thanks everyone for the support!

@01Zanon01

I can confirm this method works on CachyOS as well.

Can Linux players finally host a game or still only join without being kicked after a few minutes?

Can Linux players finally host a game or still only join without being kicked after a few minutes?

Hosting and joining work fine, as long as you launch the game with the 'skip launcher' option.

I've made a patch that allows the launcher + EAC and all game modes to work:

0001-HACK-Force-Vermintide-2-current-working-directory-to.patch

Problem and resolution explanation:

Vermintide 2's launcher runs from game-folder/launcher/Launcher.exe, it then launches the EAC versions of the game using '../start_protected_game.exe' .

The problem is that when it's launched this way it keeps the current working directory set as game-folder/launcher, while the start_protected_game.exe and EAC files reside in game-folder/, thus start_protected_game.exe and subsequently EAC expect to read files from game-folder/, -not- game-folder/launcher/. Since the current working directory is set as game-folder/launcher by the launcher, it breaks EAC's file reading.

This patch checks for vermintide 2 if 'start_protected_game.exe' is called then forces the current working directory to game-folder/ instead of game-folder/launcher, allowing EAC to work when run from the launcher.

Unfortunately per discussion with proton devs this patch won't be accepted because it is indeed a hack and the underlying problem of 'current working directory' resolving properly either in wine or in the EAC linux bridge is what really needs to be addressed, so I wouldn't go expecting it to be upstreamed, but at least for now we have some method of working around the bug.

ayyy.. looks like we got an official fix now in experimental!:

https://github.com/ValveSoftware/wine/commit/c5a27304e01e5e5f38b82974b29ca30c532ead4c

ayyy.. looks like we got an official fix now in experimental!:

ValveSoftware/wine@c5a2730

Installed bleeding edge experimental. Unfortunately running the launcher bypass will briefly seem to start the EasyAntiCheat_EOS.exe program, but it almost immediately closes before Vermintide 2 starts up. I believe the issue is that EAC EOS executable closing that's causing the connectivity issues on official. I'm able to "connect" to others games, get the manifest of heroes that were picked, be told to swap to something else at times, but after a lengthy connection period I'll get told I'm untrusted and get booted back to the title screen. Same with people trying to connect to me. They attempt to connect, I see the attempt, and then they get booted.

Log attached if it'll help. Shows Proton version experimental-bleeding-edge-10.0-314083-20260217-pa57496-wc5a273-d8e6a2d-vd6ac0a

Operating System: Bazzite 43
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.17.7-ba25.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: AMD Radeon RX 6900 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X470 AORUS ULTRA GAMING

steam-552500.log

That build is too old, the Wine repo submodule in Proton was updated ~4H ago which includes the changes in commit https://github.com/ValveSoftware/Proton/commit/e784a4d5cbdf513870f17d283e426aace116583b.
The version should be experimental-bleeding-edge-10.0-315014-20260218-pa57496-wc5a273-d8e6a2d-vd6ac0a or newer.

That build is too old, the Wine repo submodule in Proton was updated ~4H ago which includes the changes in commit e784a4d. The version should be experimental-bleeding-edge-10.0-315014-20260218-pa57496-wc5a273-d8e6a2d-vd6ac0a or newer.

New version: experimental-bleeding-edge-10.0-315206-20260218-pa57496-wb49a74-dd222d2-vd6ac0a
Still unable to connect to games

steam-552500.log

Replying to https://github.com/ValveSoftware/Proton/issues/1528#issuecomment-3918800750

no. dont use the launcher bypass branch.
use the normal branch
make sure you have the latest version of bleeding edge
press play, the LAUNCHER will open.
press play on the launcher.

the fix was for running the game USING THE LAUNCHER. not bypassing it.

I did a few games yesterday with the new build, worked like a charm 😄 🎊

You can see the version of Steam Experimential with:
cat ~/.local/share/Steam/steamapps/common/Proton\ -\ Experimental/version

Posting a few dumps of the needed configs just to make it easier for everyone to test it.

Still no love on my end. I've updated the experimental build daily since my last post, but I'm rejected from joining games every time. The reported version is: 1771720628 experimental-bleeding-edge-10.0-316698-20260222-pa57496-w2ab7e7-d4357d6-v9ced67

Testing Vermintide 2 on an old laptop, I was able to get it to run the EAC front end. At least, I'm certain it worked, because it actually got to 100% rather than flickering on screen and disappearing. It didn't actually get into game (black screen), but the laptop is old enough that I expect it doesn't support the game.

Since both are running Bazzite, is there some way to "diff" the two systems to see what might be installed that's different? Besides me running an Radeon 6900 XT in my primary computer and the laptop having an nVidia integrated card that is. I'm curious what is making EAC say no to my main computer while the laptop is fine.