-
-
Notifications
You must be signed in to change notification settings - Fork 487
Star Wars Battlefront 2 fails to launch #4563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I had the same issue (flatpak, 2.17.0), but I was able to resolve it by following these steps:
Note: It seems that AUTH_PASSWORD is regenerated every time the game is launched – or at least it would seem so from my experience, although more thorough resting is required to confirm. This means that new link2ea url may have to be obtained for every launch from logs. |
I had the same problem, and when I looked at @Po11da 's solution I realized that what he had done was basically disable umu. So I tried doing just that on the original game (after installing it via the EA app) and it works.
|
Disabling umu at least results in the EA App showing up. |
TBH I just found random article online, which relied on article made back in the Origin days I followed most of the steps with some tweaks. At no point I knew what I was really doing or why it works, but I didn't want to bring the morale down. |
Can confirm disabling UMU works here too! |
I "solved" this by not using Heroic. |
I have a similar issue to OP, I'm using Bazzite. Disabling umu in Heroic did not fix. I've tried this approach:
However, I'm unable to find a way to get the EA App from staying open while running under GE-Proton-10-x, hotfix, experimental, or GE-Proton-9.27. The EA App opens, I can sign in, and then moments later from the interface it crashes. The most stable way to have the EA App + Epic Games Store apps open at the same time seems to be using wine-10.8-staging-x86_64, and I was able to install Star Wars Battlefront 2 (2017) in this configuration, but the game is an unresponsive black screen with only a cursor and choppy sound playing when it runs. This is why I'm trying to run it using GE-Proton. Curious if there's a known solution to what seems like the EA App intentionally not playing nicely with GE-Proton. |
Describe the bug
When trying to launch Star Wars Battlefront 2: Celebration Edition from the Epic Games store it always quits with the message
bwrap: Can't chdir to /app/bin/heroic/resources/app.asar.unpacked/build/bin/x64/linux: No such file or directory
Add logs
Steps to reproduce
Expected behavior
it should allow to install the game from the EA App and launch it
Screenshots
No response
Heroic Version
Latest Stable (Flatpak)
System Information
Additional information
No response
The text was updated successfully, but these errors were encountered: