Proton icon indicating copy to clipboard operation
Proton copied to clipboard

Bioshock (7670)

Open Dakunier opened this issue 6 years ago • 32 comments

Short Playtime but it works :)

Edit: Better textures and improved loadtime with PROTON_NO_ESYNC=1 %command%

Systeminfo: https://gist.github.com/Dakunier/352c4f0b1b7c027065f71993367b0249

Dakunier avatar Aug 24 '18 13:08 Dakunier

I'm not so optimistic: the first time I launched the game with SteamPlay, the game crashed and crashed Gnome-Shell too. The second times it launched but the game resolution was not correct (not my desktop resolution), I changed it, applied, but the result was not the one expected. Other thing: you can not choose Directx10 option in the graphic menu. When I choose to use Gamepad in the "control menu", the mouse cursor is no more available. I don't know if it is a normal thing.

legluondunet avatar Aug 24 '18 14:08 legluondunet

@legluondunet i expericend no crashs at all. Resolution is sometimes reseted. DX10 is not available in proton. I tested with a Steam Controller, used the Configuration from Dirty Dan, this worked for me. Overall it is a playable Game with a little remaining work to do.

Dakunier avatar Aug 24 '18 16:08 Dakunier

DX10 is not available in proton.

Normally it should be , Proton has DXVK integration and DXVK support DX10 and DX11.

legluondunet avatar Aug 24 '18 17:08 legluondunet

i see everywhere only DX11... I think this needs further Investigation :D

Dakunier avatar Aug 24 '18 17:08 Dakunier

Assassin Creed is a directX10 game and it works very well with Proton, it could be Whitelisted.

legluondunet avatar Aug 24 '18 17:08 legluondunet

Does anyone have a problem with slow disk access? Like I walk around there are a lot of objects that aren't fully loaded, and the game freezes for 20 seconds or more when trying to save or when trying to access or hack vending machines or medical stations.

moragtong avatar Aug 25 '18 05:08 moragtong

@moragtong As for the the other Bioshock games, use: PROTON_NO_ESYNC=1 %command%

dubigrasu avatar Aug 25 '18 05:08 dubigrasu

@dubigrasu thank you very much it worked!

moragtong avatar Aug 25 '18 07:08 moragtong

I experienced rendering issues with OpenGL 4.5. The first seen was unplayable. Adding MESA_GL_VERSION_OVERRIDE=3.3 %command% to the launch options fixed it.

chrilves avatar Aug 25 '18 23:08 chrilves

Works only with steam-runtime. Has some issues with vertical mouse movements. Sometimes you just can't move mouse down | look down. System info: https://gist.github.com/XakepSDK/fc796a8ac0dd1c21f25b62903deb1af3

XakepSDK avatar Aug 28 '18 08:08 XakepSDK

Won't start even with steam-runtime System info: https://gist.github.com/XakepSDK/db878b1fee107c542da6adcf0bb7f638 Proton: 3.16-5 Beta

XakepSDK avatar Dec 17 '18 21:12 XakepSDK

Hello @XakepSDK, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

kisak-valve avatar Dec 17 '18 22:12 kisak-valve

@kisak-valve https://gist.github.com/XakepSDK/6764b1a3741897e981c4782403163888

XakepSDK avatar Dec 18 '18 15:12 XakepSDK

@XakepSDK have you tried using the "-dx9" launch option?

alasky17 avatar Dec 18 '18 17:12 alasky17

@alasky17 yeah, it works. PROTON_NO_D3D11=1 %command%

XakepSDK avatar Dec 18 '18 17:12 XakepSDK

@kisak-valve I think the regression tag is incorrect here. On old versions of Proton, Bioshock was failing to run on dx10 and getting automatically bumped back to dx9. The failure was partially fixed, so Bioshock no longer automatically forces dx9, but still fails to actually run with dx10. Users now have to force Bioshock back to dx9 manually, but the behavior hasn't actually regressed per se.

alasky17 avatar Dec 20 '18 14:12 alasky17

Compatibility Report

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

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

Symptoms

Videos and game intro cinematics have no audio.

In DX10 mode, you must disable ESync and FSync by using "PROTON_NO_ESYNC=1" and "PROTON_NO_FSYNC=1" in launch options to fix the low resolution texture glitch.

ESYNC FSYNC DX10 LOG: steam-7670yes10.log

NO ESYNC FSYNC DX10 LOG: steam-7670no10.log

When enabling DX9 mode by using the "-dx9" launch option, the game will crash at the loading screen, whether or not "PROTON_NO_ESYNC" and "PROTON_NO_FSYNC" is 0 or 1.

ESYNC FSYNC DX9 LOG: steam-7670yes9.log

NO ESYNC FSYNC DX9 LOG: steam-7670no9.log

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

