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%

[darkpumpkins]

steam-409710.log config.txt The game crash at start up for me. I tried differents options without any success.

[kisak-valve]

Hello @darkpumpkins, looks like the wine prefix didn't get setup properly. What filesystem is being used for /media/lchauvin/Data2/SteamLibrary?

[darkpumpkins]

Hello @darkpumpkins, looks like the wine prefix didn't get setup properly. What filesystem is being used for /media/lchauvin/Data2/SteamLibrary?

It's a NTFS filesystem.

[kisak-valve]

NTFS is known be finicky with Proton and there are various issue reports open regarding Steam libraries on it. Please make sure the drive is not mounted with the windows_names mount option (from https://github.com/ValveSoftware/Proton/issues/11#issuecomment-414915525).

[darkpumpkins]

Ok, It was related to NTFS filesystem, i don't know if there was the "windows_names" flag, I haven't been able to make a proper mount of NTFS partition and own the file in to use it with stream using /etc/fstab. I switched the game to a ext4 partition and now it works fine.

Thanks !

[mozo78]

You just have to mount it properly. /dev/sdbX /media/sdbX ntfs-3g defaults,auto,uid=1000,gid=1000,umask=002 0 0

All my games are on NTFS drive and all of them are working perfect. https://www.youtube.com/channel/UCm21eK86ZmD0FQoNPGqvKlw/videos?view=0&sort=dd&shelf_id=0

[darkpumpkins]

You just have to mount it properly. /dev/sdbX /media/sdbX ntfs-3g defaults,auto,uid=1000,gid=1000,umask=002 0 0

All my games are on NTFS drive and all of them are working perfect. https://www.youtube.com/channel/UCm21eK86ZmD0FQoNPGqvKlw/videos?view=0&sort=dd&shelf_id=0

Thanks a lot !

[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://gist.github.com/shoober420/1215c40214cf70e1fabb760b5bd2a341
• 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.

https://github.com/doitsujin/dxvk/issues/1581

[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.7-zen
• https://gist.github.com/shoober420/1215c40214cf70e1fabb760b5bd2a341
• Proton version: 5.6-GE-2
• Log: steam-409710.log

I've also noticed that decals will remain red or green when in areas with security cameras. The dynamic light rendered by the security cameras will bug out decals and make them green or red. This happends using both DXVK and WINED3D.

[Corben78]

Cross posting from https://github.com/ValveSoftware/Proton/issues/215#issuecomment-742403711 as that issue is closed:

If core dumps are enabled, and the game crashed once, just the mere existence of the core file in <SteamLibrary>/steamapps/common/BioShock Remastered/Build/Final causes the game to segfault. This is now also mentioned on the corresponding PCGamingWiki article.

[zelfir]

Compatibility Report

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

System Information

GPU: RTX 2070 Super
Driver/LLVM version: NVIDIA 470.63.01
Kernel version: 5.13.14-200.fc34.x86_64
Proton version: 1631125536 experimental-6.3-20210908

The game actually crashes after its loading screen. It managed to load one time, but now loading its save makes it crash all time.

steam-409710.log screen

[Simmonz]

I am having a couple issues. When I press the button to hack anything it takes usually between 30 second to 2 minutes to bring up the menu to begin the hack. The game looks like it is frozen but if I leave it will finally do it's job in the end. Saving and loading can also take upwards of 1 minute. I have tried using XFCE instead of Mate and the issue remained. I also tried Proton GE instead of 6.3-7 but it also still remained. I did a fresh install of Manjaro using EXT4 instead of BTRFS for the file system but the issue remains. I also tried the 5.10.70 kernel instead of the 5.14.10 kernel but the issue still happens. I added PROTON_LOG=1 %command% to the game's launch and got the following log:

steam-409710.log

I have checked whether there are updates for my system available and I am up to date

System Information:

Distro: Manjaro

GPU: RX 580 8GB

Driver/LLVM version: Mesa 21.2.3/12.0.1

Kernel version: 5.14.10-1-MANJARO

Proton version: 6.3-7

https://gist.github.com/Simmonz/2ba8ec43599e31a19c700bb1983efd39

[kisak-valve]

Hello @Simmonz, that sounds like an esync-related issue. (https://github.com/ValveSoftware/Proton/issues/388#issuecomment-415940766 https://github.com/ValveSoftware/Proton/issues/388#issuecomment-415941616)