Proton: Bioshock 2 Remastered (409720)
The menu loads and I'm about to click continue (and change key-bindings), but when the loading screen asks me to click the space bar, nothing happens.
Bioshock 1 Remastered works fine after adding the esync parameter.
d10sfan
All 41 comments
Can you attach a controller and see if that works?
dubigrasu
on 25 Aug 2018
I've been having the same problem. Bioshock doesn't register any of my controller input (tested it on other games and it works)
DarkZek
on 25 Aug 2018
@DarkZek
My controllers are recognized though, I tested a Steam Controller and a Xbox360 one. The Xbox360 has also the rumble working.
dubigrasu
on 25 Aug 2018
Same here - controller and keyboard/mouse input work fine in the menu, but once a game is started it does not register any input anymore (i'm stuck at "press space to continue" as well)
pprotonrep
on 25 Aug 2018
BioShock 2 Remastered displays black screen during first start (409720)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/504.
@pprotonrep posted on 2018-08-25T09:16:37:
I could not even Alt+Tab out of it, and had to kill it changing to a terminal via Ctrl+Alt+F Key.
Changing the configuration file steamapps/compatdata/409720/pfx/drive_c/users/steamuser/Application Data/BioshockHD/Bioshock2/Bioshock2SP.ini wouldn't work at all (the settings would be reset as soon as the game starts). I had to start the game within a virtual desktop鹿 and then change the settings from the game's UI. After that i experienced https://github.com/ValveSoftware/Proton/issues/482.
- Ubuntu 18.04.1 LTS (64 bit 4.15.0-33-generic)
- GeForce GTX 1070/PCIe/SSE2 (396.54)
- tested with Proton 3.7-3 and 3.7-4 Beta
鹿 via
WINEPREFIX=/media/pedro/SteamWin/Steam/steamapps/compatdata/409720/pfx winecfg
as suggested here.
kisak-valve
on 25 Aug 2018
The game is always blocked here and then it does not continue:
https://i.imgur.com/kCbLKHP.jpg
Reborn OS (Arch Linux)
Proton 3.7-3
Nvidia Geforce GTX 950
396.54-1
CPU AMD FX
https://gist.github.com/Xeers/219b4b3e5eb10c6ec225d7cc8c61be44
Pastebin:
https://paste.drhack.net/?0d65bf433873550d#2oC0uqH14uKzxlpaSiam56Zd7ZzDiGD4q6opEakDT0M=
Xeers
on 31 Aug 2018
With Steam Play (Proton 3.7-5-Beta) the gamepad buttons appear, it does not freeze and I can start the game correctly.
Xeers
on 31 Aug 2018
For me on 3.7-6, the space bar is not working.
d10sfan
on 9 Sep 2018
True, with Proton 3.7.6_Beta the game does not detect and can not be played with the Steam Controller. In the spacebar image the game freezes.
Xeers
on 9 Sep 2018
@Xeers
Make sure you're using the launch option:
PROTON_NO_ESYNC=1 %command%
I'm playing the game with the Steam Controller and it works perfectly.
dubigrasu
on 9 Sep 2018
Without the command PROTON_NO_ESYNC = 1% command% I can not select the Steam Comtroller gamepad. The game is blocked at the beginning where it says press the space bar.
Image:
https://i.imgur.com/sEYKCCV.png
With PROTON_NO_ESYNC = 1% command% I can use the gamepad and the game works perfectly (Small defects: it takes a few seconds to start some puzzles, it does not allow to adjust the brightness, faults in textures in paintings and posters)
Xeers
on 9 Sep 2018
@Xeers
Interesting, I never noticed any kind of issues (I never tried to adjust the brightness though).
"faults in textures and paintings" can you give some details about this?
dubigrasu
on 9 Sep 2018
The paintings, the posters, the drawings of the weapons sale machines ... appear blurred, pixelated at low resolution.
Xeers
on 9 Sep 2018
I tested using PROTON_NO_ESYNC=1 %command% and game controller (Xbox One S over bluetooth). Without controller, I am stuck at "Press space to continue" screen. With controller, I can go past this screen (by pressing A), and then turn controller off in Options and continue playing using keyboard and mouse. Performance seems great (comparable, maybe even better than on Windows? I am not sure).
[edit] Seems like problem with "Press space to continue" happens on Windows as well: 1, 2 (or at least happened at some point).
As long as I don't have browser opened in the background, I seem to have ridiculously high FPS (150-200 FPS on GTX 770, when I had ~80 when I played original Bioshock 2 on Windows) - not complaining :D
dreamer
on 18 Sep 2018
I've got proton_no_esync 1 and the game shows the logo, gives me a black box, and then crashes.
unfortunately can't even get to "space to continue"
Kommynct
on 30 Oct 2018
@Kommynct System info? Which proton version are you testing? Logs? We can't help if we don't know what the problem is.
dreamer
on 30 Oct 2018
I played some more trying to turn on/off different workarounds (using 3.16-4) and the game works best with following settings: PROTON_NO_ESYNC=1 %command% -nointro
PROTON_NO_ESYNC=1prevents bug with low-resultion textures-nointrodisables developers' logos from showing up (real intro when game starts is still there), but what is more important - it prevents "space to continue" bug. Game starts as soon as it's loaded, no workaround with controller required.
dreamer
on 5 Nov 2018
PROTON_NO_ESYNC=1 %command% -nointro
Nice! Works for me too.
supertin
on 21 Nov 2018
PROTON_NO_ESYNC=1 %command% -nointro
OK
Xeers
on 21 Nov 2018
I'm seeing the same crash as Kommynct on my machine (logo, then black box, then crash). Here's my sysinfo and log.
My command string is PROTON_NO_ESYNC=1 PROTON_USE_WINED3D11=1 %command%, I added PROTON_USE_WINED3D11 as I needed that to get Bioshock 1 Remastered working, and I don't get the black box for a second without it.
jgkamat
on 1 Jan 2019
Hello @jgkamat, err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3 and err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3 in your log hint that there might be an issue with your vulkan video driver. Please verify you have the mesa-vulkan-drivers and mesa-vulkan-drivers:i386 packages installed and that any vulkan application like vulkaninfo from vulkan-tools works.
kisak-valve
on 1 Jan 2019
Actually, mine was fixed by installing 32-bit vulkan Radeon. So I'm just dumb for not having that installed anywho. Forgot to report back with logs, my bad.
Kommynct
on 1 Jan 2019
I tried the GOG version of this game via Codeweavers Crossover 18 and the "press space to continue" bug is present too...
And I tried the game on a Windows 7 machine and the bug is not present there...the game works fine. That means that the "press space to continue" not responding bug is a wine issue.
CSahajdacny
on 10 Jan 2019
-nointro in launch options get's the game past the "press space to continue" bug for me, I haven't needed anything else to get the game running.
lucifertdark
on 10 Jan 2019
@lucifertdark , I know, but that is not a bug fix...
I confirmed that the "press space to continue" is a proton /wine issue that must be solved by Proton devs.
On Windows, the minimum system requirements are Win7 SP1 with Platform update KB2670838 -
I wonder if Proton/wine is equivalent to that.
CSahajdacny
on 10 Jan 2019
The "Press space to continue" bug still present in PROTON 3.16-7....
CSahajdacny
on 19 Feb 2019
The "Press space to continue" bug still present in PROTON 4.2-1
Here is the game log:
CSahajdacny
on 27 Mar 2019
Is that possible that dinput8.dll is the guilty of the "Press space to continue" bug?
CSahajdacny
on 29 Mar 2019
The "Press space to continue" bug still present in PROTON 4.2-3
CSahajdacny
on 21 Apr 2019
Adding PROTON_NO_ESYNC=1 %command% -nointro -allowconsole works well for me using NVIDIA proprietary drivers on Pop!_OS. I have it running at home with the same commands using amdgpu on Manjaro.
njakes
on 8 May 2019
The "Press space to continue" bug still present in PROTON 4.2-4
steam-409720.log
CSahajdacny
on 15 May 2019
The "Press space to continue" bug is still present in PROTON 4.11-1
steam-409720.log
CSahajdacny
on 31 Jul 2019
The "Press space to continue" bug is still present in PROTON 4.11-3
steam-409720.log
CSahajdacny
on 30 Aug 2019
The "Press space to continue" bug is still present in PROTON 4.11-7
steam-409720.log
CSahajdacny
on 4 Nov 2019
The "Press space to continue" bug is still present in PROTON 4.11-12
steam-409720.log
CSahajdacny
on 5 Feb 2020
The "Press space to continue" bug is still present in PROTON 5.0-1
steam-409720.log
CSahajdacny
on 8 Feb 2020
Brightness adjust does not stay at desired level while in game. Brightness will change while playing without going into any menus or alt-tabbing.
kalamalka
on 29 Mar 2020
The "Press space to continue" bug is still present in PROTON 5.0-7
CSahajdacny
on 10 May 2020
The "Press space to continue" bug is still present in Proton 5.0-8 RC2
steam-409720.log
CSahajdacny
on 6 Jun 2020
-nointro in launch options get's the game past the "press space to continue" bug for me, I haven't needed anything else to get the game running.
this solved my problem in archlinux. thanks
dfso
on 11 Jul 2020
I tried PROTON_NO_ESYNC=1 PROTON_USE_WINED3D11=1 %command% -nointro, PROTON_NO_ESYNC=1 %command% -nointro and %command% -nointro and only the second works acceptable for Bioshock 2 Remastered. However, I get a lot of stutters in the game. My CPU is only using ~4% and I have plenty of Memory available.
Archlinux, Proton 5.0-9, Radeon RX5700XT, Threadripper 3970X
jhamfler
on 25 Aug 2020
Related issues
shanefagan
路
3Comments
Dakunier
路
3Comments
AwesamLinux
路
3Comments
raikirii
路
3Comments
BLaDZer
路
3Comments
Most helpful comment
I played some more trying to turn on/off different workarounds (using 3.16-4) and the game works best with following settings:
PROTON_NO_ESYNC=1 %command% -nointroPROTON_NO_ESYNC=1prevents bug with low-resultion textures-nointrodisables developers' logos from showing up (real intro when game starts is still there), but what is more important - it prevents "space to continue" bug. Game starts as soon as it's loaded, no workaround with controller required.