Enable multiplayer for Titanfall 2 from EA Games with Lutris
I have installed the Flatpak version of Lutris from Pop_Shop in PopOS. From within Lutris, I have installed the EA App, which I have then used to download several games from my library. Unfortunately, when starting up Titanfall 2 from inside the EA App, multiplayer is unavailable. Singleplayer runs fine with no issues, however, the "Launch Multiplayer" button is locked, with a message stating "Contacting Respawn servers" that never ends. At the same time, Battlefront II connects to its servers just fine, so I'm assuming Titanfall should too, yet it doesn't. How do I resolve this issue?
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
This sounds like an anticheat issue. You may or may not be completely at the mercy of the developers. Titanfall 2 does use EAC, though, and Steam does have a Proton runtime for it (which should already be in your library but might not be installed). Again, this is not a guarantee this will solve your issue because anticheat software does not play well with Linux for numerous reasons.
0 comment threads
My guess is that this is an anti-cheat problem. The symptom of those is often everything working on Linux except the multiplayer, with no explanation.
I don't play Titanfall 2, but apparently it uses Easy Anti Cheat. EAC and Valve Anti Cheat are two very common ones. Usually, VAC is considered restrained and Linux friendly, while EAC is more aggressive (borderline rootkit). Since Linux is designed to have security against malware, it's hard to get EAC to work right on it.
Commercial launchers like Steam or Epic Game Store can sometimes include some black magic to placate the anti-cheat, so the game works on those but not with third party launchers like Lutris. So that's worth a try. You could also try asking the developer for support, they should at least be able to confirm whether it's the anti-cheat causing the issue.
According to ProtonDB it should run, though: https://www.protondb.com/app/1237970/
0 comment threads