up, i'm also facing issues when connecting to the servers on linux
played around an hour, there were 3 instances of my character and mobs disappearing for around 3 seconds before returning, other than that I didn't have any issues. And, in general, the game seems to work for most people outside stuttering.
@imensy so are you getting disconnecting after a few seconds? can you get ingame, or it fails before that point?
@Telmur so you have 1 computer, and swapping gpus there can make the game not work? Making sure I'm reading things correctly, because this is something rather unusual. If so, it'd be good to have proton logs for both, but you need to change to proton experimental, your log is from a cachyos build
proton experimentalx2 2026-07steamclient64.dllx1 2026-060x80000026x1 2026-06
Compatibility Report
System Information
GPU: AMD Radeon RX 9070 XT (RADV GFX1201)
Video driver version: Mesa 26.1.2-arch2.1 (radv)
Kernel version: 7.0.11-1-cachyos
Link to full system information report as Gist:
(https://gist.github.com/Telmur/e78c5a4abc0d4036121d7043bbd56302)
Link to Proton.log
steam-3672400.zip
Proton version: Proton Experimental 11.0-20260609 (also tested GE-Proton, same result)
I confirm:
Symptoms
The game fails to connect to its servers and shows a "no internet connection" error
immediately on startup. The issue is reproducible 100% of the time with an RX 9070 XT,
but does NOT occur with an RX 9070 in the same system with the same software stack.
The Proton log reveals the root cause – two errors in the steamclient bridge:
After this, steamclient64.dll enters a connection retry loop (STATUS_LONGJUMP /
0x80000026, 623 occurrences over ~13 seconds) before the game gives up and exits.
The hypothesis is that Steam detects the RX 9070 XT (PCI device ID 0x7550) as new/
unknown hardware and triggers a hardware survey callback (1112) that Proton's
steamclient translation layer does not correctly map. This corrupts the Steam
networking state for the duration of the session. Swapping back to the RX 9070
eliminates the issue entirely.
Reproduction
Tested workarounds that did NOT help: