UnsupportedShow Details
Unknown
When changing proton versions you have to delete the ea prefix for the new one to work
fullscreen a little buggy borderless worked better
mouse was mostly off screen in game until launching with proton 10
Using proton 10 resolved all issues
Launched, then crashed and stopped working ever since.
At first launched without any issues, got into menu , settings and whatnot without a problem then after loading into multiplayer game it crashed within 5 sec and stopped working completely after that.
Somewhat of a struggle at times to simply start and play without stability issues, but when it works it works.
Seemingly random crashes of the EA App during gameplay, disconnects, random game crashes (often on map change). Zombie processes often remain on crash that must be manually killed.
Crashes will sometimes leave the origin client in a semi broken state where the game must be launched then restarted or re-authenticated to EA App.
Note for Nvidia, include in environment:
__GL_SHADER_DISK_CACHE=1
__GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1
Without these set, the game would recompile shaders at signifigant cpu load and delay at every launch.
gamescope -w 2560 -h 1440 -r 165 -b --force-grab-cursor -- %command%
Plasma 6: cursor leaves in windowed mode, fixed by using fullscreen.
GNOME 48: cursor escapes even in fullscreen, fixed with gamescope --force-grab-cursor.
No issues at all
GameScope 3.16.14.2:
[gamescope] [Error] xdg_backend: Couldn't create Wayland input objects.
[gamescope] [Error] xdg_backend: Failed to initialize input thread
After switching to Hyprland it revealed a Wayland input issue. Trying again on GNOME wayland session, the same error resurfaces, but enabling debug:full_cm_proto = true on Hyprland makes GameScope work smoothly again. I don't know of a workaround for GNOME.
Game ran also with Proton Experimental [bleeding-edge] when using a single display setup no tinkering required at all besides the Proton Version.
Game stopped at preparing vulkan-shader somewhere between 30-65%
tried several versions of proton
Steam Input defaulted to Pad to Keyboard translation. Just set the Gamepad Profile, the Game has native Controller support even though Steam reports the opposite.
works fine
Ran excellently on my Legion Go, didnt need any tweaking. Have VRAM set to 6GB. Around 50fps in multiplayer at 1050p, medium setting at 20 watts. 800p or higher TDP for better performance.
Overall works well, and friends on Windows confirm connection issues happen frequently regardless of OS.
Game initially failed to launch in the manner other people (and myself) have previously identified on this page. EA Launcher would instantly crash and the game wouldn't launch. After trying everything to fix this, one day it just randomly stopped happening and the game now works consistently.
Frequent (multiple per hour) disconnects from online services, issues with game recognizing that I've completed achievements to unlock weapon attachments.
PROTON_USE_WINED3D=0 DXVK_ASYNC=1 PROTON_NO_ESYNC=1 %command%
Very rare
Sometimes ends up on the wrong monitor (prob an issue with my system)
Unplayable levels of input lag on Proton versions other than Proton 9.0-4
Best chances of success when installing on system drive. May not require any tinkering on other systems.
A neat game with cool graphics and sound design!
For DirectX 12, performance is way worse. Even the main menu is lagging. For DirectX 11, it's all good.
Didn't notice any microtransactions anymore. There's an O.K. campaign. And there are a few customzation options for characters you play. I really like co-op missions!
Game works as intended through Cachy Gaming Meta packages. Installed Lutris from those packages. Game took a minute to manifest.
Installed Lutris EA-APP from their website
I was able to join friends and their invites. But game takes a long time for initial boot.
My experience without the Cachy Meta Packages were poor. Unable to start. After installing all dependency. Lutrus successfully installed the Ea app and I was able to run the game from Lutris. I have purchased the game from steam. Downloaded it through the ea app running lutris.
EA says "Preparing game..." but the game doesn't launch
It used to work perfectly before, but it suddenly stopped working overnight last week. I've tried several different Proton versions, tried deleting the wine prefix and reinstalling, nothing worked.
opens EA launcher, game doesn't t run
I tried using proton experimental, GE-10-10, 9.0-4, 10.0-1(beta) and 6.3-8, and deleting the prefix directory each time
Deleted the compdata folder and then disabled 2FA on EA Games website. Somehow it worked. I am unsure if Proton 10.0-1 beta helped but it launched the game and able to play online. I did get a network error but switching to proton 9.0-4 fixed the issue.
During some campaign missions it will lag but lowering graphics fixed it
Strange network error even though i can join multiplayer games
Game runs amazing but tickering setup to launch it was a pain
The game works, but it tries to buffer vulkan every time I play it. Moreover, my system becomes unable to shut down after using it
You can play it, but it's annoying
Game only launches once, if you're lucky
Also tried on Proton Experimental, 6.3-8, 7.0-6, Hotfix, GE10-8, and GE10-9.
Tried deleting the compatdata folder for the game to get it to reinstall EA Launcher with various versions of proton as per recommendations on this site. Tried reinstalling, etc. The game only started the very first time I launched it, and then randomly one other time after a reboot. It only launched the two times (and ran flawlessly during those sessions). Unfortunately, it seems the EA Launcher is broken as clicking launch only results in an EA Launcher popup saying "preparing game" for several seconds before closing and never actually opening the game.
When downloading the game heroic first downloads the Ea launcher, then in the Ea launcher you download battlefront 2, I don't know if Ea launcher works with proton GE 9-27 but in some forum I found that you run Ea launcher with proton experimental install the game and then run the game with whatever proton you like.
To initiate, trying to run the Ea launcher with the heroic launcher that's available on flatpak heroic would just crash and close, I had to install the heroic launcher for my specific distribution and that for some reason make heroic launcher to stop crashing, however I had to try and open the EA launcher multiple times to make it work, after that I just downloaded battlefront via EA launcher and everything worked
The EA app opens but the game itself won't
Used to work fine with the Steam default Proton but now doesn't work at all.
I initially used to have this installed on a mounted m.2 drive. It used to work on this drive. Due to EA app updates recently it will launch once and bork. If installed on my OS drive this does not happen.
Cannot install this game to a mounted drive, it must be installed on the main drive your OS is installed on otherwise it will bork after the first launch. Iv'e had similar odd situations with some Ubisoft games too.
Its frustrating I had this exerpience with this game but I am happy EA I can still play this game as its one of my favorite games to relax on.
Sometimes it takes multiple tries to start the launcher
I tried to get the game to run via Lutris. You need to own the game through the EA App—either by purchasing it or by having Game Pass or EA Play, where it's included. All you have to do is download and install the EA App inside Lutris. Then, open the EA App, download the game, and install it.
Before starting the game, go to the EA App settings in Lutris, click "Configure," then go to "Runner Options," and set the runner to Proton Experimental. After that, simply start the EA App and launch the game from there.
Sometimes it takes a few tries to get the EA App to launch properly. I'm not sure why, but just keep restarting it until it doesn't crash. It usually takes 5–6 tries for me, but eventually, the launcher stays open.
The game launches once on a fresh install, but after playing once it will not work. I tried all the suggested tinker steps, nothing works.
No longer works
Don't buy an EA game if you don't want it just taken away from you at any given point.
Solid 60 FPS on medium settings. The game runs really well on the Deck!
PROTON_USE_NTSYNC=1 PROTON_ENABLE_WAYLAND=1 DXVK_FRAME_RATE=60 gamemoderun %command%
Game gets killed by systemd-oomd after a while (iGPU), either lower the resolution or edit the oomd config (this appears to be a general issue with Fedora and Ubuntu specifically)
Initially worked perfectly after install, but after a system update or Proton update or something, the game would no longer launch (the EA launcher would start and do nothing). Deleting the wine prefix would allow the game to launch only to exit with a message about having "Failed to activate." After a lot of headache, the following worked:
- Ensure all the wine/EA processes are actually killed (in the broken state, it will not quit from Steam and requires a SIGKILL)
- Delete the wine prefix folder (e.g.
/path/to/SteamLibrary/steamapps/compatdata/1237950where1237950is the ID for this game) - Set to Proton 10.0-1 (beta)
- Start the game, which should re-install the EA launcher. If it hangs like before, kill the processes and restart the game. The game should run and get past the activation garbage
- Change back to whatever Proton version you were using before, if applicable
https://www.stopkillinggames.com/ there is an alternate reality where DRM doesn't exist
Not working as of today
Worked fine with no tinkering in Bazzite with default settings. Today I tried tinkering and changed bunch of versions and whatnot without a resolution. I tried to update the EA app within Wine enviroment to the proton default appID installation without success.
The EA app will open but the game itself will never open.
This seems to be an issue prevalent on Linux Mint systems, so whatever is causing the issue is likely persistent across systems.
Tried every version of GE as of the date of this report: FAILED. Lutris: FAILED. File Verification: FAILED. Reinstall and Play: FAILED.
For anyone considering writing a review, let it be known what installer the game works on. It seems after a week of investigating, playing the game on Steam is a lower success rate as opposed to others, but some reports don't divulge that information. Other reports mention memory leak as well but I have not gone that far.
EA App may launch but will not start Game
The furthest I got it to run, was getting an error message about EA App not being able to connect via Port 3216. After research that Port seems to be TCP. But allowing it through the firewall did not help and the error just continued to occur again and again.
Game installs from steam but in the forced ea launcher it refuses to let me start the game as "some features are disabled"
Electronic Sharts
EA app launches, but the game does not.
Tested on GE-Proton, Proton Hotfix, Proton Experimental and Proton 10 beta.
Needed to switch to proton 6.x.x to get past the EA login screen, then switched back to experimental once logged in. After that ran buttery smooth.
Mouse would escape window in window mode. Fixed via the input fix below.
Thanks to JonioN & Maitreya I had the same issue with input lag in the game, The game would have a warning about network issues, but it was actually the overlay issue.
Copied from Maitreya: Go to: ~/.local/share/Steam/steamapps/compatdata/1237950/pfx/drive_c/users/steamuser/AppData/Local/Electronic Arts/EA Desktop/user_[Number].ini and add the line user.igoenabled=0 there.
Flawless gameplay, didn't notice any issues or performance degradation.
Installs but will not get past EA launcher
EA Launcher opens up, but game never launches, and manually running game is disabled. Any and all fixes across the internet did not work, such as changing proton version, using heroic, running installer as non-steam game.
Had to let the EA App install using Proton 7 first, it's missing UI that way but it installs fine still. Launched with proton-cachyos after and it works as expected.
PROTON_USE_WINED3D=0 DXVK_ASYNC=1 PROTON_NO_ESYNC=1 %command%
Game start very long with ea....
