WineHQ

Bioshock

August 21, 2007 initial release version.

Application Details:

Version: 1.0
License: Retail
URL: http://www.2kgames.com/bioshoc...
Votes: 55
Latest Rating: Gold
Latest Wine Version Tested: 2.13-staging

Maintainers: About Maintainership

Test Results

Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results

What works

Tested in a 32-bit WINEPREFIX, Windows 7 compatibility, Wine Virtual Desktop @1920x1080p.

  • DVD Installer - using setup.exe
  • Online DVD key activation
  • Launch the game
  • Intro and in-game videos
  • Sound
  • CSMT (Wine Staging)
  • Reasonable FPS @1920x1080p
  • Switching resolution in-game appears to work OK now!
  • Command line switches: -nointro -defaultres


What does not

  • DirectX 10 features are problematic still: water droplets are square ; game hangs when set to DirectX 10 mode (dxgi.dll override still required)
  • Mouse warping - in a Virtual Desktop - still requires the Registry hack to avoid the mouse escaping the Virtual Desktop region


Workarounds

[HKEY_CURRENT_USER\Software\Wine\DirectInput]
MouseWarpOverride="force"

[HKEY_CURRENT_USER\Software\Wine\DllOverrides]
dxgi=""


What was not tested

  • Extended gameplay

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

Some issues like the occasional crash after exiting the game (hardly critical). DLL overrides still required. The failure to start in DX10 mode. The (now) working in-game resolution switching raises the game above a Silver rating! System Software =============== uname -r 4.12.3-gentoo emerge -pv1 sys-devel/gcc kde-plasma/plasma-desktop media-libs/mesa x11-base/xorg-server x11-drivers/nvidia-drivers =app-emulation/wine-staging-2.13 [ebuild R ~] sys-devel/gcc-6.3.0:6.3.0::gentoo USE="cxx doc fortran go mpx (multilib) nls nptl openmp pch sanitize ssp vtv (-altivec) (-awt) -cilk -debug (-fixed-point) (-gcj) -graphite (-hardened) (-jit) (-libssp) -objc -objc++ -objc-gc (-pie) -regression-test -vanilla" 97,570 KiB [ebuild R ~] kde-plasma/plasma-desktop-5.10.4:5::gentoo USE="debug fontconfig gtk2 handbook legacy-systray pulseaudio semantic-desktop -appstream -gtk3 -ibus -qt4 -scim {-test}" INPUT_DEVICES="evdev synaptics" 5,944 KiB [ebuild R #] media-libs/mesa-17.1.5::bobwya USE="classic egl gbm nptl osmesa wayland xvmc -bindist -d3d9 -debug -dri3 -gallium -gles1 -gles2 -llvm -opencl -openmax -pax_kernel -pic (-selinux) -unwind -vaapi -valgrind -vdpau -vulkan -xa" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="(-freedreno) -i915 -i965 -imx -intel -nouveau -r100 -r200 -r300 -r600 -radeon -radeonsi (-vc4) (-vivante) -vmware" 0 KiB [ebuild R #] x11-base/xorg-server-1.19.3-r1:0/1.19.3::bobwya USE="ipv6 kdrive suid systemd udev xephyr xorg -debug -dmx -doc -fop -glamor -libressl -minimal (-selinux) -static-libs -tslib -unwind -wayland -xcsecurity -xnest -xvfb" 5,909 KiB [ebuild R #] x11-drivers/nvidia-drivers-384.59:0/384::bobwya USE="X acpi driver kms multilib tools uvm -compat -gtk3 -pax_kernel -static-libs -wayland" ABI_X86="32 (64) (-x32)" 0 KiB [ebuild R #] app-emulation/wine-staging-2.13:2.13::bobwya USE="X alsa cups dos fontconfig gecko gphoto2 gsm gstreamer jpeg lcms ldap mono mp3 ncurses netapi nls openal opencl opengl osmesa pipelight png pulseaudio realtime run-exes s3tc samba scanner ssl threads truetype udev udisks vulkan xcomposite xinerama xml -capi -cuda -custom-cflags -odbc -oss -pcap -perl -prelink (-selinux) {-test} -themes -v4l -vaapi" ABI_X86="32 64 (-x32)" LINGUAS="en en_US -ar -bg -ca -cs -da -de -el -eo -es -fa -fi -fr -he -hi -hr -hu -it -ja -ko -lt -ml -nb_NO -nl -or -pa -pl -pt_BR -pt_PT -rm -ro -ru -sk -sl -sr_RS@cyrillic -sr_RS@latin -sv -te -th -tr -uk -wa -zh_CN -zh_TW" 0 KiB H/W path Device Class Description ========================================================= system G751JT (ASUS-NotebookSKU) /0 bus G751JT /0/0 memory 64KiB BIOS /0/8 processor Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz /0/8/9 memory 1MiB L2 cache /0/8/a memory 256KiB L1 cache /0/8/b memory 6MiB L3 cache /0/c memory 32GiB System Memory /0/c/0 memory 8GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/c/1 memory 8GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/c/2 memory 8GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/c/3 memory 8GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/100 bridge Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller /0/100/1 bridge Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller /0/100/1/0 display GM204M [GeForce GTX 970M] /0/100/1/0.1 multimedia GM204 High Definition Audio Controller /0/100/14 bus 8 Series/C220 Series Chipset Family USB xHCI /0/100/14/0 usb1 bus xHCI Host Controller /0/100/14/0/3 bus USB 2.0 Hub /0/100/14/0/3/2 bus USB2.0 Hub /0/100/14/0/3/2/1 input USB Receiver /0/100/14/0/3/2/3 input Corsair K65 Gaming Keyboard /0/100/14/0/4 multimedia Corsair Gaming H2100 Headset /0/100/14/0/5 communication Bluetooth wireless interface /0/100/14/0/7 multimedia USB2.0 HD UVC WebCam /0/100/14/0/a input ASUS ROG Macrokey /0/100/14/1 usb2 bus xHCI Host Controller /0/100/16 communication 8 Series/C220 Series Chipset Family MEI Controller #1 /0/100/1b multimedia 8 Series/C220 Series Chipset High Definition Audio Controller /0/100/1c bridge 8 Series/C220 Series Chipset Family PCI Express Root Port #1 /0/100/1c.2 bridge 8 Series/C220 Series Chipset Family PCI Express Root Port #3 /0/100/1c.2/0 wls1 network Wireless 7260 /0/100/1c.3 bridge 8 Series/C220 Series Chipset Family PCI Express Root Port #4 /0/100/1c.3/0 p3p1 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller /0/100/1f bridge HM87 Express LPC Controller /0/100/1f.2 storage 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] /0/100/1f.3 bus 8 Series/C220 Series Chipset Family SMBus Controller /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 2048GB Samsung SSD 850 /0/2 scsi2 storage /0/2/0.0.0 /dev/cdrom disk BD-CMB UJ172 S /0/2/0.0.0/0 /dev/cdrom disk /0/3 scsi3 storage /0/3/0.0.0 /dev/sdb disk 1024GB Samsung SSD 850

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
CurrentGentoo Linux x86_64Jul 31 20172.13-stagingYes Yes YesGoldRob 
ShowArch Linux x86_64Oct 24 20131.7.4Yes Yes NoBronzeMario Oelze 
ShowFedora 16 x86_64Mar 03 20121.4-rc6Yes Yes NoGoldJohn P Sims 
ShowUbuntu 10.04 "Lucid" amd64 (+ variants like Kubuntu)Dec 24 20111.3.35Yes Yes NoPlatinuman anonymous user 
ShowopenSUSE 11.4Aug 20 20111.3.26Yes Yes NoGoldPhilipp Lorenz 

Known Bugs

Bug # Description Status Resolution Other apps affected
7991 Test Drive: Unlimited messed up graphics REOPENED View
34362 Bioshock takes way way way too long to load UNCONFIRMED View

Show all bugs

HowTo / Notes

Test Submissions ... how to avoid a rejection notice!!

These notes were last updated: 14 May 2018

Follow these guidelines to avoid embarrassment when your Test Submission is immediately rejected!!

  • Put your PC specifications in the Extra Comments section e.g. like your CPU and system memory.1
  • When adding test results please specify video card and driver version you are using.2
  • It's also useful to mention what desktop environment you are using (e.g. KDE, Gnome, Xfce, Unity...)
  • Specify what version of the Windows compatibility option you use in your Wineprefix (e.g. Windows XP, Windows 7, etc.).
  • Add a comment about what is not working for you.
  • Specify if you made any other changes to Bioshock e.g. installing a game "Mod", an .exe patch or details of any other modifications you made to the stock configuration files for the game.
  • Please indicate if your using Wine Staging and/or any additional patches applied - to the version of Wine you are using.
  • Please, don't submit test results like "Everything is working" or "Everything isn't working".

These guidelines ensure your submitted test results are actually relevant to other users of Wine and WineHQ.


1 The console version of the lshw utility is your friend. This command will dump your System hardware specification in a clean format. Post command and output in the Extra Comments section:

sudo lshw -short | egrep -v '(volume|disk|bus)'

2 inxi can be used to display information about your graphics card, and your OpenGL/ graphics driver versions. Post the command and output in the Extra Comments section:

inxi -G -c0

Troubleshooting





Bioshock red fog during game play. 

Note: this only seems to be a problem with older nVidia Geforce 7000 series cards.

Fixing this issue will involve changing 2 files in the Bioshock binaries folder with modified versions. Download the following 2 files:

Extract the files and copy the 2 files you extracted from the downloads into the directory:

"${WINEPREFIX}/drive_c/Program Files/Steam/steamapps/common/bioshock/builds/release"

... overwriting the files that are already there. Then retest.




Sound isn't working.

This issue could be related to the OpenAL library, you can fix this problem by setting the library openal32 to native (using winecfg).



General Troubleshooting.

  • Verify if your native video driver is installed properly (the 64-bit version of Wine will require the 32-bit libraries of your video driver to be installed - alongside the 64-bit version).
  • Install the Steam client and BioShock, to a separate/clean Wineprefix.
  • Set your Bioshock Wineprefix Windows version to Windows XP (using winecfg).
  • Close BioShock and Steam client, and reboot Wine by typing wineserver -k.
  • Check the integrity of the game through Steam client window, you can do that by right clicking on Bioshock (in your games list) and selecting Properties.
  • To rebuild the prefix you can reinstall Steam to a clean Wineprefix then copy over the directory:

    "${WINEPREFIX}/drive_c/Program Files/Steam/steamapps"

    ... i.e. your full Steam library that will include all the installed Bioshock files (from the existing/ old Wineprefix).
Installation Guide (Retail DVD)
  1. Install Wine
  2. Configure Wine
  3. Setup your environment variables:
    export WINEPREFIX=" ❚❚❚❚❚❚ "
    WINEARCH=win32 wineboot -u
    winetricks sandbox
  4. Check your DVD-ROM drive is mounted and mapped using:
    winecfg
  5. Launch the setup:
    wine "D:\setup.exe"
    (Replace D: with whatever drive letter you have your DVD mapped to in winecfg)
    Uncheck: ☐ install Nvidia Drivers

The default installation folder is:

C:\Program Files\2K Games\BioShock
Known Issues

Mouse axes confined to 360° zones

There is still a bug present with Wine that causes you mouse to lock in a fixed 360° arc whilst playing Bioshock. This issue always manifests when you play Bioshock in a Wine Virtual Desktop arrangement. It will manifest occasionally when playing Bioshock in standard Wine arrangement (i.e. non-Virtual Desktop). The symptom is that you are unable to spin you character round on the spot (it will become locked at a fixed angle) or be unable to view your characters feet.

The only work around for  this issue is to enable the mouse warping override:

wine reg.exe ADD "HKEY_CURRENT_USER\Software\Wine\DirectInput" "/v" "MouseWarpOverride" "/t" "REG_SZ" "/d" "force"


DirectX 10.x Support

As of Wine version 1.7.53(+) there are tests enabled to see if your graphics hardware supports DirectX 10.x... Unfortunately a significant amount of the DirectX 10.x support has still to be implemented in Wine. The symptom for this issue is that Wine will crash immediately after you launch Bioshock.

The workaround is to disable support for the DirectX Graphics Infrastructure (DXGI) in Wine:

wine reg.exe ADD "HKEY_CURRENT_USER\Software\Wine\DllOverrides" "/v" "dxgi" "/t" "REG_SZ" "/d" ""


Changing Game Resolution

In game changing screen resolution can be a bit erratic. The symptom of this is that you change the screen resolution in the game menus and you end up with a "windowed version" of the game running (i.e. smaller than your full monitor real estate). This problem especially manifests when using Linux proprietary graphics drivers.

Option 1 : set game resolution manually before launching

To set the default Bioshock game resolution manually, from a terminal... Run this terminal command (changing first: Xres & Yres - as required):

export Xres=1920
export Yres=1080
sed -i -e '/^\(Fullscreen\|Menu\|Windowed\)Viewport\(X\|Y\)=/{s/X=.*$/X='"${Xres}"'/;s/Y=.*$/Y='"${Yres}"'/}' \
"$( find "${WINEPREFIX:-${HOME}/.wine}/drive_c" -type f -iname "Default.ini" )"

NB: this command won't work if you're using a separate Steam Library directory (external to your WINEPREFIX) to install Bioshock to!


Option 2 : set game resolution in-game

A rather hacky in-game workaround for this issue is to switch Bioshock to windowed mode and then back to full screen mode:

  • mouse Select Windowed Mode ON and your desired Resolution...

Graphics Options
 Resolution:   1920x1080
―――――――――――
 Windowed Mode ON OFF
 ...

  • mouse Then set Windowed Mode OFF...
Graphics Options
 Resolution:  1920x1080
―――――――――――
 Windowed Mode ON OFF
 ...


Audio Garbled or No Audio when using PulseAudio

If you find that your in game audio is garbled or non-existent it may be advisable to try Wine with pulseaudio support. Any supported version of Wine will provide the necessary audio driver support - if the pulseaudio flag was enabled at build time.

Troubleshooting

Bioshock red fog during game play. 

Note: this only seems to be a problem with older nVidia Geforce 7000 series cards.

Fixing this issue will involve changing 2 files in the Bioshock binaries folder with modified versions. Download the following 2 files:

Extract the files and copy the 2 files you extracted from the downloads into the directory:

"${WINEPREFIX}/drive_c/Program Files/2K Games/BioShock/Builds/Release"

... overwriting the files that are already there. Then retest.



Sound isn't working.

This issue could be related to the OpenAL library, you can fix this problem by setting the library openal32 to native (using winecfg).



General Troubleshooting.

  • Verify if your native video driver is installed properly (the 64-bit version of Wine will require the 32-bit libraries of your video driver to be installed - alongside the 64-bit version).
  • Install BioShock, to a separate/clean Wineprefix.
  • Set your Bioshock Wineprefix Windows version to Windows XP (using winecfg).
  • Close BioShock, and reboot Wine by typing wineserver -k.

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Stuck at title screen
by Martin Vu on Monday August 13th 2012, 3:51
I am using wine 1.4, i have installed everything you guys told me to install, but when i got to the title screen, i couldn't see my mouse anywhere. there are no buttons like new, options,... there is only the bioshock logo. so what should i do to fix this?
No executable files
by Raffaele on Thursday August 18th 2011, 12:39
With some problems, the game installs (securom protection, 2k updater) but in the folder there aren't any executables so It doesn't start... Manual patch doesn't work (I think the game version is 1.1 however).
Installation creates no Bioshock.exe
by Olof Nord on Saturday June 18th 2011, 4:15
Installing the game, and in the end of the installation changing the ownership of the BioShock directory so it is not erased by the failed patching.

But there is no Bioshock.exe file in the BioShock directory. In fact, there is no .exe file at all.

Tried to install the game using both BSAutoRun.exe and setup.exe, but with no difference.

Using Ubuntu 11.04 x64, wine 1.3.22 and a HD 4850 with the radeon driver.
RE: Installation creates no Bioshock.exe
by William J May on Tuesday August 2nd 2011, 3:26
Chmod on the directory alone is not enough.

Personally, I get through the install to where it tries updating.
Then open a terminal and [wineserver -k]
And manually patch it.
RE: Installation creates no Bioshock.exe
by robert on Thursday September 22nd 2011, 4:46
Hello there,
I have an ATI card with 64 bit Kubuntu.

Bioshock is running for me - which it would not do in windows 7.

There is a program called WineQT4 - in the repositories. It's excellent. Once installed click on the exe file in the bioshock DVD folder QT4 will open automatically. Simple click ok and QT4 will install the game and updates.

Changing the resolution without a virtual desktop is problematic. Better to use a virtual desktop. I can run the game at 1080p. It sometimes crashes but plays smoothly for most of the time and my progress is saved.

It's such an awesome game. There are a few texture glitches but I'm going to try the DLL overrides some have suggested here. I also have wine set to windows 2000.

regards#
robert.
Keyboard inactive while Bioshock is running.
by Cegu on Monday April 4th 2011, 2:41
Installed & started successfully, following instructions. BUT, trying to change ingame keyboard settings, found out that when I push keyboard buttons - game doesn't react. Thinking that maybe it just doesn't wish to change settings (sometimes happens), I start the new game, but it still doesn't react on the signals from keyboard.
Ubuntu 10.10 maverick, wine 1.3.16
I'd appreciate some help.
RE: Keyboard inactive while Bioshock is running.
by goviedo on Thursday October 24th 2013, 20:17
Happend the same thing to me. Arch Linux x64 3.11.5-1-Arch Kernel compilation.

I fix the mouse problem, had to set to force_edge no false.
RE: Keyboard inactive while Bioshock is running.
by goviedo on Monday October 28th 2013, 8:32
Sorry for the comment past below... BioShock has the inactive keyboard because there is an option in winecfg. You hava to let the windows controlled by winecfg. "Allow the window manager control the Windows"
ticked!!!.
Bioshock crashes while loading a New Game
by Lars-Philip on Tuesday November 16th 2010, 14:11
I can install and patch Bioshock fine and it starts up wonderfully. I followed the howto and have vcrun2005 installed, including the library overrides that are mentioned. But when I click and new game and select the difficulty it just crashes on the loading screen after a few seconds of normal loading with not much of an error: pastebin.com/awQ3wZ42

This is with a clean 32bit prefix. I also tried a clean 64bit prefix and of course at the start my normal prefix. Nothing seems to help, it always crashes at the same point at the loading screen. :(
RE: Bioshock crashes while loading a New Game
by Kris Blackhall on Wednesday November 17th 2010, 4:01
I will need a little more information to be able to assist you :-

Linux distro version
Wine version
How you installed wine (compiled yourself? etc...)
CPU
Graphics card
Graphics drivers
How you installed graphics drivers

Recommended you run on 32bit as that is how wine is programmed to run best.
RE: Bioshock crashes while loading a New Game
by Lars-Philip on Wednesday November 17th 2010, 9:17
Sorry, normally I think of that.
My machine is a phenom X4 955 with an nvidia 8600GT graphics card, running 260.19.21 drivers installed from the 64bit Archlinux repositories (which is of course also my linux distro). Wine is version 1.3.7 and also installed from the arch repos.
RE: Bioshock crashes while loading a New Game
by Kris Blackhall on Thursday November 18th 2010, 3:54
OK. The issue is most likley with your distro. You are running on 64bit. Wine is not programmed to function in a 64 bit environment and will be more unstalbe as a result. I would recommend changing to 32bit.

Before you try that however. Try changing wine to the latest stable version rather than the beta version. Ensure you completely remove wine and then manually delete the .wine and .winetrickscache folders. Then reinstall to the latest stable version.
RE: Bioshock crashes while loading a New Game
by Kevin Whitaker on Tuesday December 28th 2010, 14:12
I have this same issue, but on OpenSuse 11.3. Running the same wineprefix on Ubuntu (64bit even) yields no issues. Am currently trying to find out what is causing it. I've tried multiple kernel versions(/34 and .36), multiple wine versions of different Architechtures, and am now trying other factors out, like graphics drivers(I have currently nvidia with same version too.) and patches.
RE: Bioshock crashes while loading a New Game
by Kevin Whitaker on Wednesday December 29th 2010, 9:48
using same graphics driver didn't change anything. I'm not sure what is causing this.
RE: Bioshock crashes while loading a New Game
by Lars-Philip on Sunday April 10th 2011, 14:24
I just got Bioshock to work. But only with playonlinux. It's using wine version 1.3.10 and it just works. :)
RE: Bioshock crashes while loading a New Game
by Kevin Whitaker on Sunday April 10th 2011, 22:27
Interesting, I haven't yet gotten Bioshock to work with Playonlinux(what i've used all this time) even usign 1.3.10.
i have this problem too.
by Nikolai M. on Sunday February 20th 2011, 23:42
i have this problem too.

ubuntu 10.10 amd64
wine 1.3.14 from official wine's ppa
cpu: amd athlon x2 5000+
gpu: nvidia 7800 GT with latest proprietary official drivers

what is to be done?
RE: i have this problem too.
by Nikolai M. on Sunday February 20th 2011, 23:51
also, i'm trying to set graphic low

output: pastebin.com/exY1qGFn
mouse pointer stick to one side of my screen
by rudy Z on Tuesday September 21st 2010, 14:17
Hello,

I just installed Bioshock, replaced the file to correct red fog issue and put the key to solve mouse problem in regedit

however I cannot play the game: when I'm on the main menu screen, the pointer of my mouse is stuck to the top or the bottom of my screen.
I can move it laterally, but when I move it up or down, the pointer moves but directly goes back to the top or the bottom of the screen.

Consequently, I cannot reach the NEW GAME button...

can someone help me??

thks

Z.
RE: mouse pointer stick to one side of my screen
by David on Thursday December 9th 2010, 22:19
Open Default.ini and go to line 561. Replace "False" with "True" and that fixed it for me. (put it into nonfullscreen) I think its a bug with the fullscreen force when you have different aspect ratios but I have no idea.
RE: mouse pointer stick to one side of my screen
by David on Thursday December 9th 2010, 22:26
GAH i had a stoke when typing ... Replace True with False >.>
All bugs except for mouse should be fixed in wine-1.3.2
by Dan Kegel on Saturday August 28th 2010, 8:03
If you can build wine from git, try it now; the only bug left
should be the good old mouse problem.
Gameplay video
by Jake ward on Monday July 19th 2010, 5:21
www.youtube.com/watch?v=l3FQLl3zrxI

Gameplay of Bioshock in Linux, Game should run much better as shown in the video as recordmydesktop slows it down a lot, Sorry about being killed by the big daddy 3 time!!!! D:
RE: Gameplay video
by Kris Blackhall on Monday July 19th 2010, 6:33
Very good, glad to see that it is working.

This intro is quite dramatic!
fglrx
by William J May on Wednesday March 10th 2010, 3:36
I'm pretty sure this is a fglrx thing since I don't see it mentioned anywhere...
I installed the game loaded up, looks great! Start playing, autodetect set visual quality to high, looks good but laggy. So I turn off a few things and it gets worse. It gets to the point that I can't play because I can't see anything! Semi-flashing polygons radiating in all directions everywhere. Although menu is untarnished.

Any suggestions other than reinstall?

Mandriva 2010, fglrx 8.70.3 (10.2), 2600XT, AMD dual-5400 2.8Ghz, kernel 2.6.31.6, Wine 1.1.39 from src
RE: fglrx
by Philipp Lorenz on Thursday March 11th 2010, 12:53
Did you try PlayOnLinux? Also, try to follow my test result (OpenSuSE 11.2 Silver)
RE: fglrx
by William J May on Monday March 22nd 2010, 4:57
I'm not want to use PlayOnLinux even though it is available in Mandriva repos. Not big on third-party scripts since the highest valid test rating would be Gold.

I'll try again with 1.1.41 or later, not a high priority right now- playing through 'Star Wars KotOR 2: TSL'
RE: fglrx
by William J May on Thursday August 18th 2011, 2:53
Tried Wine 1.3.25, still there.
err:d3d_draw:drawStridedFast >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawElementsBaseVertex @ drawprim.c / 46
Shows up alot. Can work around it by exiting to menu, then reloading save. Pretty sure it's GLSL, but registry key seems useless.
Red fog all around
by Tomi Pieviläinen on Saturday February 20th 2010, 8:42
I got the game running, finally (it loads the level for a _very_ long time, way more than few minutes) but all around is some red fog. Not sure what it's supposed to be, haven't played on Windows. Does anyone else have this or have an idea how to get rid of it?
RE: Red fog all around
by Tomi Pieviläinen on Saturday February 20th 2010, 11:08
I managed to get the fog turn into translucent smoke temporarily by turning the shadow maps off. But then it came back, and no graphics setting seems to affect it.
RE: Red fog all around
by blaise on Tuesday February 23rd 2010, 23:07
With the shadershock (Flints Fix v220) the smoke and fog is white, but with the original shader programs it's red ... go figure.
RE: Red fog all around
by Philipp Lorenz on Monday March 8th 2010, 14:36
Just use wine 1.1.34 - it's working normally there (use PlayOnLinux to choose a specific wine version).
RE: Red fog all around
by Tomi Pieviläinen on Tuesday March 9th 2010, 0:47
I managed to play through in .31. In that version there are some black box artifacts with high quality post processing on, but otherwise it's fine. With .38 I had the fog, .37 couldn't load the saves and .39 couldn't even get to the main menu.
RE: Red fog all around
by blaise on Friday March 19th 2010, 0:56
P.O.L. stuff has nothing to do with Wine so why do you still try to advertise here.[rhetorical]
RE: Red fog all around
by Philipp Lorenz on Friday March 19th 2010, 7:44
1.) If you use PlayOnLinux, you don't have to remove your native wine version
2.) There's an installer for Bioshock available which is downloading needed contents (like DLLs) automatically

... and I didn't advertise it - I only gave a recommendation.
I don't like POL too much, but it is much easier if you use it to handle Bioshock.
RE: Red fog all around
by Steve on Friday April 16th 2010, 8:03
I'm using 1.1.34, have also used the current version. The red fog persists.
RE: Red fog all around
by Zachary on Saturday May 29th 2010, 22:03
I have found a hack. (Don't worry, it's really easy.)

www.gamedev.no/projects/BioShockSM2Hack/BioShockSM2Hack.html

Scroll down to the Installation section and say goodbye to red fog until the bug is fixed.
Solution Bug 6971: Mous Escape from Window
by Raziel on Tuesday August 4th 2009, 6:41
Type "regedit" into a terminal and go to HKEY_CURRENT_USER --> Software --> Wine, make a key named "DirectInput". In this key make the string "MouseWarpOverride" with the value "force".
After this key is placed, the mouse can not escape from the window.

P.S.: Sorry for my bad english...I'm swiss :)
RE: Solution Bug 6971: Mous Escape from Window
by Jack Diaz on Friday August 7th 2009, 17:33
Tried this, didn't work for me did you do this in fullscreen mode or windowed?
RE: Solution Bug 6971: Mous Escape from Window
by Raziel on Sunday August 9th 2009, 8:52
I tried this in fullscreen mode in Bioshock. In wine i have to emulate a virtual desktop because i have two screens. Maybe it's the reason?
RE: Solution Bug 6971: Mous Escape from Window
by Jack Diaz on Monday August 10th 2009, 20:51
Nvm man, I just tried it on 1.1.27 it works XD! Thanks for the tip you, Swiss are alright d(^.^)b.
RE: Solution Bug 6971: Mous Escape from Window
by Jack Diaz on Monday August 10th 2009, 23:53
Btw do you know how to fix the graphics? I had it perfect like 2 days ago it didn't do that weird graphics where it looks inverted or something. On the highest settings and no crash/slowdown on Wine 1.1.27
RE: Solution Bug 6971: Mous Escape from Window
by Raziel on Tuesday August 11th 2009, 1:51
Sorry, I have no idea. My graphic is ok, apart from a little graphic bug sometimes, a black square that appears on some doors and other things.
Do you have a ATI card?
I have a Nvidia card, it works good on it.
RE: Solution Bug 6971: Mous Escape from Window
by Jack Diaz on Tuesday August 11th 2009, 2:32
I have NVIDIA too and its gone now I had to reboot for the settings to take effect. I'm having the same issues as you I get it on all enemys at a distance. I have a NVIDIA GeForce 8800M GTS with beta drivers (190..xxx)
RE: Solution Bug 6971: Mous Escape from Window
by Mark  Ackerman  on Monday February 8th 2010, 20:48
I don't know if this is the best place for this, but I have done the regedit and my mouse is still so erratic I can't control it. I have finally got the game loading after combining so many suggestions and combining 2 torrent dowloads for Bioshock. I have it installed through Playonlinux. Can anyone point me in the direction of troubleshooting.
RE: Solution Bug 6971: Mous Escape from Window
by blaise on Tuesday February 9th 2010, 23:19
This is a common mouse problem with Unreal2+ games. Either you can try the native M$ dinput.dll or use the 'force_edge' MouseWarpOverride hack @ repo.or.cz/w/wine/hacks.git?a=commit;h=d84f68a188135abb5f6249671615b8e078b8eb24 if you know how to patch wine from source.

