this post was submitted on 21 Jun 2023
17 points (94.7% liked)

Linux Gaming

15377 readers
303 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 1 year ago
MODERATORS
monolalia
17
EAC Seems broken on Arch? (lemmy.simpl.website)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/linux_gaming
15 comments fedilink hide all child comments
 

I recently installed BattleBit Remastered on Steam (uses EAC). Upon trying to run the game, I only get as far as a screen telling me to ensure EAC is installed. I tried their "repair EAC" option in steam, and there was no change (a terminal opens, blinks, and closes again). I tried a system update to see if that would help, but no dice.

Now, when I try to launch Apex Legends (a game which I play all the time), I see EAC loading extremely slowly, then it goes away, but the game never launches (though Steam still shows the title as running).

Is anyone else having issues right now (with an up to date system)? Has anyone else experienced this before?

Edit: Decided to format my OS drive and move to Fedora. Using the same steam library, both games are now working. Clearly some package ended up misconfigured, but I have no idea what or why.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

I just switched from flatpak to rpm because of two annoying issues

Firstly steam kept forgetting my two other disks and I kept having to add them again via settings/storage

Secondly I couldn’t get steam to start at boot without messing about with other config.

Both these issues are solved by switching to the rpm/native version

Running Fedora 38 Btw

[–] dobo99 1 points 1 year ago

The first point was solved after the ui update and I never had to do with the second point..