Arch Linux

patoll

Member

Registered: 2025-05-22

Posts: 2

Battlefront II via Steam not working

If I start Battlefront II via Steam, it opens the EA App, runs the EA App installer and then proceeds to open the EA App and show a Windows saying "preparing game". That window then dissapears and the EA App minimizes. One or two minutes later the EA App shortly opens and then crashes.

I have already tried all Proton versions form 6 to 10, GE Proton 7-55, GE Proton 10-3, Hotfix and Experimental, some crash the game earlier, some later.

I also tried using Proton 7 while installing the EA App, then stopping the game and using Experimental to start the game. That actually worked once, but the game didnt detect my keyboard, only my controller and upon restarting the game/trying this again it didnt work anymore.

Running the game/EA App through Lutris isnt really an option as the play button in the EA App is just grayed out and there being no install option due to the game being managed by Steam.

I Also already tried switching from Wayland (Hyprland) to Gnome under XOrg with no effect.

Does anyone know how I can get the game to run consistently?

Sorry for accidentally posting this twice

Last edited by patoll (2025-05-22 14:55:07)

alejandro

Member

Registered: 2019-12-30

Posts: 4

Re: Battlefront II via Steam not working

I have a similar issue, I have been playing for a couple of days and all of the sudden (even in the same day as my last gameplay, without updating the system) I only see the "preparing game" and then nothing. I saw once "rendering vulkan shaders" (or something similar, can't remember) but then nothing

ankabo

Member

Registered: 2025-07-14

Posts: 16

Re: Battlefront II via Steam not working

I would try to install "bottles" and there install the EA App (its pre configured).
Give it a try, because I dont trust a gaming platform that is calling another gaming platform ;-)

yilmaz

Member

Registered: 2025-01-17

Posts: 4

Re: Battlefront II via Steam not working

Having the same issue, it was working yesterday, and today it stopped working. I've tried everything from deleting the wine prefix, trying various Proton versions including GE, gamescope (it was working until i tried running the game with gamescope, it didn't work, but it continued not working after I stopped using gamescope), downgrading the kernel to 6.14.9 along with the Nvidia drivers, nothing fixed it. EA app says preparing game, nothing happens for 5 minutes while Steam still says the game is running, then either the EA app opens again for a split second and closes, or nothing happens and it stays like that forever.

I'm seeing a lot of recent reports in ProtonDB about the game suddenly stopping working, but seeing as this happened even without updating anything for a lot of people, I'm confused.

John-Something-Something

Member

Registered: 2024-12-04

Posts: 20

Re: Battlefront II via Steam not working

Hello, sorry for the later reply and for my poor english.
I am a Newbie, so sorry for any possible error.
I did not have the game, so i can't test .
Can you try to run it through wine and redirect the errors to a log file so we can analize it?

Just as a sanity check in case you do not know how to use  steam generated prefixes read the following. Otherwise you can just jump this part if you know.

Steam stores all your prefixes by default under ~/.local/share/Steam/steamapps/compatdata. But, they are all named with random numbers(or at least random for me) and to find out witch one is the prefix steam is using for your game you will need to head one directory back to ~/.local/share/Steam/steamapps/
In this directory you will find files that match the model appmanifest_XXXXXXX.acf (Where X is a random number). You will need to cat/read all those files until you find one that matches your target(Battlefront II for example). Once you know in witch prefix your game is located you can use the system variable WINEPREFIX=~/.local/share/Steam/steamapps/compatdata/randomNumberPrefix/pfx .This will allow you to get the errors from the executable that will run through normal wine.
Steam stores the game executable usually at ~/.local/share/Steam/steamapps/common/.
WINE IS NOT PROTON and because of that fact you may get some errors that did not will appear when you run the game from steam and it may crash even before anything different from running on steam happens. In this case we will go to proton/steam troubleshooting.
Here is an example, my target game is Sniper Elite 5:

cd ~/.local/share/Steam/steamapps/
cat appmanifest_1029690.acf

The output will look something like this:

