PP
Published
DXVK_ASYNC=1 bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/Build\/Final\/BioshockHD.exe}"' -- %command% -nointr
Needs the "DXVK_ASYNC=1 bash -c 'exec "${@/2KLauncher/LauncherPatcher.exe/Build/Final/BioshockHD.exe}"' -- %command% -nointr" to start.
I had to install vcrun2017 manually from the winetricks GUI, the -q option did not lead to a successful installation for me. Also, had to run the game once (crashed) to create the prefix folder. No need to rename the movies folder. WINEPREFIX="$HOME/.local/share/Steam/steamapps/compatdata/570940/pfx" winetricks select the default wineprefix option, then select the vcrun2017 and accept the license. Steam controller works, if activated before starting the game.
The font issue is distracting, but the game is playable. Exiting the game does not work normally.
The user interface font (menus, buttons) is replaced by a too large, pixelated font. Other fonts are ok.
Exiting the game did not work, had to task switch to Steam and stop it from there.
Tested with Proton 6.3.7 - first time the game even starts for me.
Getting protontricks to run (correct version etc) was possible, but awkward -- too much trouble for a typical gamer
As suggested by BalzA, with those changes to gdiplus and corefonts, the game fonts are the correct size. Game performance is good, exiting sometimes works without need of alt-tabbing to steam to kill it.
Requires protontricks for gdiplus and corefonts
Other than the front end process (?) causing trouble at starting, and the requirement on desktop to modify steam input for controller.
Apparently, to no greater degree than on windows -> bug for bug compatibility!
The game tends to require several start attempts before it starts. After initial installation, both on desktop and SteamDeck, first attempt failed silently, second led to a freeze at a white screen, third worked. After that, it has a < ~50% chance of starting. Once it starts, it works well -- to same degree than on windows apparently, but no stuttering.
Did not invade anyone, did not ask for co-operation, was not invaded. The messages, blood stains etc. passive multiplayer features worked.
Requires the desktop steam input to have controller, as mentioned in many reports.
Controller not recognized on initial launch, worked on the next attempt
Using https://git.sr.ht/~_dev_fra/hwrc-proton-launcher First run without it. Then edit the paths in the hwrc-proton-launcher. Launch homeworld classic 1 in windowed mode using the script. Set largest available display size in the game. Exit game, relaunch in full screen mode. Seems to work - played up to training mission 7. Sounds work. Exiting the game works. 3D movement (z axis) with the mouse feels slightly off or unresponsive.
Sudden color transition from dark to light blue in night sky in Hirata Estate
A black box appears for a second, then the game exits
Tinker winetricks d3d9 for the prefix fails, complains about 64 bit wine prefix
Works better than the native version:
- no bugs which are present in native
- multiplayer works
- mods work
Works perfectly, on launch day, with Proton 7.0
For some reason protondb does not see this in my steam library, even after multiple refreshes, and having verified I have a public profile.
