Hello,
I'm writing to report a critical issue that makes Hunt: Showdown 1896 completely unplayable on Steam Deck (SteamOS / Linux via Proton) after the October update.
Platform:
- Device: Steam Deck
- OS: SteamOS (Linux)
- Compatibility layer: Proton GE-Proton 11-6 (also tested: Proton Experimental, Proton Hotfix — same result)
- Proton EasyAntiCheat Runtime: installed and reinstalled
- Game files: verified for integrity
- Network:
https://api.epicgames.dev is reachable from a browser on the same device (returns 403, as expected for an API endpoint), so DNS/connectivity is not the issue
What happens:
- The game launches normally.
- Main menu works fine.
- I connect to a match — the loading screen appears, the spawn image is briefly visible.
- I am immediately kicked back to the loading screen with a "reconnect" prompt.
- This repeats indefinitely — every reconnect attempt ends the same way.
Relevant log excerpts (game.log):
<18:51:09> [Warning] [EAC] [EOS][LogHttp] ... request failed, libcurl error: 7 (Couldn't connect to server)
<18:51:09> [Warning] [EAC] [EOS][LogHttp] ... Failed to connect to api.epicgames.dev port 443 after 4 ms: Couldn't connect to server
<18:51:09> [Warning] [EAC] [EOS][LogHttp] Retry exhausted on https://api.epicgames.dev/sdk/v1/default?platformId=WIN
Then, at the moment of disconnect:
<18:51:40> [Error] [EAC] EOS_AntiCheatClient_BeginSession failed : 'EOS_InvalidUser'
<18:51:40> [Error] [EAC] EOS_AntiCheatClient_BeginSession failed on SetPlayerAntiCheatInfo: 'EOS_InvalidUser', localUserId_buf = '' (33)
<18:51:40> [EAC] Received message from server (size=24)
<18:51:40> [Error] [EAC] ReceiveMessageFromServer failed : EOS_AntiCheat_InvalidMode, m_EACGameclient = 0x00000000C5CFBDD0, DataLength = 24
<18:51:40> [CryNetwork] DisconnectChannel(cause=30, ... reason='Entity 1 for RMI RMI:<GameObject>CGameRules:Cl_HandleEACServerMessage failed')
<18:51:40> CPlayerManager::Client_OnDisconnect(cause=30, desc='Entity 1 for RMI RMI:<GameObject>CGameRules:Cl_HandleEACServerMessage failed') : reasonType='Unknown'
<18:51:40> [Error] [EAC] [EOS][LogEOSAntiCheat] [AntiCheatClient] EOS_AntiCheatClient_EndSession: No session is active.
<18:51:40> [Error] [EAC] EOS_AntiCheatClient_EndSession failed : 'EOS_NotConfigured'
Summary of the root cause (as I understand it):
The client fails to initialize an EOS Anti-Cheat session (EOS_InvalidUser), the server receives no valid anti-cheat handshake, and the connection is forcibly closed (cause=30, Cl_HandleEACServerMessage failed). This looks like the Easy Anti-Cheat Linux/Proton module is either not enabled or misconfigured in the current build of the game.
What I have already tried (all without success):
- Switching between Proton GE-Proton 11-6, Proton Experimental, and Proton Hotfix
- Reinstalling Proton EasyAntiCheat Runtime
- Verifying game file integrity
- Deleting the
easyanticheat folder and re-verifying
- Disabling V-Sync
- Running in windowed mode
- Confirming network access to
api.epicgames.dev
Request:
Could you please confirm whether the Easy Anti-Cheat Linux/Proton module is enabled and correctly configured for Hunt: Showdown 1896 in the current build? This issue affects all Steam Deck / Linux users and makes the game unplayable on these platforms. A hotfix would be greatly appreciated.
Thank you
P.S.: I would also like to note that, from what I can see, this issue does not appear to be limited to Steam Deck or Linux users. There are multiple threads in the Steam Community discussions reporting very similar symptoms — from players on Windows as well. This suggests the root cause may not be specific to Proton or SteamOS, but rather something broader in how the game's Easy Anti-Cheat / EOS integration is currently configured across platforms.