Quoting: ShmerlDid anyone play Bioshock 1 & 2 in Wine+dxvk? How is the experience? They just got released on GOG DRM-free, so I'm quite interested in trying them out.

I currently playing Bioshock Remastered in Proton. After the -nointro and turning off esync, it's been rock solid. 60 fps all the way, haven't even seen any shader/pipeline compiler stutter. Surprising because the reviews of the remaster are not so optimistic. Nvidia though, so can't comment on the AMD experience.

I'm usually not using esync, since it's a pain to keep it up to date with upstream Wine, so that won't be an issue. Is intro somehow broken and what exactly does -nointro skip?

I suppose some video codecs are failing. Did you try installing any native overrides?

Quoting: ShmerlIs intro somehow broken and what exactly does -nointro skip?

Not entirely sure. For me it broke my fullscreen mode. It only skips the brand logos at the start though, so it is actually an improvement.

Ah, I see. So no essential story intros are skipped - that's good! I'll surely use it as well then.

Quoting: ShmerlAh, I see. So no essential story intros are skipped - that's good! I'll surely use it as well then.

I tested them earlier today and they work quite well with DXVK (needs 32bit dll's). In Bioshock 2, the -nointro presumably lets you go past the first "press Space to continue" screen which otherwise blocks keyboard input, [see here.](https://github.com/ValveSoftware/Proton/issues/482#issuecomment-436019150) I recommend to also run the first game with -nointro unless you wanna fall asleep before the main menu appears.

The space to continue bug could be related to previously fixed bug in upstream Wine, so may be Proton picked up an older code. I just bought both games and will give them a try later. I'm surprised they remastered them in 32-bit though. It would be the first game that I know that's using DX11 while being 32-bit.

Quoting: ShmerlIt would be the first game that I know that's using DX11 while being 32-bit.

Because it isn't using DX11, it's actually DX9.

Quoting: ageres

Quoting: ShmerlIt would be the first game that I know that's using DX11 while being 32-bit.

Because it isn't using DX11, it's actually DX9.

The remastered ones are supposed to use DX11 according to system requirements.

According to system requirements, it also needs 64-bit Windows. But it is 32-bit itself. And it runs on DX9. I played it on Windows, and MSI Afterburner showed me it's on DX9. So, BioShock games weren't actually remastered, just few newer textures and 3D models. The laziest remasters ever.

It's easy to test. Check its log when Wine runs.

Quoting: ageresAccording to system requirements, it also needs 64-bit Windows. But it is 32-bit itself. And it runs on DX9. I played it on Windows, and MSI Afterburner showed me it's on DX9. So, BioShock games weren't actually remastered, just few newer textures and 3D models. The laziest remasters ever.

Actually the games both use DX11, here's a screenie of the first game with DXVK:


@shmerl: There's quite a few other 32bit games with DX11 such - Shantae and the Pirate's Curse, Ghost of a Tale, Darksiders 1 Warmastered Edition.

Quoting: Avehicle7887Actually the games both use DX11, here's a screenie of the first game with DXVK:

It probably is DX10 renderer. DXVK supports it, right?

Quoting: ageres

Quoting: Avehicle7887Actually the games both use DX11, here's a screenie of the first game with DXVK:

It probably is DX10 renderer. DXVK supports it, right?

Tested it without the DX10 dll's and DXVK still runs, it's clearly DX11.

Just tried it out. I had to clean up my dxvk builds to produce 32-bit ones as well. Here is Bioshock running with winelib dxvk:





I'll enable vsync for this, no point to run at such huge framerate.

Once thing I noticed is a lot of stutter when entering new areas. Hopefully dxvk pipeline cache will mitigate it over time.

Quoting: ShmerlOnce thing I noticed is a lot of stutter when entering new areas. Hopefully dxvk pipeline cache will mitigate it over time.

I noticed that too, thought it was just my setup.

I guess it somehow creates tons of Vulkan pipelines. That's the first such game I encountered. It's also indicated by the cache file size - it's already 6.3 MB and I'm just in the beginning areas still. In comparison, pipeline cache file for Shadow Warrior 2 (completed the game) is around 7 MB.

I usually add this to my launcher scripts:

export DXVK_STATE_CACHE_PATH=$HOME/.cache/dxvk

So all cache files go in one place.

is their any software similar to Lutris other than PlayonLinux

There was, I don't remember the name though. I stopped using PlayOnLinux and never used Lutris really. I prefer my own installation method lately. May be if I'll have time I'll wrap it up in some minimalist toolset.

But you can use some of my scripts, like these:

* [wine_env.sh](https://gist.github.com/shmerl/a2867c5a675ed1795f03326b32b47fe7)
* [wine_run.sh](https://gist.github.com/shmerl/edf230db5d4a24fd92aea16c31393d89)

Those are launching tools that I constantly use. Place them for example in $HOME/bin

Here is how Bioshock setup is organized for me:

In $HOME:
games/wine/bioshock
games/wine/bioshock/prefix
games/wine/bioshock/start.sh

start.sh can look like this:

#!/bin/bash

hud=${hud:-false}

if $hud; then
   export DXVK_HUD=devinfo,fps,memory
fi

export DXVK_STATE_CACHE_PATH=$HOME/.cache/dxvk
export WINEPREFIX=$HOME/games/wine/bioshock/prefix

export WINEDEBUG=${WINEDEBUG:-"-all"}
export DXVK_LOG_LEVEL=${DXVK_LOG_LEVEL:-"none"}

cd $WINEPREFIX/drive_c/bioshock/Build/Final

wine_run.sh BioshockHD.exe -nointro #&>wine_run.log

Installing the game itself (into $HOME/games/wine/bioshock/prefix) and setting up dxvk for it are separate steps.

For example to install the game, you can do the following (using GOG installer):

WINEARCH=win32 WINEPREFIX=$HOME/games/wine/bioshock/prefix wine_run.sh setup_bioshock_remastered_1.0.122872_(25715).exe

I select something C:/bioshock in the installer (start.sh points to it).

Then, I extract the png icon from the *.ico file provided by GOG (using imagemagic) and create .dekstop launcher for start.sh in $HOME/.local/share/applications for easy access.

UPDATE:

Hm. Code blocks are completely messed up here.