shoober420 avatar Apr 20 '20 01:04 shoober420

Also, I get the infamous black squares bug at the vending machine in "Neptune's Bounty" in front of "Fontaine Fisheries" using DX10. This is apparently a bug with NVIDIA cards, and happens on Windows as well, so I guess its ok. This bug does not occur using DX9 mode.

https://www.youtube.com/watch?v=ZxajUUErvy4

shoober420 avatar Apr 21 '20 19:04 shoober420

Compatibility Report

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

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-7670.log

Symptoms

Intro and game cinematics now have audio, and the game has no sound.

I recently upgraded my computers sound card from a ASUS Xonar Essence STX to an external Topping D50s DAC. I reinstalled Bioshock and Proton to make sure it wasn't a software issue, and the same behavior persists. Oddly enough, Bioshock Remastered game sound still works with broken sound in cinematics like Bioshock 2007 used to behave.

shoober420 avatar Apr 25 '20 19:04 shoober420

The brightness slider is not working by default (dx10 mode), but works with dx9. The problem happens with DXVK and WINED3D. Some pictures below:

7670_20200613164234_1

7670_20200613164247_1

The problem happens on the remastered version as well.

My specs:

  • GPU: GTX 970 4GB
  • S.O: Manjaro Linux 20
  • Driver: Nvidia 440.82
  • Kernel: 5.4.43
  • Proton version: 5.0-9
  • Logs: steam-7670.tar.gz

vinifmor avatar Jun 13 '20 19:06 vinifmor

Unplayable for some reason (on NVidia at least) with 6.3-4, playable with a current Proton Experimental.

thaewrapt avatar May 20 '21 23:05 thaewrapt

Compatibility Report

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

System Information

  • GPU: Radeon RX 5500 XT
  • Driver/LLVM version: Mesa 21.2.0-devel (git-d677120cae) / LLVM 13 git master
  • Kernel version: 5.13.0-pf2+
  • https://gist.github.com/shoober420/35af31e8e121a2a55a1004a37597ca60
  • Proton version: 6.12-GE-1 / Proton Experimental
  • Log GE: steam-7670.log
  • Log Experimental: steamexperimental-7670.log

Symptoms

The brightness slider in DX10 mode is still not working, and the default brightness is too bright and washed out.

20210710_11h17m43s_grim

shoober420 avatar Jul 10 '21 20:07 shoober420

Just crashes with experimental

rtentser avatar Sep 05 '22 05:09 rtentser

Please include your system information (Steam -> Help -> System Information) which you can post as a github gist,
And attach a proton log by launching the game with PROTON_LOG=1 %command% in it's launch options. It should appear in your users home folder.

Blisto91 avatar Sep 05 '22 06:09 Blisto91

System information: https://gist.github.com/rtentser/a28d3cfe60f8f75ad51122b33a0e2539

Log: steam-7670.log

rtentser avatar Sep 05 '22 06:09 rtentser

According to protondb last working proton is 5.13

rtentser avatar Sep 05 '22 07:09 rtentser

The brightness slider in DX10 mode is still not working, and the default brightness is too bright and washed out.

I had the same problem with remaster on windows

rtentser avatar Sep 05 '22 10:09 rtentser

I've retested. Looks like the problem was in directx. If installed when offered, the game starts fine. The issue with gamma can be fixed by using PROTON_NO_D3D10 (it's the game bug which exist on windows too with dx10), but this way the game will crash when starting a new game / loading the save. I'll provide a new log tomorrow

rtentser avatar Sep 09 '22 21:09 rtentser

I've retested again Clean prefix, proton experimental, PROTON_NO_D3D10 to fix gamma, no esync and no fsync to fix textures. I refused to install additional software steam offered, new game started successfully, i also can change game resolution without restarting the game.

rtentser avatar Sep 10 '22 05:09 rtentser

Compatibility Report

  • Name of the game with compatibility issues: BioShock
  • Steam AppID of the game: 7670

System Information

  • Steam Deck: Steam OS Stable Channel v3.4.4
  • Driver/LLVM version: 4.6, Mesa 22.2.0 (git-17e5312102)
  • Kernel version: 5.13.0-valve36-1-neptune
  • Link to full system information report as Gist
  • Proton version: ??? / Default Proton

I confirm:

  • [X] that I haven't found an existing compatibility report for this game.
  • [X] that I have checked whether there are updates for my system available.

Symptoms

Bioshock when installed on a Micro SD card doesn't create the necessary folder structure to save your game. Manually creating the folder structure inside Proton compatdata/pfx fixes the issue.

Correct path: %USERPROFILE%\Documents\Bioshock\SaveGames\

Reproduction

Launch game. Try to save.

CookieDoodle avatar Mar 01 '23 16:03 CookieDoodle