I give up on MISERY Thread - MISERY mod for S.T.A.L.K.E.R.: Call of Pripyat

After watching gameplay on youtube and thinking to myself the gunplay and atmosphere looked outstanding, I earnestly went through 3 reinstalls of both CoP and MISERY itself to try out this seemingly amazing mod.

I could not play for more than 5 minutes on a medium-high end PC (i7 CPU, Radeon 7870 OC) without running into a Crash. The framerate was widly fluctuating between 130 fps and 40 fps (!) on open areas. I settled on medium-low settings to try to lessen the load and prevent crashes. Even that was not enough.

Ultimately, after 2 days of wasting my time tinkering with the game just to get it to run with some sort of stability, I have reached a point where, after crashing for the Nth time, the game won't even launch. Running the shortcuts and/or .exe files of the game do absolutely nothing (there is even no indication of the xrengine.exe process running in the task manager).

Keep in mind I played and finished Call of Pripyat (with the starter pack mod compilation, which I was privy to remove before installing MISERY) before with no problems. All my troubles started ever since installing MISERY.

I have never gone through so much work and experienced so much trouble just to arrive at my wit's end with no solution. I am angry and frustrated. Forgive me if this post comes through as a bit agressive but some of this frustration will inevitably seep into the writing.

I'm aware that the devs of the mod are doing this for free and receiving no compensation, but you should make sure your work is ready and functioning before you make it available to others. I'm not expecting everything to work perfectly, far from it; but this level of instability is outrageous.

I sincerely hope that MISERY 2.0 has a higher sucess rate. Maybe I will even play and enjoy it. As it stands now, I can't and won't waste any more of my time with it.

Edited by: Tonycaveman

well, ive played through 75 % of the game and even installed some of my own mini mods on top and didnt experience a single crash that wasnt somehow my fault so i am pretty sure you did something wrong.

Edited by: RagingRapscallion

You should check to see if any logs were produced, these logs can be found under \Users\Public\Documents\STALKER COP(or something like that),the latest error log, called xray_.log* is in the logs\ subdirectory. At the end of that file is usually a section that starts with "FATAL ERROR" and has lines beginning with "[error]". Include those lines in your post to give an idea of what is wrong.

There's a checklist of things that could've caused this. It's likely MISERY 2.0 won't change the behaviour of your PC because in the end, all we're doing is adding in new lines of script here and there (it's ofc. way more complicated, but one could interpret it like this)

Did you:

• Update your drivers to the newest ones?
• Overclock your CPU/GPU? If yes, are they inline with your memory CL settings?
• Left your Catalist settings on a weird configuration? *Nvidia Control center sometimes does this as well. It can cause heavy stuttering because of the custom profiles it enables which force maximum FSAA, AFx16, Forced Motion Blur etc.
• Clean your registry? *Cleaning your registry allows windows to perform way quicker, CCleaner is adviced
• Patched the game to 1.6.02?
• Buy the game? If yes, CD or steam? *Pirated versions of any game most likely suffer from mods as the .exe's aren't always stable enough to even support modding. It's always adviced, especially with big mods like misery, to spend those 5$ for a great game and great mod, imho.
• Shared / looked at your Crash Log? (hover over link with your mouse)

Tony wrote: I'm aware that the devs of the mod are doing this for free and receiving no compensation, but you should make sure your work is ready and functioning before you make it available to others. I'm not expecting everything to work perfectly, far from it; but this level of instability is outrageous.

Do mind that the problem is probably on your end of the spectrum. Most of the users have done several play-throughs without any problems. STALKER is known for it's weird behaviour on some PC's. If I could have your PC specs, that'd might clear some things up.

Edited by: Lоnerboner

I hope that 2.0 will make either add back the ability to see allies on minimap, or remove grenades from the three military guys in the Unidentified Weapon mission.

It was annoying enough in vanilla when they kept commiting suicide, but it's downright nightmarish in Misery.

SquigPie wrote: I hope that 2.0 will make either add back the ability to see allies on minimap, or remove grenades from the three military guys in the Unidentified Weapon mission.

It was annoying enough in vanilla when they kept commiting suicide, but it's downright nightmarish in Misery.

The ability to see allies in the mini map hasn't been removed in Misery 1.

Edited by: Astyr

I have to say I encountered nearly the same problems. Stuttering in CoP have always been a problem but it has reached a new level with Misery 2.0.
In two days playing the game I've experienced nearly 5 xrengine crash and there are some areas where the game freeze for several seconds every meter even if I have more than 60 fps.
My PC : Phenom II x4 965 3.4 Ghz
Radeon HD 7870
8 Go DDR3
Catalyst 13.4
Windows 7 64 bits
No problems running 3D mark or Furmark
I will send a log as soon as possible. (ie when I encounter a crash again).
Thank you in advance for your help.

Been running it great on near max settings with 3gb RAM. First, if you're using a 32bit system enable the 3gb switch, it helps. Also, disable all processes that aren't necessary. Even vanilla CoP was bitchy about most other programs. Also, bad sound drivers also used to be a common crash cause afaik.

Also, theres a mod out there that disables prefetching. I've been using it with misery 2.0 and it reduces stuttering by a lot.

Crashed two times since release, hardly bad for an unpatched mod of this scale.

Edited by: usersd

[error]Expression : !m_error_code
[error]Function : raii_guard::~raii_guard
[error]File : D:\prog_repository\sources\trunk\xrServerEntities\script_storage.cpp
[error]Line : 748
[error]Description : ...f pripyat\gamedata\scripts\inventory_upgrades.script:412: attempt to perform arithmetic on a nil value

Found this one when crashing while doing repair/upgrades at Cardan (Black Road start/USS Sniper)
I5-3570K @4.2GHz
Asus DCII GTX580
Win7Pro64Bit
8GB Ram

usersd wrote: Been running it great on near max settings with 3gb RAM. First, if you're using a 32bit system enable the 3gb switch, it helps. Also, disable all processes that aren't necessary. Even vanilla CoP was bitchy about most other programs. Also, bad sound drivers also used to be a common crash cause afaik.

Also, theres a mod out there that disables prefetching. I've been using it with misery 2.0 and it reduces stuttering by a lot.

Crashed two times since release, hardly bad for an unpatched mod of this scale.

Already tried this. No results.

Well, looks like I'm done with Misery 2.0 now too. It was great for the two hours I got to play it.

The zone gives, and takes.

Made something that lowers the lag by decreasing AI distance:
Moddb.com
A low resolution package in the works ATM...

Mygame is runnin on Static Lighting (not by choice) as it crashes on any other setting, but most stuff is on the highest I get random lag at some times, so I close everything else than the game.

Also 40 FPS is bad...? My game run at 60..40 FPS , And I'm happy with that.. After all, 40 FPS is barely lag, 30 FPS is when lag begins to hit hard.

A crash usually has a cause and you'd have to check you crash log (not the error report) for what reason there is. Only that way you can determine if your crashes are memory related, or caused by a mesh, pseudo giant or maybe a stuck zombie.

DX11 works very poorly with stalker, you better of using 9 or 10. Also important is how high is your alife setting when it comes to fps.