It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi !
I get this error every time I start a game, or even when I click on the credit button.
I suppose this is due to an issue with the graphical engine of the game, but running it in compatibility mode doesn't help at all.
I got an ATI hd5870, and I7 860 proc and I run windows 7 64 bits, if that's any help.
I tried to tweak the options in the advanced options menu at start, but no dice.
EDIT: Apparently I can run the game in 1440*900, but not in 1680*1050.
I can start loading levels in 1440*900 and then switch to 1680*1050, and it does work, but then I have the same crash at the next loading
Post edited April 29, 2010 by PaladinGunn
This question / problem has been solved by PsychosesManimage
Hey guys. I'm running blood2 on Vista64 with compatibility mode set to win98 and running as admin. This works fine as I managed to complete the game.

The expansion however has some issues. It crashes with the usual MFC error when I switch from the Jojo level to the haunted mansion one. I hooked up a debugger and noticed that it crashed in the imusic dll, so I disabled music and managed to load the level without issues.

Thought this might be helpful to some people.
Thanks for the tip on how to get this game to run :) Just changing the compatibility mode to Windows 98 / Window ME but leaving the rest of the settings alone as they were setup when installed worked out great on my Windows 7 X64 setup.


avatar
BertSt: Hey guys. I'm running blood2 on Vista64 with compatibility mode set to win98 and running as admin. This works fine as I managed to complete the game.

The expansion however has some issues. It crashes with the usual MFC error when I switch from the Jojo level to the haunted mansion one. I hooked up a debugger and noticed that it crashed in the imusic dll, so I disabled music and managed to load the level without issues.

Thought this might be helpful to some people.
Post edited March 15, 2012 by Trebor
Myself I'm running Win7 x64 w. a Radeon 6870 card, had various issues.
Setting to WinVistaSP2, turning off desktop composition etc. got rid of the MFC problem.

