You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Needing Steam to download Proton is not necessary, specially with GOG support now Steam is a thing that is not a given. The big issue is host dependency. The list of packages the user needs to install may grow big without Steam, and normal Proton just isn't supposed to be run in the first place without the Steam Runtime. There are prebuilt protonified wine tars out there, haven't really investigated it much, just used the first one that I found.
Putting the script in .faforever/bin and pointing the client to it gets you a working game, mostly. The latest DXVK version has working effects without the need for the configfile.
I recently upgraded Proton from 5.13 to 7.0.6 and I'm not getting in-game videos running somehow. It's a minor problem, but it is there.
Ideally, eventually, somehow, we get the script(s) into the java client and just let people play oneclick. It annoys me that the client would be the 99th instance of software implementing what PlayOnLinux/Lutris/Heroic/Bottles do, but tbh it's not much code.
The text was updated successfully, but these errors were encountered:
One of the things I've wanted to do is to move the entire thing into container image(s), somewhat similar to how the Steam Runtime does it. That could solve a lot of the annoying issues relating to the environment such as library versions being wrong. This isn't exactly foolproof, notably because graphics libraries are pretty finicky, but it could help. The Steam Runtime uses bwrap and their own runtime named pressure-vessel (https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/blob/main/docs/container-runtime.md) which seems to deal with some of this so we could look into using that. Code related to the Steam Runtime is permissively licensed.
The script already supports running the game without Steam, but that bit isn't yet documented or tested. Doing BYPASS_STEAM=1 GAME_PATH="/path/to/FA" WINE_PATH="/path/to/wine" ./setup.shshould in theory be enough to set things up without Steam.
The script currently defaults to Proton Experimental as that (in my experience) generally results in fewer problems. It may be better to directly pin to a prebuilt version of Proton though.
There are a lot of client integration features to be desired. The client updater on Linux is currently entirely nonfunctional. It may be better to rewrite these scripts in Python for better user experience.
iczero
changed the title
Ship prebuilt Proton/Wine to avoid Steam
Switch to the Steam Runtime
May 13, 2024
I've always been using my own crappy script to run the game. Just recently discovered this repo, which outclasses it greatly in many aspects.
Here:
https://gist.github.com/p4block/8d947f85fa707b433af359a699b367fb
Needing Steam to download Proton is not necessary, specially with GOG support now Steam is a thing that is not a given. The big issue is host dependency. The list of packages the user needs to install may grow big without Steam, and normal Proton just isn't supposed to be run in the first place without the Steam Runtime. There are prebuilt protonified wine tars out there, haven't really investigated it much, just used the first one that I found.
Putting the script in .faforever/bin and pointing the client to it gets you a working game, mostly. The latest DXVK version has working effects without the need for the configfile.
I recently upgraded Proton from 5.13 to 7.0.6 and I'm not getting in-game videos running somehow. It's a minor problem, but it is there.
Ideally, eventually, somehow, we get the script(s) into the java client and just let people play oneclick. It annoys me that the client would be the 99th instance of software implementing what PlayOnLinux/Lutris/Heroic/Bottles do, but tbh it's not much code.
The text was updated successfully, but these errors were encountered: