Painkiller: Black Edition

Painkiller: Black Edition

Game crashes when I save
I haven't had this issue until I got to the Docks level. When I reach a checkpoint or try to save manually, it crashes immediately. The same also happens when I try to load that save after starting up the game again. Can anyone help with this issue? My specs are:
Windows 10, Intel Core i7-5500U, NVIDIA GeForce 940M, 8 GB RAM
Last edited by Sir Simothy Jam XXXII; Jun 4, 2017 @ 8:37pm
< >
Showing 1-15 of 15 comments
Peppins Jun 5, 2017 @ 12:46pm 
Corrupted savegame, try to delete them one by one until this bug disappear.
Originally posted by Peppins:
Corrupted savegame, try to delete them one by one until this bug disappear.
I tried each save, deleting the ones that resulted in the game freezing or a CTD, until I found one that works. I played using that save for a while, but after a few checkpoints, I died, and I couldn't load my save from the last checkpoint.
Peppins Jun 6, 2017 @ 10:00am 
Try to limit fps when you play and run in compatibility mode if you're on win 10.
Originally posted by Peppins:
Try to limit fps when you play and run in compatibility mode if you're on win 10.
I've tried compatibility mode for XP SP2, XP SP3, Vista, Vista SP1, Vista SP2, and 7. None of these resolve the issue.
How would I limit the FPS?
Peppins Jun 8, 2017 @ 2:11pm 
Open the console and write /setmaxfps 120

Here for more:

http://steamcommunity.com/sharedfiles/filedetails/?id=472947921

ps. try aso to run the game as administrator
Last edited by Peppins; Jun 8, 2017 @ 2:12pm
Originally posted by Peppins:
Open the console and write /setmaxfps 120

Here for more:

http://steamcommunity.com/sharedfiles/filedetails/?id=472947921

ps. try aso to run the game as administrator
I am running the game as administrator.
Writing /setmaxfps 120 in the console doesn't change the fact that opening my save crashes the game.
I don't have the lua files to access the script for max FPS.
Peppins Jun 9, 2017 @ 10:58pm 
The fps modification just make the game more stable (and about the lua file, there is a download link in the guide, at the start).

Your only option is to delete sevagames :/
Originally posted by Peppins:
The fps modification just make the game more stable (and about the lua file, there is a download link in the guide, at the start).

Your only option is to delete sevagames :/
I loaded the autosave from the beginning of the level, and made my way through the rest of it without any issues.
Drunk Monkey Jul 5, 2017 @ 5:55pm 
I deleted all my saves and started from the beginning and still had an autosave freeze. on the first level. I limited fps to 150 and on W7. I got a retail copy and applied each patch and played. 1.31 was the last patch that worked. The bug was introduced in 1.35.
Last edited by Drunk Monkey; Jul 6, 2017 @ 10:59pm
Samwise Jul 7, 2017 @ 12:36pm 
I have beaten this game 4 times and on main game i have gotten only 2 crashes.

I copied my post from other topic, because this could potentially be helpful to you too.

What i have done is i have kept the resolution on 4:3 ratio (widescreens wasn't too common at the time afaik) and keep aspect ratio so the game still looks good. Sure, there will be black bars on widescreen monitors but its not too bad.

I have kept the graphics settings on stock, everything high, except dynamic lightning on normal, and haven't enabled character shadows.

I also limit the framerate to 60, even though the game is supposed to run at 120 afaik, but i can't hit that fps with my crappy laptop.

Now, these things apparently causes crashing:

1. Too many saves. Delete all except most recent one after beating couple of levels. Too many saves causes issues.

2. If you see glitches like battle music still playing after dying and respawning at check point, reboot the game. Same if you see expansion weapons in main game.

3. Don't use hd resolutions, limit the framerate by "/setmax fps XX" In game. To do that map a button for TALK ALL from the controls in options. Don't go higher than 120, or it will glitch the physics and can cause crashing.

4. Someone mentioned that putting dynamic lightning higher than normal might cause crashing as well. This is why i kept all the graphics settings on default, which is pretty much maxed already, though no AA is enabled, but tbh this game don't need AA. Not even on 1024x768 res.

Battle out of hell, though is crash fest. When the main game has crashed TWICE, the BOOH crashed about 5-10 times in the time it takes me to beat all maps. The lab map is especially unstable.
Drunk Monkey Jul 10, 2017 @ 3:33pm 
It only happens to some people. I have never crashed playing the game. It is only at checkpoints and loading saves. And 1.31 in the main game hasn't crashed anywhere either. So it has to be a bug with 1.35 that never got ffixed. I can play redemption and overdose I think is ok but all the others crash.
Drunk Monkey Jul 13, 2017 @ 1:49am 
I just downloaded and installed the unofficial black edition patch from pkzone and it seems to be working now!
DyslexicAnaboko Oct 28, 2022 @ 2:32pm 
I know this is a super old thread, I just wanted to pop this in here for anyone still having this problem.
I am running version 1.64 for context
I ran into this problem only one time on Chapter 4 Level 1 - Castle.
I had to do a few things, but ultimately it was a corrupted save. The corrupted save would also cause corrupted loads to occur (never ending load screen with music).
1. As stated ad-nauseum by Peppins, set your frame rate to 120 when you start the game before loading a save.
2. Perform a file integrity check, you might have corrupted files. I had one corrupted file apparently.
3. Delete your corrupted saves. You can fall back to an Auto-save hopefully or start the level over.
4. What I did as an extra precaution was just play the rest of that level without saving until finished. By the time I got to Level 2 the problem stopped.

Just a guess, but I think it's a problem with a specific save point in Chapter 4 Level 1. It's before you go under ground. That's when there is an auto save and my game just flat out crashes.

Either way, was happy I could overcome the problem and wanted to share. It's an old game, so it's understandable.
Drunk Monkey Oct 29, 2022 @ 11:06pm 
Thanks for the update. I don't ever remember it crashing like this on XP. But I played the entire game on 1.31 from insomnia to the true ending, even collecting all cards manually (which is a big plus), and it never crashed once om Win 7 so it is a random bug they caused with 1.35 and maybe later patches. And in doing this I saw that the title page was actually chenaged at least twice. I prefer the earlier titles.
Last edited by Drunk Monkey; Oct 29, 2022 @ 11:07pm
Havcom Nov 17, 2022 @ 5:43am 
Problems, you are talking about, oddly enough, relate specifically to the Steam version. Game work unstable, while older pirated editions have no problems. I cannot say for sure whether the game data is different in these versions, at first glance there seems to be no difference. However, there are problems.

SetMaxFPS will not give you anything but more or less stable physics, because at high FPS values, physics starts to lose weight, as it were. For example, when you shoot a stake at an enemy and his body flies up somewhere, this is the result of a high FPS. This is a common issue with the Havok engine. For example, in Skyrim there are also quite a few problems with physics due to high FPS.

If you're having CTDs when take a checkpoint without errors, usually compatibility with Win7, XP helps.

I also note that on pirated editions, saves almost never break.
< >
Showing 1-15 of 15 comments
Per page: 1530 50