Defiance

protonopen Game compatibility - UnofficialRegression

ValveSoftware/Proton#8624 · opened 2025-04-23 by arazilsongweaver · updated 2025-05-16 · 12 comments · github

Aarazilsongweaver 2025-04-23 github

Compatibility Report

Name of the game with compatibility issues: Defiance
Steam AppID of the game: N/A

System Information

GPU: AMD Radeon RX 6900 XT (radeonsi, navi21, LLVM 19.1.7, DRM 3.61, 6.14.3-arch1-1) (0x73af)
Video driver version: Arch Linux mesa 1:25.0.4-1
Kernel version: 6.14.3-arch1-1
Link to full system information report as Gist: https://gist.github.com/arazilsongweaver/11fbb1fcc69e85574b29e51136e25ee0
Proton version: 6.3 (last known working version), Experimental (broken)

I confirm:

[X] that I haven't found an existing compatibility report for this game.
[X] that I have checked whether there are updates for my system available.

Log Files

protonexp-fail.log
proton63-success.log

Symptoms

Defiance does not connect to servers under the latest Proton Experimental but connects ok under Proton 6.3.

Reproduction

[The following instructions use the latest stable build of Lutris and that Proton 6.3 is installed via Steam.]

Set the Lutris WINE version to "Proton 6.3"
Install Fawkes Launcher under Proton 6.3.
Use Fawkes Launcher to install Defiance under Proton 6.3.
Launch the Defiance launcher under Proton 6.3.
Verify operation. The game should connect and allow you to create a character after playing the introduction cutscene.
Close out of everything.
Configure Lutris to launch Defiance using Proton Experimental instead of Proton 6.3.
Launch the Defiance launcher under Proton Experimental.
Verify operation. The game will attempt to connect and then instantly return a message stating that the game is currently unavailable. There is no getting past this connection error message.

Kkisak-valve maintainer 2025-04-23 github

Hello @arazilsongweaver, please share a Proton log without WINEDEBUG set. System WINEDEBUG: -all makes the Proton log you shared unusable for troubleshooting purposes.

Aarazilsongweaver 2025-04-24 github

Hello @arazilsongweaver, please share a Proton log without WINEDEBUG set. System WINEDEBUG: -all makes the Proton log you shared unusable for troubleshooting purposes.

New logs with full debugging have been uploaded to the original issue (see the new "Log Files" section).

Thanks for the follow up.

550MV 2025-04-25 github

Same here

Proton 5.13 and 6.3 can connect (some random disconnection)

Proton 7 and upper can't connect to servers

CachyOS

Kernel 6.15
Mesa 25
KDE 6.3.4

I714700
7900XT

NNSD4rKn3SS 2025-04-25 github

I've also experienced the same problems, also tested the Proton 6.5-GE fork which works the same as 6.3 and 5.13 but with less graphical glitches.

RRolandBarbe 2025-04-27 github

When using Proton versions 7.0 and higher (including Proton 9.0), the application fails to establish a connection due to an issue with the Winsock connect function. This problem does not occur with Proton 6.3.

Details:

The issue appears to be related to the network stack rework introduced in Wine 7.0, which Proton 7.0 and later versions are based on.
A Wireshark capture reveals that no data is transmitted after the TCP handshake when using Proton 7.0 or above.
The same application works as expected on Proton 6.3, indicating a regression in newer Proton versions.
Steps to Reproduce:

Run the application using Proton 6.3, 7.0, or 9.0.
Attempt to establish a network connection via the application.
Observe the connection behavior using Wireshark.
Expected Behavior:

The application should successfully establish a connection and transmit data after the TCP handshake, as observed with Proton 6.3.
Actual Behavior:

On Proton 7.0 and above, the connection fails after the TCP handshake, with no further data transmitted.