Game constantly locking up Thread - MISERY mod for S.T.A.L.K.E.R.: Call of Pripyat

So. I have Misery 2.1.1 with Les Miserables installed. I've been playing it for a while and just now reached Stingray 5. Prior to this point, the game was running pretty smooth with DX10, except for a few occasional stutters here and there.

Basically, what happened was that I started getting overwhelmed with bloodsuckers and they were soaking up a lot of damage - I thought to myself, you know what? that's not fair, and decided to change their health so that they die quicker.

I went into m_bloodsucker.ltx and changed HealthValue from 200 to 100, and option for ALife SimulatorHealth from 265 to 100. Seemed to do the trick - the bloodsuckers still put up a fight, but they went down with a buckshot or two.

Then came the problems. The game started crashing every 5 minutes or so, and 3/4ths of the time it would automatically crash if I entered the menu.

I went on like this for an hour before I decided to change the values back to their original selves. It didn't appear to fix the issue.

Then I went further and got the original m_bloodsucker.ltx file from Les Miserables and replaced the de-modified file I had with it. Didn't fix the crashes.

Finally, I thought to myself, maybe my save files are broken and I need to go back a few. So with the original file in place, I loaded up a save that I made long before I tried modifying the bloodsucker file. Same problems.

Now - even though the problems started after I messed with the files, they persisted even when I reverted to the original files and a save before I made that change, so I'm convinced that this issue is not because of the edit that I made.

IMHO those crashes are caused by something else. Would you mind posting here the end of your crash logs?

Edited by: Caffeine_Zombie

Caffeine_Zombie wrote: IMHO those crashes are caused by something else. Would you mind posting here the end of your crash logs?

I'm not getting any, unfortunately. The game freezes, I alt tab out and I simply get the message that the game stopped working. I'm not getting that usual xray crash log thingy.

EDIT: Actually, scratch that - I just didn't click that more details button.
Anyways, here's the log:

Problem Event Name: APPCRASH Application Name: xrEngine.exe Application Version: 1.6.0.2 Application Timestamp: 4b275197 Fault Module Name: d3d11.dll Fault Module Version: 6.2.9200.16570 Fault Module Timestamp: 5153774d Exception Code: c0000005 Exception Offset: 000a7904 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: c3fd Additional Information 2: c3fd62fe81b1c65e85762970c6680588 Additional Information 3: 1f5f Additional Information 4: 1f5f1e03b5fc58187a34bb38d618b63d

d3d11.dll, huh? appears to be a graphics-related problem, then

EDIT 2: Fixed it.
In my OP, I completely failed to mention that I went from dx11 to dx10 right before I got to Stingray 5, and apparently, STALKER CoP REALLY hates dx10, so you should either play with dx11 or dx9. Found this out after searching what CoP has to do with d3d11.dll.

Edited by: Lolpingu

Well, that sounds strange. I'm not as good in divining as other guys here, so you'd better wait for them to tell something.
The only thing I've heard about savegames corruption is related to auto/quick save problems.
My game crashes without logs when I headshot something too hard for game engine to sustain.

Isn't that .dll related to DX11? If so, you can try downgrading to 10.

Edited by: Caffeine_Zombie

Caffeine_Zombie wrote: Well, that sounds strange. I'm not as good in divining as other guys here, so you'd better wait for them to tell something.
The only thing I've heard about savegames corruption is related to auto/quick save problems.
My game crashes without logs when I headshot something too hard for game engine to sustain.

Isn't that .dll related to DX11? If so, you can try downgrading to 10.

It's fixed. Ironically, it appears to be related to dx10, as turning dx10 off seemed to remedy this issue.

The game does hate DX10. Static lighting or DX11 will give the least problems. The crash logs someone needs to see are in the _appdata_/logs directory. Only the part after "Fatal Error" is generally beneficial. The bug trap stuff doesn't help. Deleting user.ltx is very helpful when changing video settings. They are not always properly applied otherwise. I can't speak to any compatibility problems with les Misrables. A tip when editing files, use notepad++ they are much easier to read and edit. Put your new value right before the original followed by a ;. Everything after the semi-colon is ignored. You can then see what the original values were and revert at will without having to remember everything. Notepad++ also can remain open and keep a tab open for each file you edit so switching back is super easy and you also don't have to find files over and over.

@ CaffeineZombie Sometimes if you get carried away bumping hit power the game engine can't handle the ragdoll physics. Hit Impulse needs to generally stay below 75. I had the same problem when I tweaked weapons so I could see the bodies fly ... sometimes it causes CTD's.

What does this one mean

FATAL ERROR

[error]Expression : error handler is invoked!
[error]Function : handler_base
[error]File : D:\prog_repository\sources\trunk\xrCore\xrDebugNew.cpp
[error]Line : 764
[error]Description : application is aborting

Does it repeat? What are the circumstances under which it happens? Are you using any add-ons besides Misery mod?

Edited by: jasper34

Vyrkonik wrote:

What does this one mean

FATAL ERROR

[error]Expression : error handler is invoked!
[error]Function : handler_base
[error]File : D:\prog_repository\sources\trunk\xrCore\xrDebugNew.cpp
[error]Line : 764
[error]Description : application is aborting

Find or fix what causes this type of crash?

Because the causes of CTD's can be quite varied, I always need to ask a few questions to eliminate simple things. Hardware specs (Memory, CPU and GPU), verify proper installation, verify no other mods are installed. Sometimes all that is wrong is the Video Config needs some adjusting. Unfortunately that error log doesn't reveal anything specific. With the above details we should be able to quickly narrow down the problem and get you Stalking