built against wine 1.1.38
includes system32-dlls and usr/lib/wine/*.so(if needed).
hotfile.com/dl/27935732/d620a21/Forceedgehackdlls.rar.html
RE: Solution Bug 6971: Mous Escape from Window
by Mark  Ackerman  on Friday February 12th 2010, 16:14
Are you suggesting I patch 1.1.38 with the above patch only? or are there other patches as well?
and I don 't understand the reference ..."built against wine 1.1.38
includes system32-dlls and usr/lib/wine/*.so(if needed). "?
- I guess i putt hte 2 dll files in the Systrem32 folder, but what do i do with the 2 .so files, put them in the /usr/lib/wine folder or run them, if so how?

with everything I have tried, it is getting very confusing. Could I possibly trouble you to go through the steps for a complete install from scratch (with playonlinux preferably, or directly through wine), including:
what patches to use
what version of wine to use, and
what files to replace or add before and after the games install
and what changes to the registry (like force_edge)

thanks so much
RE: Solution Bug 6971: Mous Escape from Window
by Mark  Ackerman  on Friday February 12th 2010, 19:11
OK, it seems to be working at least better! The mouse is pretty well normal though it tends to escape the screen or can't move into the bottom 1/4 of the screen. Does this sound familiar to anyone who knows any fixes, and I will post my success if I find it, THANKS.

p.s. I am also now having the problem with hanging while saving, and the below mentioned patches wouldn't patch and the below mentioned POL doesn't seem to help?? and the fire graphics are really bad with everything set to max? .. progress though!
RE: Solution Bug 6971: Mous Escape from Window
by blaise on Friday February 12th 2010, 19:34
I think that's as good as it's going to get for the odd menu behavior and the mouse. You can try different video resolutions to see what works best or solves it. Or esc the menu, move the character viewpoint to a different angle(up/down) and then try the menu again. Odd but it sometimes solves it. It takes a while to save and load levels. Just going from what I remember.
RE: Solution Bug 6971: Mous Escape from Window
by blaise on Friday February 12th 2010, 19:30
You can drop the 2 dlls into windows/system32. Rename the old dll files to *.old as backups. 'force_edge' under DirectInput/MouseWarpOverride.
RE: Solution Bug 6971: Mous Escape from Window
by Zootal on Thursday April 3rd 2014, 14:40
Here it is several years later, and this bug still exists, and this fix still works. The Wine bug list says it is fixed, but it isn't - the mouse still escapes. Applying this registry fix worked great.
Hangs while saving
by Mike on Sunday June 7th 2009, 9:55
It seems like everyone else is having great luck with Bioshock and while I managed to get the game running, it's hanging almost every time I save. There's no output in the terminal when this happens, it just sits at the save screen for minutes and I have to kill Bioshock.exe. I've applied the mmap and malloc patches (wine-1.1.22 and now 1.1.23), then made a new wine directory and installed vc2005sp1 and directx9. Any suggestions?
RE: Hangs while saving
by NSLW on Monday June 8th 2009, 9:21
Yes i do have got one suggestion: someone here posted about PlayOnLinux (just install POL and then Bioshock) , so you may want to give it a try. It applies preloader hack. It works for me and game doesn't hang on saving.
RE: Hangs while saving
by Mike on Monday June 8th 2009, 10:07
I looked at that the other week and I couldn't find any information on how the binaries were built or what patches were included, then not knowing the builder.. It's just not for me.
RE: Hangs while saving
by NSLW on Monday June 8th 2009, 11:04
My work is intended to facilitate installation and running of Bioshock not to document how i made it or what i used. Patches are well known and i named them just for my convenience and i don't think average user is interested in that. What for do you need this info? , if you would be able to understand it you wouldn't ask here what to do to run Bioshock.
RE: Hangs while saving
by Mike on Monday June 8th 2009, 12:11
You said "preloader hack" and I don't see anything like that here. The only patch I recall using that's touched loader/preloader.c was something in the Mass Effect comments. Apparently the patch you're talking about isn't well known enough if it's not even mentioned here.

The average user may not be interested, but surely I'm not alone in wanting to know what it takes to get Bioshock running under wine. Why do I need this info? So I can inspect the patches, apply them, and build wine myself in order avoid running binaries from unknown sources.

I don't understand your question about my not understanding. Wine is a complicated piece of software. Even if everything was properly documented here, I could still run into any number of problems and need help.
RE: Hangs while saving
by DL on Monday June 8th 2009, 21:59
Check this bug: bugs.winehq.org/show_bug.cgi?id=13335
The preloader hack isn't listed in that bug, but these two patches are likely to work much better:
bugs2.winehq.org/attachment.cgi?id=20483 - mmap patch
bugs2.winehq.org/attachment.cgi?id=20484 - malloc patch

Search the bug tracker and you should be able to find the preloader hack if these 2 patches don't work for you.
RE: Hangs while saving
by chourmovs on Monday June 8th 2009, 10:10
It worked for me and is actually the easiest way to run bioshock on linux
thanks to the scripter
RE: Hangs while saving
by Chris on Monday June 8th 2009, 10:20
Does PlayOnLinux / Bioshock Script work with Steam?
RE: Hangs while saving
by NSLW on Monday June 8th 2009, 10:48
This script is intended to work with DVD version (no autopatcher), but if you give me the path where Steam downloads your Bioshock then I could modify only small part of script so it could adopt Bioshock downloaded by Steam (if you use Steam installed from PlayOnLinux) This way I successfully made script for Fallout 3 installed either with DVD version or Steam.

If your version of Bioshock uses autopatcher and it hangs on the end of the installation then you should give me name of autopatcher proccess and i can make script handling this version too.
RE: Hangs while saving
by Mark  Ackerman  on Friday February 12th 2010, 19:04
Ok I have the saving and hanging problem, and have POL already installed but don't see anywhere how to install the "preloader hack", can you be more specific or detailed? Thanks, it is getting closer to being functional!
RE: Hangs while saving
by Mark  Ackerman  on Friday February 12th 2010, 20:55
OK it is saving now and I am not sure what fixed it or if it is just a inconsistent glitch, but what I have done since the time of the problem was ... added some dll files to go into the BioShock/Builds/Release directory!, not System32!
∘ d3dx9_36.dll, msvcp80.dll, msvcr80.dll, xinput1_3.dll

still having issues with the graphics (bad fire), and mouse escaping the window, though getting better!
PlayOnLinux
by NSLW on Sunday May 17th 2009, 9:09
Hello,
if someone is interested there is PlayOnLinux script [ www.playonlinux.com/en/topic-2586-script_Bioshock.html ] which installs Bioshock (you even have got ability to patch to 1.1). You don't have to compile from sources to get mouse working.

PS. The script is very fresh and needs more testing so expect small issues. However it works for me.

PS. If someone knows additional tweaks/fixes please inform me it would be much appreciated.
RE: PlayOnLinux
by Zarmakuizz on Monday September 14th 2009, 17:19
I have tried it, but it didn't work. I then did a simple installation, all was ok (complete installation, i am actually playing to see if i can go in Medical Pavilion without a freeze).

Good luck for your script !
RE: PlayOnLinux
by NSLW on Thursday September 17th 2009, 7:51
It would be nice to know:
1) What version of Bioshock you've got?
2) What was the cause of failure?
RE: PlayOnLinux
by Zarmakuizz on Thursday September 17th 2009, 11:48
Oh sorry, i have forgotten to mention anything. ^^
So, I have the disk of Bioshock with the last update of directx of June 2007. I remember it was the 1.1 version of Bioshock, but i cannot be sure.
For wine, i have the 1.1.29 version.
For PlayOnLinux, i have the 3.6 version.


The installation has started, one thing has failed : the auto update manager (he cannot connect to the server).
Then, when i wanted to update the game myself, there were no Bioshock.exe file (it should have been into the folder of bioshock/Builds/Release/ ). So, the game cannot start.

When writing this message, i was trying to install bioshock via PlayOnLinux and then complete the missing Bioshock.exe from the wine-installed game. But this time, the installation and the auto update succeded. I can even start Bioshock without any no-cd.

However, when starting the game via PlayOnLinux, nothing did happen.
I have started the PlayOnLinux executable Bioshock.exe myself with the mouse's click (/home/$USER/.PlayOnLinux/wineprefix/Bioshock/drive_c/Program Files/2K Games/Bioshock/Builds/Release/Bioshock.exe), not via PlayOnLinux. The game has started, he has recognized my saves, but when i choose to have a 1440*900 screen resolution instead of the basic resolution (1024*768 ?) (with the basic resolution i have the Gnome task bars), the effect was like a kill -9 -1 command. Usually the wine-installed version don't do that.
I have tried another time, i can see the game works, the mouse can be ok, the graphic changes do not do a kill -9 -1 anymore. So, the game looks like to work.
Thank you for the patch. :D

Is is normal that PlayOnLinux cannot start the game himself ?
RE: PlayOnLinux
by NSLW on Thursday September 17th 2009, 12:22
"The installation has started, one thing has failed : the auto update manager (he cannot connect to the server)."

You've got Bioshock with auto update manager. I know that there is problem with your version and I cannot do anything about it because:
1) I created script working on Bioshock without auto update manager
2) I haven't found anybody willing to help at creating script for Bioshock with auto update manager

"Is is normal that PlayOnLinux cannot start the game himself ?"
Sometimes yes, but it's so because:
1)there are various versions of the same game in different countries
2)there are regressions in Wine
3)wrong NO-CD is used
RE: PlayOnLinux
by Zarmakuizz on Thursday September 17th 2009, 13:17
During the last installation, the auto update manager have worked, and well worked. I don't really know what was different, maybe i have already installed Bioshock with wine only...

I have tried to start Bioshock via PoL with and without a NO-cd executable, same result.


Well, as long as it works, this is fine for me.

Thank you again !
RE: PlayOnLinux
by Kyle on Sunday November 8th 2009, 16:55
I installed it and patched it succesfully but when I try to run from play on linux nothing happens any ideas?
RE: PlayOnLinux
by Mark  Ackerman  on Tuesday February 2nd 2010, 6:39
I am using Playonlinux as well and have installed, updated, and at best it opens up, I can even change options, but when I run the game it starts to load then crashes. I am trying everything below with no luck yet.
Any help would be appreciated.
RE: PlayOnLinux
by Mark  Ackerman  on Monday February 8th 2010, 20:52
I know have manged for it to load though all the graphics and audio is crazy and the mouse is so erratic it is unmanageable....any ideas??
RE: PlayOnLinux
by Mark  Ackerman  on Friday February 12th 2010, 23:04
I fixed the mouse mostly (read in the mouse erratic thread), though it still has problems when reaching full L. or R. positions, and the graphics are good except with anything red (smoke or fire) makes the screen TOTALLY red, any ideas here?
RE: PlayOnLinux
by Türklinke on Saturday March 6th 2010, 14:04
Switch to 1.34 ... There it works, you just have sometime when s.th. burn some little black boxes, but really better then red smoke... Damn this game is loading ages (runs perfectly under highest settings, but really needs ages to load or to save ^^)
Advanced Setup
by John P Sims on Saturday May 16th 2009, 16:25
get wine-1.1.21 souce
patch source with mmap patch from bugs.winehq.org/attachment.cgi?id=20483
patch source with the malloc patch from bugs.winehq.org/attachment.cgi?id=20484
compile and install wine
install winetricks and applicable native dlls (see below)
install bioshock (see below)

Add the following to Direct3D registry:

[Software\\Wine\\Direct3D] 1242182992
"OffscreenRenderingMode"="fbo"
"PixelShaderMode"="enabled"
"SoftwareEmulation"="enabled"
"UseGLSL"="enabled"
"VertexShaderMode"="hardware"
"VideoDescription"="NVIDIA GeForce 9800 GT"
"VideoDriver"="nv4_disp.dll"
"VideoMemorySize"=dword:00000400
"VideoPciDeviceID"=dword:00000605
"VideoPciVendorID"=dword:000010de

Obviously, you must modify some entries to match your hardware. Not all of these settings are necessary, but they shouldn't break anything.

Page faulting should be significantly reduced. You should now be able to run with higher graphical settings. Overall stability, performance, and graphical fidelity should improve.

I played for 5 hours straight last night - starting at the beginning - and made it all the way to the end of Neptune's Bounty with no crashing.

Mouse is still problematic. More of an annoyance, really.
RE: Advanced Setup
by NSLW on Sunday May 17th 2009, 10:35
Your two patches are causing instability of the game. The game has more unhandled exceptions and segmentations errora at the beginning. For me it's better to run without these patches.
RE: Advanced Setup
by John P Sims on Sunday May 17th 2009, 22:52
I'm afraid I can't take any credit for the patches, but they worked pretty well for me.

Your saying the game has more unhandled exceptions and page faults than before? Normally, you should only get one or the other. After which, the game will become unresponsive and you have to terminate it.

Could you report your configuration and findings on the use if these patches to Bugzilla?

Here's the link: bugs.winehq.org/show_bug.cgi?id=13335

thanks
Installing and playing
by John P Sims on Sunday May 10th 2009, 23:35
install wine-1.1.21
get winetricks from www.kegel.com/wine/winetricks
get bioshock 1.1 patch from downloads.2kgames.com/bioshock/patch/Bioshock_Version_11_Patch_Worldwide_Retail.zip
open a termial
start install with "wine /media/cdrom/setup.exe"
accept the license agreement
do the typical install
installer will download the latest patch and ultimately fail because the it thinks that the patch has an invalid signature
ALT-Tab back to the terminal and Ctrl-C out of the running wine process back to the command prompt
type "wineboot -k" to terminate all running wine processes
use winetricks to install ie6 vcrun2005sp1 and directx9
unzip the patch
patch your installation with "wine Bioshock\ Version\ 1.1\ Patch\ Worldwide\ Retail.exe"
change directory to ".wine/drive_c/Program\ Files/2K\ Games/BioShock/Builds/Release"
launch game with "wine Bioshock.exe -dx9 -nointro"
activate game with your serial number
game should start normally
navigate to the "Graphical Options" menu
at the minimum, turn off "Shadow Maps" and "Distortion" and set "Texture Detail" to medium
lowest graphical settings are best
leave the resolution at 1024x768
play
you should at least be able to make it to the "Medical Pavilion" level.
RE: Installing and playing
by mrshroom on Thursday July 9th 2009, 15:10
Before you install vcrun2005sp1 you need to get vcrun2005 itself, otherwise this works perfect and I'm using a self-compiled wine 1.1.25 in a 32bit chroot
RE: Installing and playing
by John P Sims on Friday July 10th 2009, 1:13
Noted. Thanks! Please post your results!
Installing
by Zarmakuizz on Thursday May 7th 2009, 16:07
If you do the install like the last comment before itself and the game still not work, you can try to start with the terminal and you will see the failed dll.
If after that it still not work... retry exactly the instructions. ;)


Actually Bioshock is unstable when playing. I can't play after the Andrew Ryan video, sometimes when the mouse is on the right/left of the screen it doesn't move on right/left anymore and the loading time is very long...
RE: Installing
by Mark  Ackerman  on Friday February 12th 2010, 23:06
my mouse is fixed except with the same problems you mentioned???
how I installed it
by Mark on Monday January 26th 2009, 0:50
I also installed "Bioshock".
Puppy Linux, wine 1.1.12.
It starts, but uses Pixelshaders.
The catalyst driver 8-12 has an incomplete implementation of OpenGL, so Wine games using this, remain black
You hear the sound, but see nothing.
I searched hours for fixes, but they do not exist.
The driver is just too bad for this.
With the onboard Nvidia 7050 I could see something, but it was like still images so slow.
So to play that, a 7600 GT for 60 Euro or better is required.
The installation required to intall vcrun2005 with winetricks, and to run the redist installation from the CD. Also d3dx9_36.dll must be copied to /root/.wine/drive_c/Programme/2K Games/BioShock/Builds/Release.

Important:
At end of installation, it downloads an upgrade. Though it was retrieved, it is not found. If you continue now, the whole installation will be deleted again!
So hit CTRL-ALT-Backspace to exit X, or use "ps -ax" to find the processnumbers, and terminate them with
kill -9 number
The Bioshock.exe still is there then, and you can start the game by running it.

Full text:
www.murga-linux.com/puppy/viewtopic.php?p=268956#268956
Mark
RE: how I installed it
by Nicole on Tuesday January 27th 2009, 8:47
Please remove your root wine directory and reinstall wine as your everyday user. Running wine as root is *dangerous* and should be avoided at all costs.

Please file bug reports for the errors with the download if you have not done so already. Thanks for helping make wine better!
RE: how I installed it
by Mark on Tuesday January 27th 2009, 10:43
Puppy is a liveCD System with read-only layered filesystem. Root is the standarduser here, Multiuser support is only rudimentary existent.
But due to the LiveCD origin, you do not have the typical problems with this as in a distro installed full to harddisk.

I made some more tests with the Nvidia 7050 chip.
Using the pixelshaders from shadershock.tk mentioned by GNU_Raziel (Shader Model 2).
Quality settings modified in default.cfg to very low values.
It now is playable, at least the first scene, where you enter the lighthouse, and use the "elevator" down.
There several cutscenes are played, and then it hangs.
I also encounter various crahes, and with these settings, it looks pretty ugly.
In the sum, too many problems to have a closer look, I played Riddick instead, that I coud finish without a single crash :-)

Mark
RE: how I installed it
by blaise on Saturday February 28th 2009, 21:57
Riddick is the bee's knees. Better than Doom 3 & Quake 4. I wonder what Riddick:Dark Athena holds in store....

p.s. Don't waste the time with Bioshock unless you're masochistic. The code is a mess. I wish I could take my rating back.:/
RE: how I installed it
by mrshroom on Thursday July 9th 2009, 15:08
you can just use winetricks to install d3dx9
newbie
by skyline on Wednesday January 21st 2009, 22:12
I have a guite powerfull video card which has pixel shader 2.0. But bioshock requires pixel shader 3.0. Is there any way to play this game in wine. I'am new to wine. thanks.
crashing bioshock
by Stefan Allmann on Monday January 5th 2009, 10:35
Sadly, even with 1.1.12 Bioshock still crashes quite often. So I made a short script which keeps the Bioshock config intact and eases the start of the game.

#!/bin/bash
rm -rf ~/games/bioshock/drive_c/windows/profiles/stefan/Anwendungsdaten/Bioshock/Running.ini
WINEPREFIX=~/games/bioshock ~/games/bioshock/wine/wine ~/games/bioshock/drive_c/BioShock/Builds/Release/Bioshock.exe -nointro -dx9

I use a separate wine version for each game and a start script to run them. Some people call it stupid but I found it very convenient as this way I can have games using different wine versions running at the same time without intefering. Especially if you need a patch like the one for Bioshock and don't want to possibly mess up your other games.
Addition to new test data
by blaise on Saturday December 6th 2008, 11:03
I forgot to add to my test data that if you experience hanging/bombing out when loading a level or a new game the low mem area hack/patch at bugs.winehq.org/show_bug.cgi?id=14657 fixes the problem. Your mileage may vary depending on your machine/config.
RE: Addition to new test data
by Chris on Sunday December 28th 2008, 0:42
Will this hack get us past the second level?
RE: Addition to new test data
by Stefan Allmann on Sunday December 28th 2008, 21:28
I tried and seemingly yes, it will. I got so far as to "Fort Frolic", however using the hack Bioshock will start crashing or just exiting non-reproduceable at random times and places. I could play the complete second level "Welcome to Rapture" in one go on my first try but could never repeat it. At least three or four times I have to restart from a quicksave (and reconfigure Bioshock as it always discards its config settings on exit) to get through. Sadly the hack will sometimes also result in crashes in the first level even before reaching the lighthouse and it makes level loading excruciatingly slow. From some gamesites I got savegames of all the levels and they work, even facing Fontaine and ending the game is possible. Interestingly, with the hack I can crank the detail settings all the way up to max without any further decrease in stability.
So I guess only a little bit of tweaking on Wine and it should run fine. The intro video and sometimes the level loading screens are upside-down. But I'm using an nvidia card and I blame it on their drivers.
Back