Bioshock 2 crashes when try to save or call up map
by wineaddict on Tuesday February 14th 2012, 14:27
Bioshock 2 crashes when I try to save or call up the map
I'm using the steam version of bioshock 2 with the fake xlive.dll and revLoader.exe to bypass Steam's Steaminess. My current wrapper is using Wineskin 2.5, with the WS8Wine1.3.36 Engine and the steam, amstream, all the d3dx s, devenum, dinput, dinput8, directmusic, directplay, directx9, dmsynth, dsoun, dxdiag, dxdiagn,gfw, I3codecx, quartz, xact, xact_jun2010, xinput, baekmuk, corefonts, droid, and eufonts winetricks. I set the launch options to -nointro -dx9 in Steam.
I don't know how to fix this. Anyone else have an idea?
bioshock 2 requires d3dx9
by Yuki on Tuesday January 31st 2012, 9:08
bleh, after some late hours of troubleshooting, I finally noticed that this game requires the d3dx9 package via winetricks installed.
Otherwise it will just hang and eventually crash at the loading screen.
Finally got Bioshock 2 to play
by blaise on Sunday September 25th 2011, 16:23
Using the Razor1911 crack. Launching from a Bioshock2.desktop file I created out of another .desktop file program and adjusted and placed on my gnome panel. Remember it should point to Bioshock2Launcher.exe.
renamed to .old everything except under /SharedBinks except Credits and Waterfall
renamed to .old 2KG_logo_720P.bik and Logo.bik in BioShock 2/SP/Content/BinkMovies
Adjusted Space= in Application Data/Bioshock2/User.ini to read Space=Space=AcceptOrSelect for every instance.
Using the -nointro and -dx9 command line switches.
No need for the env XMODIFIERS switch.
When you load a new game (I hope this happens on all levels)it goes straight into the opening movie and level.:) Not sure what part above actually makes it run and skip the -SPACE- bar continuation problem but hey whatever works!
ERROR [-2] BioShock2.exe cannot be launched directly.
by scraze on Saturday April 9th 2011, 11:18
Running into a seemingly different problem. Downloading in Steam & unlocking game with serial through Steam went fine with wine 1.3.17 (from git) on Debian Wheezy / x86-64. Launching however produces the following error:
BioShock2.exe cannot be launched directly. Please launch using BioShock2Launcher.exe
The same error appears when following the suggestion to launch using BioShock2Launcher.exe. Installing the xlive dll from timeslip also didn't change the situation.
So far only tried rzr-bio2f.7z with md5sum 742739efded5d8ef17fa857f898e8abb, replaced some files in SP/Builds/Binaries/ (after a backup). When executing Bioshock2Launcher.exe, an animated Razor 1911 splash pops up, then Bioshock 2's tiny splash, and then a maximized window is created with a cross-shaped cursor, and instantly the program crashes. This happens with wine-1.3.17 as well as wine-1.3.14.
Tried to create a sensible log file but am unsure as to the proper WINEDEBUG options. A log of WINEDEBUG=+tid,+seh with razor's Bioshock2Launcher.exe can be found here: pastebin.com/jnDm9JhW . The same command for the original Bioshock2Launcher.exe creates a log file of 34Mb, so I'll refrain from posting that until I've found the correct WINEDEBUG options. Not sure whether it's any good to anyone in this format :}.
I've installed Bioshock 2 in my main wine prefix, which has a number of specific settings for libraries for different games; I could very well be causing the problem in that way. Will test with a clean prefix asap.
how about steam?
by Zdenek Styblik on Thursday December 30th 2010, 2:39
I'm wondering if Bioshock 2 from/via Valve's Steam would yield a different result. I would say no since the XLive dependency, but still - have somebody tried it? I didn't have courage to do so.