Compatibility Report
- Name of the game with compatibility issues: Farever
- Steam AppID of the game: 3672400
System Information
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:
err:steamclient:callback_len_utow Unix len 12 not found for callback 1112.
err:steamclient:alloc_callback_wtou len 16 is too small for callback 1112, using default.
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
- Install an AMD RX 9070 XT (device ID 0x7550)
- Launch Farever (AppID 3672400) via Proton Experimental or GE-Proton
- Game shows "no internet" error and exits after ~13 seconds
- Swap GPU back to RX 9070 → game connects and runs normally
Tested workarounds that did NOT help:
- Disabling Steam Overlay
- Launching Steam with -no-hardware-survey
- Deleting compatdata (3672400) and shadercache
- GE-Proton (latest)
- Steam Beta channel
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: