The game runs pretty well on my Nvidia 3090 w/ 535.113.01 drivers, but coop refuses to connect, even when crossplay is disabled. The coop session will attempt to load, but it will get about 1/10th of the way before a "Connection lost" message appears. Judging by other people's reports, this does not happen in Windows.

The game runs pretty well on my Nvidia 3090 w/ 535.113.01 drivers, but coop refuses to connect, even when crossplay is disabled. The coop session will attempt to load, but it will get about 1/10th of the way before a "Connection lost" message appears. Judging by other people's reports, this does not happen in Windows.

Multiplayer is currently not working for Linux / Steam Deck. EAC has not been enabled for Linux. Can confirm that agent is reported as unsupported or unknown when the EAC check is ran. Notice that when the EAC splash screen comes up, it never loads only skips and moves on. Email was sent to [email protected] with this information and a discord thread was started to ensure the issue has visibility.

@ULilBagel How do you check whether the agent is reported as unsupported?

Replying to https://github.com/ValveSoftware/Proton/issues/7175#issuecomment-1766561708

Thanks, I guess this is also why when one tries to 'Log in' it says that the game client has been tampered with?

@ULilBagel How do you check whether the agent is reported as unsupported?

Very simple: you try to Log In at any vestige and the game will inform you that has been tampered with.

@Emanem I asked that question a long time ago when there wasn't a Log In button and the multiplayer would attempt to connect before disconnecting. The Log In behavior was introduced in a recent patch.

@kisak-valve most of us tried to get in touch with the developer, asking if they can enable EAC for SteamDeck/Linux - this is a verified game but it doesn't work online.
Given we have other games (such as Elden Ring) which work just fine with EAC, not sure what else can we do to have the developers reply and address these issues?
Even the developer themselves claim it's fully verified, but the online component has been de-facto disabled for 3 weeks now?

Thanks!

Replying to https://github.com/ValveSoftware/Proton/issues/7175#issuecomment-1793393307

Finally, as of today this has been enabled. The game is fully playable on Linux/SteamDeck without issues now.

Can confirm that MP works great now. I even played crossplay with a person on PS5.

All Proton versions have wrong audio on intro video. Female voice is sounding only from right chanel.

Neither my Dualsense controller nor kb+mouse seem to be working in this game. Some buttons work, but others just don't. Focus on selections in the UI sometimes works only on the keyboard, sometimes only on the controller. A functionally identical controller/input issue I'm having in The Sinking City - another Unreal Engine game. However, there are many other UE games that work just fine for me. Maybe some common middleware ? I think both those games have "native" support for DS5 - that could be the problem. Toggling Steam Input to work around it doesn't help, though.

A similar issue with input I was having in the game WARNO I managed to figure out that it is only accepting input if the window is in the upper half of my second screen, but that game only has kb+mouse controls.
Switching to proton 8 in WARNO resolves the issue, in LOTF it doesn't, haven't tested TSC with p8 because I had given up on that one before I figured out p8 might work.

This is all on xorg.

EAC is suddenly not working anymore. I could play the game perfectly just a month ago.
It says: Failed to initialize dependencies

EDIT: Fixed it by clearing the variable SDL_VIDEODRIVER and removing it from my .zshrc file.

With the new proton 10, the controller disconnects and the game cant recognize it later. The same happens in No Rest for the Wicked. Proton 9 fixes everything with the controller

This is my system information https://gist.github.com/raaffaaeell/2d0829356d006eb310ffa4f2a8d2ab30

@raaffaaeell Could you please try to capture a log of the controller disconnecting by using this launch option? PROTON_LOG=+hid,+hidp,+hid_report,+plugplay,+rawinput,+dinput,+xinput,+joystick,+setupapi,+input %command%

Log will be stored by default in ~/steam-[appid].log. Thank you!

@raaffaaeell We believe we have a fix for the random controller disconnection issue - could you please test Proton - Experimental and see if your controller is still disconnecting randomly?

@alasky17 Sorry for the delayed response, I just tested 15 minutes of gameplay in one of the games I had the problem and it seems to be working fine now, thank you very much

Same problem as reported by @FilthySchmitz in https://github.com/ValveSoftware/Proton/issues/7175#issuecomment-2848749103. After launching I'm seeing error from EAC saying 'Unexpected error. (#1)'. Tried proton 9, hotixf and experimental. My spec:

• kernel 6.15.3-200.fc42.x86_64
• mesa 25.0.7
• gfx card: radeon 9070 xt

This problem looks to be EAC related, something regarding high core count. In my case, limiting those through this env variable:
WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 %command%
fixed the issue.

This problem looks to be EAC related, something regarding high core count. In my case, limiting those through this env variable: WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 %command% fixed the issue.

That work with me!

Is this something Proton can take care of out of the box, or should the game devs look at (maybe tweaking EAC)?