Egosoft announced today that the free DLC X3: Farnham's Legacy that was released back in April is now officially out with a Linux build and there's more.
X3: Farnham's Legacy is set in the years following X3: Albion Prelude, as the chaos caused by the gate shutdown really takes hold, X3: Farnham's Legacy starts very differently to previous games in the X3 series. It was developed over five years by long-term members of the Egosoft community in close cooperation with the team at Egosoft.
YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Direct Link
Direct Link
It's not just a whole new story, the free expansion also brings with it lots more including:
- (Almost) Everything from X3: Terran Conflict and X3: Albion Prelude
- Exploration tools and explorers guild
- Diplomacy and dynamic relations
- New drone carrier and armoured transport ships
- Player headquarters with new advanced facilities
- A unique and very special new ship
- Station-building and complex planning services
- Ship browser and hyperlinked encyclopedia
- New piracy options and gameplay
- Real sector ownership
- Improved logs and graphs
- Enhanced modding support
- Lots and lots of smaller improvements!
Along with the Linux release, Egosoft also tweaked other parts of the series too:
X3: Terran Conflict
X3: Albion Prelude
- [GOG Linux only] Updated to version 3.4 (2017)
- [Steam only] Simplified first-time setup on Windows
- Fixed lib compatibility issues on Linux
- Fixed several voice samples in German version
- [GOG Linux only] Updated to version 3.3 (2017)
- [Steam only] Simplified first-time setup on Windows
- Fixed lib compatibility issues on Linux
Really amazing to see the long-term support here from Egosoft for their games.
You can buy the X3 series on GOG, Humble Store and Steam.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: whizseLooks like Proton-6.10-GE-1 is reported to be working
So I made the compatibilitytools.d dir and put that in, I also put in 6.12-GE-1 for good measure, but it doesn't start up with either one, I have my steam installed in /usr/local/games/Steam/ and maybe that's the reason, cause I am getting this errmsg from steam:
pressure-vessel-wrap[14224]: W: Using libGLX_mesa.so.0 from provider system for some but not all architectures! Will take /usr/share/drirc.d from provider.
pressure-vessel-wrap[14224]: W: Binding directories that are located under "/usr/" is not supported!
bwrap: Can't chdir to /usr/local/games/Steam/steamapps/common/X2 - The Threat: No such file or directory
So, meh, still not painless :( Thanks for trying though!
0 Likes
Quoting: gilboaAs far as I know, LGP's X2 still can be made to work
Do you have any more info on this? Preferably a painless recipe to follow, but I'll take anything.
0 Likes
Quoting: GrifterQuoting: gilboaAs far as I know, LGP's X2 still can be made to work
Do you have any more info on this? Preferably a painless recipe to follow, but I'll take anything.
Sadly enough, never tired it myself.
I'll see if I can get it to work, and report back.
- Gilboa
0 Likes
Sadly enough, no go.
I managed to get a couple of old libraries required to start the game, but it fails when trying to create the GLX context.
As I have zero experience in debugging GLX applications (and OpenGL in particular) its out of my league.
That said, have you tried using proton + steam to run X2?
- Gilboa
I managed to get a couple of old libraries required to start the game, but it fails when trying to create the GLX context.
As I have zero experience in debugging GLX applications (and OpenGL in particular) its out of my league.
That said, have you tried using proton + steam to run X2?
- Gilboa
0 Likes
Quoting: GrifterI have my steam installed in /usr/local/games/Steam/ and maybe that's the reason, cause I am getting this errmsg from steam:Games installed in /usr too? That seems like a really bad idea:
pressure-vessel-wrap[14224]: W: Using libGLX_mesa.so.0 from provider system for some but not all architectures! Will take /usr/share/drirc.d from provider.
pressure-vessel-wrap[14224]: W: Binding directories that are located under "/usr/" is not supported!
bwrap: Can't chdir to /usr/local/games/Steam/steamapps/common/X2 - The Threat: No such file or directory
https://github.com/ValveSoftware/steam-runtime/issues/288
FWIW, I tried X2 myself with Proton-6.10-GE-1 and it ran fine. Or, at least for the 10 minutes or so I played. With vanilla Proton (6.3-5 I think?) there was audio problems. No sound during intro videos or cut scenes. In-game seemed to be working fine though.
0 Likes
Quoting: whizseGames installed in /usr too? That seems like a really bad idea
It's never seemed like a bad idea to me, that's where they belong =) All a mix of native, steam-native, and steam-proton, never had an issue except for these error messages from glorious eggroll, more like inglorious deflated egg to me :(
EDIT: I should mention that steam itself is installed in /usr/local/games/Steam, so if anyone has problems like that maybe they're trying to access /usr/local from a steam installed elsewhere? I dunno, either way, has worked fine for me for a looooong time =)
Last edited by Grifter on 25 July 2021 at 8:55 pm UTC
0 Likes
Quoting: GrifterIt's never seemed like a bad idea to me, that's where they belong =) All a mix of native, steam-native, and steam-proton, never had an issue except for these error messages from glorious eggroll, more like inglorious deflated egg to me :(Seems quite odd to me. Anything in /usr should be read only for normal users. Applications that need to write data shouldn't do so to /usr. But I guess it's personal preference.
Anyhow, it's a complete no-go with containerized Proton (5.13 and up I think?).
0 Likes
I don't write anything to /usr, that belongs to the package manager, /usr/local is for me though. As for proton, I use proton 5.13 it looks like, and like I said I haven't had any problems yet.
0 Likes
Quoting: Grifterpressure-vessel-wrap[14224]: W: Binding directories that are located under "/usr/" is not supported!
Pressure Vessel is sandboxing used by more modern Proton and there are very good reasons for not adding /usr to the container and it comes with a ton of caveats: https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/tree/master/pressure-vessel and this is a PITA for some other applications too. For example Opentrack and it's wine-glue
It speaks for itself that X3 is noted as example why this approach may have issues:
QuoteSome games have distinct app IDs but share data: for example,
X3: Terran Conflict (ID 2820) and X3: Albion Prelude (ID 201310)
share SteamApps/common/X3 Terran Conflict.
And
QuoteFor example, if X3: Terran Conflict and X3: Albion Prelude
are to share data, they would have to both be run with for example
--freedesktop-app-id=com.egosoft.X3TC or --steam-app-id=2820.
…let me know if someone finds the OFF switch for this.
Edith says: There is even a ticket for /usr/local https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/issues/30
Last edited by beko on 26 July 2021 at 7:31 am UTC
0 Likes
Patreon
PayPal
See more from me