But;
The fact that I was running two monitors messed a whole lot with Blood2, it worked fine if I set it to render to my secondary low res monitor (1280x1024), but never ran stable with D3D on my main monitor, also seemed to switch monitors when changing res in game.
(regardless if I picked Primary display driver, \\Display1 or \\Display2 in Blood2 setup.

The only really good solution was to disable the secondary monitor, and only have one active while playing. (45 minutes into the game, so far so good).

Maybe this will help someone out there...
I can con firm that using a 4:3 resolution (in my case 1280:960) fixes the MFC crashes. 1024:768 also works.

Daedolons Posting from 2010

1280:1024 (5:4) was crashing on each level loading.
Post edited December 17, 2012 by Guter
avatar
Guter: Snip
Here's something that worked for me. Set all the Blood 2 EXEs to not run in any compatibility mode but only administrator mode. Run taskmgr.exe in administrator mode and, in the processes tab, change the Client.exe's affinity to one core while running the game.

You could also make a batch file to do this automatically:
http://www.gog.com/forum/blood_series/blood_2_crash_likely_fix

FYI I understand that running the game in a compatibility mode automatically sets the affinity to a single core. For some odd reason the compatibility mode will still glitch it out though and cause a crash. It seems that running the game with one core is all that is needed.
any one found a fix for this issue? Its really annoying
avatar
PsychosesMan: Have you tried it with everything in Advanced Options unchecked? Did you check the box to install Nightmare Levels in the installer?

EDIT: Also Lithtech seems to really not like super-high resolutions, so see if it works at 640x480 and if so ratchet it up and see how far you can get it without crashing. I play at 1024x768.
That didn't seem to work. For one point, I don't want to play the game with everything disabled, and even if I do and try every resolution and renderer there is, the game still crashes with "Client MFC". If someone found a solution to this problem, I would be very happy!
the batch file doesnt help...

The game runs fine in 1600x900 but not 1920x1080 (D3D)
I have the same problem, but I found another solution (for 1920x1080)
First start a game with the software renderer, go to the options menu and change it to D3D Renderer, and then it works with D3D, but this must be done each time...

Otherwise this game works only with the Software renderer on my PC
Post edited December 16, 2013 by nimrahwt
I was getting the same Client MFC Application error on Windows 7 too. I went into the Launcher's "Advanced" settings and disabled everything in the "Enable" category. Then I set the resolution to 1024x768. The game worked after I made those changes.
Hmm. I'm having a hard time figuring out which the #1 setup that makes the Lithtech engine games like Blood 2 & Shogo much more stable. Somebody's gotta make a sticky topic on Blood 2 & Shogo's pages. Could anyone figure it out?
Here's how to fix it
Open/edit "autoexec.cfg" with Notepad


Search and Delete the following texts
-----Start---------

rangebind "##keyboard" "##58" 0.000000 0.000000 "RunLock"
rangebind "##keyboard" "##45" 0.000000 0.000000 "AltFire"
rangebind "##keyboard" "##56" 0.000000 0.000000 "Strafe"
rangebind "##keyboard" "##201" 0.000000 0.000000 "LookUp"
rangebind "##keyboard" "##209" 0.000000 0.000000 "LookDown"
rangebind "##keyboard" "##22" 0.000000 0.000000 "MouseAimToggle"
rangebind "##keyboard" "##23" 0.000000 0.000000 "Crosshair"
rangebind "##keyboard" "##26" 0.000000 0.000000 "InventoryLeft"
rangebind "##keyboard" "##27" 0.000000 0.000000 "InventoryRight"
rangebind "##keyboard" "##12" 0.000000 0.000000 "ScreenShrink"
rangebind "##keyboard" "##13" 0.000000 0.000000 "ScreenEnlarge"
rangebind "##keyboard" "##53" 0.000000 0.000000 "HolsterWeapon"
rangebind "##keyboard" "##40" 0.000000 0.000000 "NextWeapon"
rangebind "##keyboard" "##39" 0.000000 0.000000 "PrevWeapon"
rangebind "##keyboard" "##211" 0.000000 0.000000 "DropWeapon"
rangebind "##keyboard" "##25" 0.000000 0.000000 "Proximities"
rangebind "##keyboard" "##19" 0.000000 0.000000 "Remotes"
rangebind "##keyboard" "##48" 0.000000 0.000000 "Time"
rangebind "##keyboard" "##67" 0.000000 0.000000 "Respawn"
rangebind "##keyboard" "##34" 0.000000 0.000000 "Grab"
rangebind "##keyboard" "##20" 0.000000 0.000000 "Message"
rangebind "##keyboard" "##21" 0.000000 0.000000 "Taunt"
rangebind "##keyboard" "##59" 0.000000 0.000000 "LevelInfo"
rangebind "##keyboard" "##15" 0.000000 0.000000 "Frag_Bar"
rangebind "##keyboard" "##64" 0.000000 0.000000 "QuickSave"
rangebind "##keyboard" "##65" 0.000000 0.000000 "QuickLoad"
rangebind "##keyboard" "##2" 0.000000 0.000000 "Weapon_0"
rangebind "##keyboard" "##3" 0.000000 0.000000 "Weapon_1"
rangebind "##keyboard" "##4" 0.000000 0.000000 "Weapon_2"
rangebind "##keyboard" "##5" 0.000000 0.000000 "Weapon_3"
rangebind "##keyboard" "##6" 0.000000 0.000000 "Weapon_4"
rangebind "##keyboard" "##7" 0.000000 0.000000 "Weapon_5"
rangebind "##keyboard" "##8" 0.000000 0.000000 "Weapon_6"
rangebind "##keyboard" "##9" 0.000000 0.000000 "Weapon_7"
rangebind "##keyboard" "##10" 0.000000 0.000000 "Weapon_8"
rangebind "##keyboard" "##11" 0.000000 0.000000 "Weapon_9"



----Ended------

I found that the game doesn't support the codes to key ("##xx")
2. Now delete them and save the file(still as autoexec.cfg)
3. Play the game, but certainly you have to re-bind the keys again


Note:
ALT is unusable for unknown reason

Don't bind the special keys such as Shift, Ctrl. You have to edit the .cfg for example
rangebind "##keyboard" "Left Shift" 0.000000 0.000000 "Run"


Now works fine on 1440x900 D3D mode and Music is on
It still doesn't work for me, in spite of me having tried every single solution written in this topic.

I regret buying this..
avatar
Westermaann: It still doesn't work for me, in spite of me having tried every single solution written in this topic.

I regret buying this..
I never had any trouble with a game I bought on gog, this is the first one. I regret it too.
avatar
PsychosesMan: Have you tried it with everything in Advanced Options unchecked? Did you check the box to install Nightmare Levels in the installer?

EDIT: Also Lithtech seems to really not like super-high resolutions, so see if it works at 640x480 and if so ratchet it up and see how far you can get it without crashing. I play at 1024x768.
I unchecked those boxes and changed the resolution to 1024x768 and it works. But it is normal that the fps rate drops to very low rates when some light effects are in view? I can play Crysis 3 on Ultra High with high fps but Blood 2 stutteres :-? I would guess D3D is not working but it is configured to be used...

And I have some issue with the Game Launcher. I always can only open one menue and change things in them. When I go back to the previous menu clicks will not be recognised any more. I have to close and re open the launcher to change something in a different menu or to start the game. This is strange.
avatar
g0dL1ke2020: This is strange.
Not really. Blood 2 is just a broken piece of shit of a game. Don't count on getting it fixed either. I've tried millions of things until I gave up and got a refund after a small debate with Gog.