I am missing BioShock Remastered but getting it to run on Linux does not seem feasible with at least the Steam version so far.

[https://www.codeweavers.com/search/?q=BioShock+Remastered](https://www.codeweavers.com/search/?q=BioShock+Remastered)
[https://lutris.net/games/bioshock-remastered/](https://lutris.net/games/bioshock-remastered/)
[https://appdb.winehq.org/objectManager.php?sClass=version&iId=35804](https://appdb.winehq.org/objectManager.php?sClass=version&iId=35804)

Quoting: WompoI am missing BioShock Remastered but getting it to run on Linux does not seem feasible with at least the Steam version so far.

[https://www.codeweavers.com/search/?q=BioShock+Remastered](https://www.codeweavers.com/search/?q=BioShock+Remastered)
[https://lutris.net/games/bioshock-remastered/](https://lutris.net/games/bioshock-remastered/)
[https://appdb.winehq.org/objectManager.php?sClass=version&iId=35804](https://appdb.winehq.org/objectManager.php?sClass=version&iId=35804)

Bioshock remastered works with proton. You need to disable esync, but it plays great so far. Bioshock 2 remastered requires a controller to get past the loading screens, but you can use a mouse and keyboard to play the game as long as you use the controller to push A to continue.

And I just finished BioShock classic from Humble Store through Wine not that long ago too. I might just wait for BioShock 2 classic to be added as a free extra and play that just for the continuity of experience.

Just tested Bioshock 1 with DXVK, runs great even on my lower end PC. Downloading Bioshock 2 as I write this, will look into the problem @chui2ch mentioned. :-)

EDIT: Apparently someone already found a workaround to the "press space to continue" issue: https://github.com/ValveSoftware/Proton/issues/482#issuecomment-436019150

Wine subforum thread.

So I have got BioShock 2 classic working under Wine using the prefix I previously setup to run BioShock classic from Humble Store.

The only thing I had to do different was patch the Bioshock2.exe using the 4GB Patch:
http://www.ntcore.com/4gb_patch.php

This resolves Bug #34658 as it gives the game enough virtual memory that it no longer hangs:
https://bugs.winehq.org/show_bug.cgi?id=34658

With the Steam version this would not work because of the DRM, saving me from having to mess around with ugly patch hacks on Wine itself to get the same effect. Just in case you needed another reminder on why fighting DRM is important.

Quoting: HamishThis resolves Bug #34658 as it gives the game enough virtual memory that it no longer hangs:
https://bugs.winehq.org/show_bug.cgi?id=34658

With the Steam version this would not work because of the DRM, saving me from having to mess around with ugly patch hacks on Wine itself to get the same effect. Just in case you needed another reminder on why fighting DRM is important.

There seems to exist another work-around. According to the last comment in the bug report you mentioned you won't need to patch the executable when using SteamPlay/Proton (with the Linux version of Steam), but just have to use PROTON_FORCE_LARGE_ADDRESS_AWARE=1. The entry here https://www.protondb.com/app/8850 (Original) seems to confirm this. The remastered version does not need this work-around https://www.protondb.com/app/409720
(I haven't tried this myself.)

Quoting: jens

Quoting: HamishThis resolves Bug #34658 as it gives the game enough virtual memory that it no longer hangs:
https://bugs.winehq.org/show_bug.cgi?id=34658

With the Steam version this would not work because of the DRM, saving me from having to mess around with ugly patch hacks on Wine itself to get the same effect. Just in case you needed another reminder on why fighting DRM is important.

There seems to exist another work-around. According to the last comment in the bug report you mentioned you won't need to patch the executable when using SteamPlay/Proton (with the Linux version of Steam), but just have to use PROTON_FORCE_LARGE_ADDRESS_AWARE=1. The entry here https://www.protondb.com/app/8850 (Original) seems to confirm this. The remastered version does not need this work-around https://www.protondb.com/app/409720
(I haven't tried this myself.)

I confirm the PROTON_FORCE_LARGE_ADDRESS_AWARE=1 for the original Bioshock 2
I did one of the reports.

I imagine that would not apply to playing the game through vanilla Wine like I am doing though. The 4GB Patch worked like a charm for me.

@Hamish yes, I think so. Your way would be the way to go for the GoG version and vanilla wine. Using SteamPlay/Proton i.c.w. Steam for Linux and aforementioned work-around would be the way to go with the Steam version.

Using the Steam version with vanilla wine and Steam for Windows probably wont work due to the reasons you gave. (Though not sure, I had patched my Dark Souls III executable for 21:9 support and the game still started fine using SteamPlay/Proton)

As of the last month or so I could not get BioShock or BioShock 2 to launch properly on my setup using the R600 Gallium3D Driver and my Radeon HD 6870 graphics card.

BioShock 2 gave the following error:
0047:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts.

Which led me to this forum thread:
[https://forum.winehq.org/viewtopic.php?t=30705](https://forum.winehq.org/viewtopic.php?t=30705)

I eventually discovered that I needed to override the OpenGL version to 4.1 to get both games to load:
export MESA_GL_VERSION_OVERRIDE=4.1 MESA_GLSL_VERSION_OVERRIDE=410

I am not sure what changed, seeing as how it used to work fine without this. Maybe something was added in either the driver or in WINE that awakened some new functionality that the engine will try to utilize if present. I was already running both games in DirectX 9 mode.

Last edited by Hamish on 21 Mar 2020 at 7:14 am UTC

As far as I understand it, my graphics card in theory has support for up to OpenGL 4.4 but to reach this it must have a driver that implements software FP64 shaders since it was not built into the hardware itself.

This means that outside of the ARB_gpu_shader_fp64 extension I do have full OpenGL 4.4 in my driver but without the override it will only report that it has support for OpenGL 3.1 due to the missing extension:
[hamish@Gehirn ~]$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.1 Mesa 19.3.4
OpenGL version string: 3.1 Mesa 19.3.4
[hamish@Gehirn ~]$ 

This is why overriding the version to OpenGL 4.4 is still able to expose the needed functionality as the support is there for everything except for FP64 shaders in both my hardware and driver.

Quoting: HamishI was already running both games in DirectX 9 mode.

The remastered versions are using DX11, which might be the reason why you need a higher OpenGL version. As for FP64, your GPU may not support it but Mesa has Soft FP64 support, naturally its' slower but doesn't lock you out.

Quoting: Avehicle7887The remastered versions are using DX11, which might be the reason why you need a higher OpenGL version.

I am using the Classic versions of both BioShock and BioShock 2.