Gamebreaking CTD, Garry's Pripyat Travel load Thread - MISERY mod for S.T.A.L.K.E.R.: Call of Pripyat

Hi all, I've been chipping away to beat Misery and it's been a fun ride but after completing Pripyat Underground, and doing the first Pripyat missions to find
the Gause Rifle, I went back to Zaton to take care of that mission, Now I'm back at Jupitar trying to get to Pripyat with Garry and the load screen CTDs everytime even with the lowest graphical settings. This CTD would happen between Zaton & Jupitar but I only had to lower the graphics temporarily to make it through the loading screen before turning textures, lighting, ecetra back to what it was set at. However, I didn't have to mess with the graphical settings going through Pripyat underground the first time I loaded Pripyat. This method does not work anymore with switching the video settings to travel back to Pripyat. I tried turning off autosaves with my normal graphic settings but that still crashes. Important note: The game CTDs when loading the actual Pripyat level (When the Pripyat photos pop up) rather than CTD before the level loads like It did for me between Zaton and Jupitar.

Thank you for any help anyone might give, Its a tricky engine to mod but STALKER Misery is still one of my top games I love to play these days and I hope I can complete it to freeplay mode.

Error Reason:
----------------------------------------
xrEngine.exe caused BREAKPOINT in module "E:\MadBug\1-Games\Steam\steamapps\common\Stalker Call of Pripyat\bin\xrCore.dll" at 001B:0058E12E, xrDebug::backend()+174 byte(s)

User Message:
----------------------------------------
Expression : fatal error
Function : out_of_memory_handler
File : D:\prog_repository\sources\trunk\xrCore\xrDebugNew.cpp
Line : 336
Description :
Arguments : Out of memory. Memory request: 73731 K

That is an out of memory bug, more related to your ram then the game itself. You could tweak down alife.

Okay I tried doing that. I set the switch distance first to 150, and then to 100. Still had the same CTD. At this point I dont know what I can do... I have a feeling its crashing because the level Pripyat is a much more smaller, compact level compared to Zaton or Jupitar and new NPCs and content are too crowded loading them all at once on my PC so the game crashes. Yes my computer is not the best to run Misery, but I know it runs fine with the texture optimizer and has thus far up to the Pripyat level. The actual loading of a level when you travel to it has been the biggest problem for me.

Are there any possible fixes for this or is my playthrough screwed because of Ram?
Maybe turn my switch distance down to like 10-30 just to get the level loaded then switch it back?

Alife down to 10 sorts most problems. 100 will still cover what's happening a little beyond the laundromat. I know this was a common problem in 2.0 but I recall the fix being lowering alife. I myself have only ever had one problem and it was the medicinthefridge bug in 2.1 although I hadn't had it in previous releases. Alife at 10 fixed it first time.

Change a-life to 10 and close all other programs except the game. It should help. BTW, how many RAM do you have?

Edited by: Chorbit

Thanks guys! My game loaded the level when I set it to 10. If any other Misery players have a Out of Memory CTD when loading a new level, go to your Stalker COP directory/gamedata/Configs and go to Alife.ltx. Make a backup of that file first, then open it and change the first switch_distance number to 10. Look at the spacing between the = and numbers and make sure it looks right like the others.

After that, save and quit, then start the game and load the level. Remember to change your graphics settings down if you have to for loading a new level before hand. Travel to the new level from a CLEAN SAVE. Hard save when you get there, then exit the game and change your switch distance and graphics the way you had it working Previously. I recommend creating a desktop shortcut to the Alife.ltx file so you can easily switch the distance when changing levels after you exit the game.

Its a pain-in-the-ass-method, but it works if you dont have a Super Computer to handle Misery's Ram Consumption. Some levels might not need the switch distance change to load without getting a CTD, such as Pripyat Underground, the first time you arrive in Pripyat from Pripyat underground, Or going INTO the X8 lab in Pripyat. Mainly Zaton, Jupitar, and Pripyat are the ones that will overload the game traveling to. So keep that in mind.
BTW Chorbit I only have 2.00 GB of physical RAM, I'm running on Windows XP. xD

MaDBuG wrote:
BTW Chorbit I only have 2.00 GB of physical RAM, I'm running on Windows XP. xD

No wonder that you have issues with game. Even people with 8GB+ RAM have problems from time to time. BTW, 2.1.1 is more friendly when comes to RAM/CPU consuption. Playing with lower alife switch distance can help a lot in your situation, but don't expect miracles, sooner or latere you will have to drop switch distance to overcome your lack of RAM.

--

haha yeah but Misery runs fine with the settings I have after loading the level and my game doesn't look bad but could be a lot better with a Supercomputer. I just finished the game, and entered free play mode no problem. But yeah It looks like I just need to switch the distance back and fourth to level jump which is annoying, but hey it is what is for my computer. I'm just glad I'm able to play Misery. Best and most rewarding gameplay I've played so far. It even has

I know the new version is out, but is there any way to continue my playthrough on my sniper in freeplay If I update? I want to explore Pripyat some more and It took me a long time to finally beat the game. If I start a new playthrough, I I'd try Recon out

Edited by: MaDBuG

Savegame from 2.1 is compatible with 2.1.1, but some bug fixes only work with new game (not so important ones). Also some users reported that previosly upgraded weapons could be upgraded again with different upgrades. It will not couse CTD, but if you upgrade such weapon it could be unbalanced.

If you reached freeplay, yes maybe it is better for you to keep playing 2.1 for a while, but if you got frequent CTD due to high mutant/npc spawn rate you should try latest version.

--

kcs123 wrote: previosly upgraded weapons could be upgraded again with different upgrades.

What do you mean exactly? Like for example, a fully upgraded SVU sniper had some upgrade paths choosing between fire rate or accuracy. Does that mean you can pick both upgrade paths now? If thats the only problem I can just ignore that. lol.

Actually upgrading would be a good thing if I can keep a playthrough. It might fix the Load level CTD, plus the other fixes and features are nice.
But do you think If I upgrade to 2.1.1 and somehow my game gets buggered doing that, can I just reinstall 2.1 over 2.1.1 and go back to a previous old 2.1 save?

Can't say exactly what upgrades, I didn't come across with such bug, but lopezien (I think), or some other user mentioned it for Nimble's SVU sniper.

Make backup of your 2.1 save, so if it gets bugged at some point, you can reinstall older 2.1 all in one version over 2.1.1. Only if you use patch version of 2.1 you can have more problems.

Bugs that could not be solved without starting new game is CTD when you pick up bugged cards in stash, for example. But those are not gamebreaking bugs, so you can continue your old save if you like it more.

Edited by: kcs123

--

Thanks for the Info! I'll try it out.