BioShock Remastered (409710)

[tr37ion]

Arch Linux
Kernel 4.18.3
Proton 3.7
Nvidia GTX 1070 - nvidia-beta 396.54
KDE Plasma 5.13.4
KDE Framework 5.49.0
Qt 5.11.1

BioShock Remastered works but has texture quality issues. Playing around with GFX settings didn't help either.

[d10sfan]

Also seeing this on Xubuntu 18.04

[robertc]

See the same on Antegros. Also there is a pause of about 30 seconds every time I save the game. I select save, there's a long pause, then the 'saving' screen comes up.

[rkunschke]

The issue with the textures are a problem for me too. But i tested it with bioshock 2 and bioshock 2 remastered. Tomorrow i will do the same test in Bioshock 1 and Bioshock 1 Remastered to Confirm it.
I'm also on Arch but with ZEN Kernel 4.18.4
Nvidia dkms driver
KDE Plasma desktop

[dubigrasu]

For the textures issues and long hangs when accessing the menus, try:
PROTON_NO_ESYNC=1 %command%

[rkunschke]

This worked for Bioshock 2 + Remastered for me :) great thank you!

[btegs]

I'd love to see Valve test both 1 and 2 with the config setting PROTON_NO_ESYNC to 1 in the config by default and adding to their whitelisted games. After more testing of course. :-)

We should push for 1 and 2 since we have Infinite native on Linux.

[1heghost]

For me the game doesn't even start after installing.
Maybe my llvm is too old.
Tested Proton 3.7-3 and 3.7-4.

System is the following:

CPU Brand: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Arch Linux Kernel Version: 4.18.4-arch1-1-ARCH
X Window Manager: KWin

Driver: X.Org AMD Radeon(TM) HD 8800 Series (PITCAIRN, DRM 3.26.0, 4.18.4-arch1-1-ARCH, LLVM 6.0.1)
Driver Version: 3.1 Mesa 18.1.7

[fafryd1125]

@1heghost Please try steam-runtime

For me the game doesn't even start after installing.

It only happens if you run the game by steam-native

Tested:
Arch Linux
Kernel 4.18.5-zen1-1-zen
Proton 3.7-4 Beta (the game only starts with steam-runtime)
RX 580 8GB
Driver Version: Mesa 18.2.0rc4
launch option: PROTON_NO_ESYNC=1 %command%

[1heghost]

Please try steam-runtime

Got the same issue with steam-runtime.
Here's the proton.log. If you need further information let me know.

steam-409710.log

[XakepSDK]

Doesn't run with steam-native or steam-runtime
System info:
https://gist.github.com/XakepSDK/fc796a8ac0dd1c21f25b62903deb1af3
Proton 3.7-3 || 3.7-4 Beta

With steam-runtime - black rectangle appears and after some seconds disappears

Launch log: https://gist.github.com/XakepSDK/3b1d647e08127377f77f41d0809dc0eb

[kisak-valve]

Hello @XakepSDK, vulkan support for the Haswell chipset is incomplete and anomalies with dxvk is expected. You may have better luck adding PROTON_USE_WINED3D11=1 %command% in the game's launch options.

[XakepSDK]

@kisak-valve thank you, game launches, but fps is ~1-5 in menu, even with lowest graphic settings possible. I did not tried to start SP.

[Xeers]

The games work "perfectly" with:
BioShock: PROTON_NO_D3D11=1 PROTON_NO_ESYNC=1 %command%
BioShock Remastered: PROTON_USE_WINED3D10=1 PROTON_NO_ESYNC=1 %command%

[stevethepocket]

I can't get the game to detect and let me use the Steam Controller. The usual "CONFIG LOADED" popup doesn't appear, and the option to turn on controller mode in the options menu is grayed out. Going into the Steam Overlay and selecting STEAM CONTROLLER CONFIGURATION brings up the config I had selected. When I launch the game with an Xbox 360 pad plugged in, the game recognizes it properly. This does not appear to be an inherent issue with Proton; when I launched RAGE, the "CONFIG LOADED" popup appeared right after the Steam Overlay one and the game was controllable with the controller. It's also not an issue with the game itself; under Windows, my config successfully fools it into thinking I'm using an Xbox pad and it behaves accordingly.

HOWEVER: Confirming when this has been fixed might prove impossible, because I tried launching the game from Big Picture mode and it worked correctly, and then I tried launching it from the desktop and again it worked correctly. So it's "fixed" thanks to a convoluted workaround, and I don't know if I'll ever be able to reproduce the original problem.

[kisak-valve]

Hello, is anyone seeing an issue with this game and Proton 4.11 that would block it from being whitelisted?

[stevethepocket]

Yes, actually. I didn't realize it at the time, but when I start a new game, there's some weird lag during the opening cutscene that causes my character to die by drowning, somehow. Despite drowning not being a mechanic anywhere else in the game. Some cursory research shows that people occasionally had this problem with the Windows version as well, and it's definitely a bug in the base game that's allowing this to happen at all, but it does mean I can play the game in Windows and not with Proton, so take that for what it's worth.

Also, it appears that the game will only work when launched with the aforementioned parameters. I'm assuming that once it's whitelisted, Proton will be instructed to use those settings by default?

[CSahajdacny]

I have an Out Of The BOX experience with PROTON_NO_ESYNC=1 %command%

[shoober420]

Compatibility Report

• Name of the game with compatibility issues: BioShock Remastered
• Steam AppID of the game: https://steamdb.info/app/409710/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.82
• Kernel version: 5.6.5-zen
• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfonvidia
• Proton version: 5.0-6

NO ESYNC AND FSYNC LOG:
steam-409710no.log

ESYNC AND FSYNC LOG:
steam-409710yes.log

Symptoms

1. Brightness slider still broken

2. No sound during intro videos and game cinematics

3. "PROTON_NO_ESYNC=1" and “PROTON_NO_FSYNC=1” are still required to fix low resolution textures.

doitsujin/dxvk#1581

[Simmonz]

I expect you'd need both to be disabled for the correct workaround effect with an fwm-enabled kernel build. (PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%)

You're awesome ! Disabling both solved the issue for me.

[Ninmi]

Linux: 5.14.14-arch1-1
LLVM: 12.0.1.5
Mesa: 21.2.4-1
Proton: Default (Assuming 3.7)
I'm not able to use Proton versions too recent as they break input (can no longer bind non-ASCII keys and mouse sensitivity goes crazy high up. They also don't solve the problem I'm having.)
CPU: R7 1700
GPU: RX Vega 64

launch options:
PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%

The issue:

I'm getting very poor performance. Most of the game hovers at around 20-30 fps. There's also a significant amount of stuttering (with new areas, it seems).

Is there anything I can do to improve the performance? Graphics settings predictably have no impact on framerates, other than disabling real time reflections providing a boost in some areas. I don't think I should need to disable anything to begin with with my hardware.

[kisak-valve]

Hello @Ninmi, there is no default Proton version. At some point you chose a version that you want Steam to use. In Steam's library view, you can select the game, then click the ⓘ on the right side to get some additional details. There should be a line that appears which reads something like "Runs on this computer via Steam Play. Proton # selected by you for this title."

I don't recall hearing about an issue with binding non-ascii keys in games. What's the newest Proton version you know is not affected by that behavior and the oldest Proton version you know doesn't behave as intended? Also, what kind of keyboard are you using?

PROTON_USE_WINED3D and the older PROTON_USE_WINED3D11 launch options tell Proton to use wine's DirectX to OpenGL render path instead of DXVK to translate DirectX to Vulkan. This is not supported and is known to cause a significant performance penalty.

[Ninmi]

The game crashes upon launch without PROTON_USE_WINED3D11=1, and judging by previous reports it seemed mandatory. Here's what Steam logs had to say as when running the game without it:
https://gist.github.com/Ninmi/69d663b5b69bb4a1d3b6e2aa386aa233
The crash happens with newer Proton versions as well. Tried with both AMDVLK and Vulkan Radeon.

5.13-6 is the last one where input works properly. I actually haven't tested any other key than ä and ö. These map properly to adiaeresis and odiaeresis on older Proton versions. Interestingly though, I'm able to skip intro videos only on the newer Proton versions. I suspect this issue hasn't come up before because very few people use a svorak keyboard (rearranged in firmware, actual x keyboard layout is set to fi for the normal qwerty Finnish layout) layout and normally these keys are on the other end of the keyboard. I'm also running fcitx5. I'm using Ergodox EZ.

6.3-7 also introduces issues in color gradients. (E: with PROTON_USE_WINED3D11=1)

Edit: I noticed I was missing lib32-vulkan-radeon after looking at the logs (not sure if it's even necessary), but installing it did not remove the crash. Here's the log after installing the 32bit library (and using a newer Proton):
https://gist.github.com/Ninmi/1ef7e4a7015e4050026d4ab56e387675

[kisak-valve]

terminate called after throwing an instance of 'dxvk::DxvkError' in your second log tells us that DXVK encountered a problem initializing the vulkan render path. Please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[Ninmi]

Game launch log 3: https://gist.github.com/Ninmi/0adafe41923fbd187d3883da69a77418
System info: https://gist.github.com/Ninmi/a1f2378b17f327963acfdf43506aac02

The terminate called after throwing an instance of 'dxvk::DxvkError' has not occured since, and the game launch log is getting less and less helpful. But the system info does seem to indicate some issues with Vulkan, which is weird since I've been playing Doom2016 and Dota 2 just fine.

More possibly related info:
I run Steam with export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json because for some reason my machine defaults to AMDVLK and I don't really know how to fix it.
I also have a second (power unplugged) GPU in the machine (RX 460), but I doubt that makes a difference either.

Also perhaps related, I get these when booting up Steam:
Vulkan missing requested extension 'VK_KHR_surface'.
Vulkan missing requested extension 'VK_KHR_xlib_surface'.
BInit - Unable to initialize Vulkan!

[kisak-valve]

VK_LAYER_AMD_switchable_graphics, which is bundled with AMDVLK forces that driver to be used over other vendors. AMD has separate 32 bit and 64 bit Vulkan driver ICDs and by setting VK_ICD_FILENAMES to only the 64 bit ICD, it breaks the 32 bit render path (https://gist.github.com/Ninmi/a1f2378b17f327963acfdf43506aac02#file-steam_system_info_23_10_2021-L155-L169).

Doom 2016 and Dota 2 are 64 bit games, so they would use a working 64 bit render path. I'm guessing you wanted something like export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json. Alternatively, there should be something like AMD_VULKAN_ICD=RADV which VK_LAYER_AMD_switchable_graphics should honor, or remove the amdvlk and lib32-amdvlk packages.

[Ninmi]

Setting both ICDs did not work, neither did AMD_VULKAN_ICD=RADV, so I opted to eradicate AMDVLK since it hasn't been useful in a while anyway. Rebooted my PC as well for good measure and the game now runs at around 80-170 fps. The stuttering still remains when loading new areas (even at newer Proton versions) and it would be nice to get rid of it, but the game is playable now.

Interestingly the Steam client works better now as well. It seems like you really should only get AMDVLK on the side if you really have to.

Thanks for the help.

[SeongGino]

Seems to be that both this title and BioShock 2 Remastered are crashing on launch.
steam-409710.log

This has worked before, not sure what's changed.

[Corben78]

Seems to be that both this title and BioShock 2 Remastered are crashing on launch. steam-409710.log

This has worked before, not sure what's changed.

As it's a 2K game, maybe check for core dump files. So far it happened to me only with Borderlands games. But if core dumps are enabled on your system, and the game crashed creating such a core file, it prevents the game from starting. Deleting the core file should let the game start again.
See the Borderlands 2 entry on PCGamingWiki for details.

[SeongGino]

There are no such coredumps in the relevant directory:

Also went into the prefix to remove both Documents/My games/BioshockHD and %APPDATA%/BioshockHD folders. No change.

I've also seen the most recent posting on ProtonDB reflecting this.
The EGS version downloaded through Heroic and played in a shared prefix (with other Epic Store games) on the other hand works fine.

[Corben78]

@SeongGino it was worth a try.
I tested Bioshock Remastered myself, unfortunately, I cannot reproduce the issue.
With Proton 7.0-3 it works as intended, with Proton experimental-7.0-20220805 it starts for me as well, but MangoHud isn't working.
Additonally to disabling ESYNC and FSYNC I added -nointro to the launch options:
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% -nointro

• steam-409710-7.0-3.log
• steam-409710-experimental-7.0-20220805.log

[dubigrasu]

@Corben78

...with Proton experimental-7.0-20220805 it starts for me as well, but MangoHud isn't working.

Check if you have the latest Mangohud (0.6.8) needed for the latest DXVK changes

[SeongGino]

Considering I've tried reinstalling twice, let Steam verify the files, and went as far as trying Proton 7.0 and Experimental and -GE, and with no change in behavior at all... I'm not sure why it's this (and BS2HD) that has this problem, and only the Steam versions.

Other games work. It's not a driver thing. Using Arch with the just-updated glibc packages.

For what it's worth, both games work in Steam now. No idea what changed.

[waspennator]

Game apparently got an unneeded third party 2k launcher alongside Bioshock 2 remastered and Infinite that's causing issues now, probably should be bumped down from "playable on deck" to "unsupported" for the time being.

[SeongGino]

The workaround for this is to simply start "BioshockHD.exe" directly, bypassing the launcher.
I've heard of some people simply replacing the 2K launcher with a symlink to the game, which I haven't tried.
What I have done is, at least for the time being, replaced the Steam command with the following run-on:

"/path/to/proton-name-version/proton" waitforexitandrun "/path/to/steamapps/common/BioShock Remastered/Build/Final/BioshockHD.exe" {"-insert" "-optional" "-args" "-here"}; echo %command%
*replace paths as is appropriate on your filesystem. Args aren't needed unless you use any, but the semicolon followed by echo %command% is needed to avoid Steam throwing out the command line string as invalid.

Basically, is just manually pointing a Proton to the game. It works and I have confirmed with others that it's fixed for them... but we shouldn't even need this fix because the launcher itself is wholly unnecessary.

[AJuujarvi]

@waspennator @SeongGino I took a look at this after the recent reports of the 2K launcher update for a few Bioshock games. I am unable to recreate the issue on a Desktop or with a Steam Deck. On the Desktop I am seeing the launcher and can get in game from there, and on the Deck it is skipping the launcher entirely. I have a few things you could try that may fix it for you and would explain why I am not seeing it.

1. Could either of you try verifying the integrity of your game files and see if that causes it to work without the Steam command?
2. Delete your prefix data and then try booting the game again. The prefix is ~/.steam/steam/steamapps/compatdata/409710
3. As a last resort test, uninstalling and reinstalling the game. There is a possibility the 2K launcher update didn't update properly and is having issues that the previous 2 things will not fix.

Please let me know the results, I would appreciate it since I cannot replicate the issue and this appears to be widespread.

[SeongGino]

@AJuujarvi The game files themselves are wholly unrelated since none of it is in any way affected by the contents of the Launcher integration itself. Also wouldn't change anything because the game itself works fine when launching BioshockHD.exe directly, so...

I am also not wasting the bandwidth to reinstall the game due to limited internet access as of late. But again, the game itself works fine, so...

Same for the prefix; nothing about the prefix setup is in any way adjusted to handle the 2K Launcher, so old and new prefixes alike will have the same issue.

The problem here is that the 2K Launcher will install and run fine... the first time run anyways. Any subsequent game bootups will cause the 2KL updater to appear, and then nothing. This is the behavior that's replicated with new prefixes, both in Experimental and GE.

If the game is directly booting up on your Deck, that would indicate either the game itself hasn't been updated at all for whatever reason, or the 2KL is being replaced with a symlink to the game executable at some point; since this is a widespread problem for Windows users as well, it being skipped without workarounds seems highly improbable.

[AJuujarvi]

@SeongGino Can you boot the game after the first boot with the 2K Launcher with the launch command PROTON_LOG=1 %command% please and upload the log file here? You can find your log file in your Home directory. This would help us investigate it as we have not been able to replicate the issue locally, even with multiple boots on multiple machines with fresh installs.

For what it is worth, all of the Bioshock installs I did to test were done within the hour before I had made my comment, so they were for sure updated. It is possible the 2K launcher does not display on some resolutions, as we have seen that happen with 1 launcher in the past, specifically the Rebellion Launcher.

[kisak-valve]

Bioshock Remastered - Steam Deck

Issue transferred from #6269.
@xfechx posted on 2022-10-25T14:18:06:

Bioshock 1 HD version (Remastered) is listed as playable on Steam Deck (Proton 7) while it does not work at all. I have tried Proton 7, 6 and Experimental versions of it.

[xfechx]

I have the issue of Bioshock Remastered not launching at all. I can only see the splashscreen, then a black content window pops up (desktop mode) then crashes right away. I have tried proton expermiental, 7, 6 with no luck. I have also replaced the Launcher exe with the main game exe also no luck. Can someone guide me to make this game work?

I am currently reinstalling it again to test your solution above. @SeongGino can you share your exact custom command args you are entering in steam for this game?

[xfechx]

OK, so I can confirm that adding the BioShock.exe directly onto Steam works.
What is the exact command in Steam Deck for instead of adding the .exe directly, just using the steam shortcut pointing to the BioShock.exe?

I think this will be useful for people that find the game crashing right away. So adding the launch args will help around.

[opyate]

Seeing this - not sure if it's Proton related:

Trying to by-pass the launcher:

STEAM_COMPAT_DATA_PATH=~/.local/share/Steam/steamapps/compatdata STEAM_COMPAT_CLIENT_INSTALL_PATH=~/.local/share/Steam/ ~/.local/share/Steam/steamapps/common/Proton\ -\ Experimental/proton run ~/.local/share/Steam/steamapps/common/BioShock\ Remastered/Build/Final/BioshockHD.exe

But:

(Steam is running, of course.)

((And the publisher suits wonder why folks resort to piracy... bit of negative sentiment all around...))

UPDATE: ok, like @xfechx, I can also confirm that adding the EXE works.

Here's the path (just change your username):

Then find the EXE game in your library (e.g. at the bottom of this list in the screenshot), and add Proton compatibility:

Then, when you run the new EXE game, the original game will show as Running:

Hallelujah.

(Update: encountering lots of long pauses in the game, when pressing V for hacking, when trying to save, when trying to adjust brightness, etc. 2-3 minutes wait at a time. Unplayable, really.)

[xfechx]

I think they have fixed it. I haven't had trouble with it for a while.

…

On Fri, Feb 9, 2024, 11:14 AM Juan M Uys ***@***.***> wrote: Seeing this - not sure if it's Proton related: image.png (view on web) <https://github.com/ValveSoftware/Proton/assets/96808/7d6f3ba9-dbdf-4ae9-a0f4-9828fe276b9c> — Reply to this email directly, view it on GitHub <#399 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACD4JKTIKL6NO2MWWXVB5I3YSXZKHAVCNFSM4FRN2R6KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJTGU3DKNZVGAYQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[daninsky1]

Like I mentioned on the #388, I could't make this work, I run with this flags PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_NO_D3D11=1 %command%
https://gist.github.com/daninsky1/dfc06992b25dafdfa3476a5c97b4be84

If I ran without PROTON_NO_D3D11=1 and I got something siminar to > @kisak-valve https://gist.github.com/XakepSDK/6764b1a3741897e981c4782403163888:

https://gist.github.com/daninsky1/b9c116f61aafdccfc30b85ecbc62ef80

The funny thing is working with heroic launcher(it is the remaster epic games version), and heroic is using the same experimental proton binaries of steam, there is a minor diference how the prefix folder is created, so I tried to import the same files to the compatdata of the game, but didn't work.

I've tried run the TK2 launcher on steam and steam + epic games launcher and didn't work.

[Ninmi]

So, I have an issue trying to bind the key ö. Unlike in the previous Proton versions (starting from 6.*), the latest one seems to be able to bind å and ä and they correctly display as ARING and ADIARESIS respectively in the key binding menu. But while ö should map to ODIARESIS, nothing actually happens. I'm on a Finnish layout, and as these engines always map to the US layout first and foremost, I tried mapping the action to SemiColon in the configuration file. This works, but it mapped to DEAD_ODIARESIS in the key binding menu. I'm guessing ö doesn't work because for some reason it's interpreted as a dead key? Or does the Finnish ö key map to something else?

Anyone know how I could map ö? I used to be able to map the key in old versions of Proton (5.* and earlier), but these Proton versions are no longer able to launch the game so I can't test.