Confused on Steam Play and Proton? Be sure to check out our guide.
We do often include affiliate links to earn us some pennies. See more here.

Just recently the Native Linux port of BioShock Infinite was updated to fix it failing to launch after an update.

As a quick reminder — back in September last year 2K updated various BioShock games to have their own launcher, because we all know gamers love extra launchers don't they? The previous article lists workarounds for them on Linux but as a side-effect they also broke the old Native Linux version.

It's taken over five months to sort it but they finally released an update and said:

Our last patch to BioShock Infinite on Steam was intended only for Windows but unexpectedly affected shared dependencies with the Linux version that made the game unplayable on some versions of Linux. We’ve since identified and fixed those conflicts and have verified those solutions addressed the issue in Linux (Ubuntu 22.10). We apologize for the inconvenience to our fans on Linux and appreciate their patience as we worked on a fix.

I checked on it and the Native Linux port launches fine now on Fedora.

Nice to see they finally did something, even though you could workaround it with Proton. For some it seems the Native Linux version actually works better though. I'm just surprised they actually fixed it, I was half expecting them to just leave it and tell people to use Proton at this point.

Article taken from GamingOnLinux.com.
38 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
The comments on this article are closed.
12 comments
Page: «2/2
  Go to:

Grogan Feb 13, 2023
Hah... no kidding. I had to switch to the Windows version (I rebought it on GoG with all the bioshock games after 2K tried to shove that broken launcher up my ass... those are some of my old favourites, I replay them every year or so on average)

I guess I'll give the Steam native version a try again then. It'll give me an excuse to enable mesa_glthread for something (I find that detrimental to most opengl games, only a few benefit, so I have it disabled globally, toggled off at build time, and only use it per-instance)

I'm quite glad to hear that got some needed love.
Grogan Feb 14, 2023
I appreciate that this is working again. I installed it again last night and tested it out and it works decently.

Unfortunately, the Windows version I have in GoG works considerably better. The Linux "port" is that eON wrapped shit, which is less than ideal. Running it through OUR DXVK -> Vulkan is much better translation.

It is also a better experience in general, as it does not have that annoying, delaying "Connecting to 2K account" and that stupid "not linked... press [J]" 2K icon in my menus. That can take several seconds and what would happen if it stalled?

It is also a better experience in that configuration isn't buried in "~/.local/share/irrationalgames/bioshockinfinite/GameDocuments/My Games/BioShock Infinite/XGame/Config" with the game saves buried in "steam/userdata/yoursteamidnumber/8870/remote/SaveData. The addition of the 2K launcher changed that.

In the GoG version it's just appdata/local for the config and Documents/My Games for the saves, in the wine prefix like normal.

So thanks (but no thanks) for all the fish.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.