"AppState"
{
	"appid"		"1029690"
	"Universe"		"1"
	"name"		"Sniper Elite 5"
	"StateFlags"		"6"
	"installdir"		"Sniper Elite 5"
	"LastUpdated"		"1735317085"
	"LastPlayed"		"1745184149"
	"SizeOnDisk"		"107679997745"
	"StagingSize"		"0"
	"buildid"		"16533524"
	"LastOwner"		"76561199150827619"
	"DownloadType"		"4"
	"UpdateResult"		"0"
	"BytesToDownload"		"7896650272"
	"BytesDownloaded"		"0"
	"BytesToStage"		"0"
	"BytesStaged"		"0"
	"TargetBuildID"		"18805095"
	"AutoUpdateBehavior"		"0"
	"AllowOtherDownloadsWhileRunning"		"0"
	"ScheduledAutoUpdate"		"1754633307"
	"InstalledDepots"
	{
		"1029691"
		{
			"manifest"		"8969215143174066692"
			"size"		"852750896"
		}
		"1029692"
		{
			"manifest"		"8815250204752132903"
			"size"		"29752817357"
		}
		"1029693"
		{
			"manifest"		"4867551714124288426"
			"size"		"63913591"
		}
		"1029694"
		{
			"manifest"		"2627073715339891225"
			"size"		"32"
		}
		"1029695"
		{
			"manifest"		"7828996838065525636"
			"size"		"2769729734"
		}
		"1029696"
		{
			"manifest"		"760633837610679207"
			"size"		"36484796916"
		}
		"1029697"
		{
			"manifest"		"6752346799350258443"
			"size"		"32038689615"
		}
		"1029698"
		{
			"manifest"		"5617116148313554621"
			"size"		"32"
		}
		"1034302"
		{
			"manifest"		"4856102686006355147"
			"size"		"32"
		}
		"1724940"
		{
			"manifest"		"2888072743867185638"
			"size"		"2279059347"
			"dlcappid"		"1724940"
		}
		"1724942"
		{
			"manifest"		"4860612510972632829"
			"size"		"1603478354"
			"dlcappid"		"1724942"
		}
		"1872750"
		{
			"manifest"		"6244346987595837129"
			"size"		"1834761903"
			"dlcappid"		"1872750"
		}
	}
	"SharedDepots"
	{
		"228988"		"228980"
	}
	"UserConfig"
	{
		"language"		"brazilian"
	}
	"MountedConfig"
	{
		"language"		"brazilian"
	}
}

Pay attention to these specific lines of the file:

"appid"		"1029690"
"name"		"Sniper Elite 5"

appid is the name of the prefix you are searching for, for me it is 1029690, so i know now that  ~/.local/share/Steam/steamapps/compatdata/1029690/pfx is the folder were the prefix for Sniper Elite 5 is located on my machine.
With this information all you need to try is a wine commad that uses that prefix and stores the errors in a file. The following code does that and removes duplicated entries:

env WINEDEBUG="fixme-all" WINEPREFIX="/home/pedro/.local/share/Steam/steamapps/compatdata/1029690/pfx/" wine start /i "/home/user/.local/share/Steam/steamapps/common/Sniper Elite 5/SniperElite5.exe"  2>&1 | uniq | tee wine_log.txt

If you have prime and a nvidia card in your machine it is a good idea to make sure the game will run with that card

prime-run env WINEDEBUG="fixme-all" WINEPREFIX="/home/user/.local/share/Steam/steamapps/compatdata/1029690/pfx/" wine start /i Index of "/home/user/.local/share/Steam/steamapps/common/Sniper Elite 5/SniperElite5.exe" 2>&1 | uniq | tee wine_log.txt

And, remembering, you will need to replace 1029690 with the directory steam uses to store your prefix, SniperElite5.exe with the name of the executable of BattlefrontII and user with your user name.
If you can get the log file, plese post it here so we can analyze. Sorry for any misunderstanding
Observations: I just copy-pasted these commands from my paste file and modified it, i did not re-tested the command yet. Please warn me if i made some really big mistake on this command so i can edit on my commands paste file.

Last edited by John-Something-Something (2025-08-05 01:06:37)