Support

KNOWN ISSUES

Here stating whatever issues that we are already aware of
and this will be updated frequently based on feedback.

Version 2.0.1 should be much more stable in save-corruptions and random, no-log ctds
- one of the things that were done was disabling of faulty mechanic repair scripts
(they were supposed to make mechanic repairs delayed). Please use included
‘old saves compatibility patch to restore previous settings at the cost of still
having risk of those issues)

However other instances can still be present, so please:
* Do numerous hard saves and loading them after each save to check wheter there
was no corruption – this way only small portion of gameplay needs to be reverted

* In case of save corruption – reverting to last working save, it is very unlikely
that random save corruption will re-appear any time soon as it is very rare

ISSUE 1:
Some people are experiencing Render3 crashes.
See the latest info about this issue in the FAQ (performance).

ISSUE 2:
Crash when Tuna is giving ‘Twisted’ artifact to Beard

ISSUE 3:
Batteries which are taken out of UPD on recharging sometimes have lower
power than the energy which was in the UPD prior to their removal

IMPORTANT:

In case of repeatable random crash (for ex. when level switching) or savegame corruption please always try following procedure:
1. go to configs\alife.ltx
2. change value of ‘switch_distance’ param to 10
3. go into the game / try to load save
4. if game starts leave it by itself for few minutes
5. make a new hard save and exit the game
6. again go to configs\alife.ltx and change s_d back to 300
7. load your new hard save

It is not guaranteed that above method will always work but there is a significant
chance that crash loop will be broken thru it. Point of above procedure is that
on low s_d entire a-life is in off-line mode and thus is able to ‘reset’ itself,
clearing whatever circumstances were causing the immediate crash.
It has also been reported that once corrupted saves were able to be loaded again on lower s_d.

Version 2.0.2 should be much more stable in save-corruptions and random, no-log ctds.
One of the things that were done was disabling of faulty mechanic repair scripts
(they were supposed to make mechanic repairs delayed). Please use included
‘old saves compatibility patch to restore previous settings at the cost of still
having risk of those issues)

HAVING TROUBLE SWITCHING BETWEEN USS CLASSES?

Make sure that you start the game “as administrator” at all times.
Also, anti-virus software has to be disabled as well as everything
else that can cause script-induced changes to files
(which is normally done by mallware). And don’t worry, MISERY
will not do any harm to your system or software.

BUGS & CRASHES

If you experience a CTD (Crash To Desktop) with a Crash log saying:
“Not enough storage is available to process this command”.
Then you will need to either turn off background music or turn your graphical settings down
as this crash is caused by the mod using too much of your system memory (RAM).
Maybe you will even have to do both to avoid the problem.

FREQUENT CRASHING

Some people are having continuous crashes and no X-Ray error in the log,
and even crashed while I was in the video menu. Read this:

Okay I believe this issue is not related to Misery. Your crashes might
be a problem with a windows update. “Update for Microsoft Windows (KB2670838)”
has been causing dx10 issues in a LOT of games. In fact if you just google
“stalker dx10″ the first result will be a thread detailing the problem.
I first had this issue trying to play Clear Sky in dx10 and deleted the update then,
but I had the problem again when installing CoP a few days ago to get ready for Misery 2.0.
I saw that windows had reinstalled the update again! A quick way to test if this
really is your problem is to download a program called fraps if you don’t already have it.
(or use any program with the same function) Fraps is supposed to show you your framerate
at all times in the corner of the screen while playing a game. If fraps does NOT show up
in the corner in dx10 mode, but it does in other modes and other games, then you know
its the windows update that is your problem.”

Here is how you get rid of it:
“If you go to Control Panel > Windows Update > then click Installed
updates on the bottom left. Sort the updates by name then search for this update.
Right click and uninstall it and then restart your computer and your problem will
be fixed. Don’t worry its only an optional update anyway. Uninstalling it won’t break
anything on your computer. If you ever have more dx10 issues in the future remember
to check if windows didn’t ninja reinstall the update.

Finally, utilizing directx 11 mode seemed to to good things in this regard.
CREDIT FOR THE TIP: TheSmokeyBloke

SUFFERING FROM CONSTANT STUTTER?

This topic and issue seems to very different from one rig to another.
If you suffer from such stutter and low FPS that your game is rendered unplayable,
please refer to STIIVAIS’ MISC ADJUSTMENTS FOR MISERY 2.0
which is an unofficial editing of the mod data. It contains a
“Low-resolution Texture Package” that seems to help some people.
Although MDT does not support your manual editing of unofficial data we are
interested in knowing if this installation did help you at all.

Please send us the result of this attempt at contact@miserymod.com
and you will be contributing to MDT development research.

EDITING/MERGING MOD DATA

MISERY is not directly compatible with any other mod.

Your adding of another mod might overwrite basic gamedata files…
- but I might have scripted the mod to use alternative files in many cases
- which leaves you with an unwanted result of merging or even constant crashes or bugs.
Merging, altering and/or editing of this mod data is at own risk and will not be commented
or supported on the mod profile by me.

TECHNICAL SUPPORT

Mods do not work with multiplayer.

It’s the “Crash Logs” that tells us what seems to have caused a crash to desktop.
If you are using windows XP you will find your crash log here:
C:\Users\Public\Documents\S.T.A.L.K.E.R. – Call of Pripyat\logs
Only the last part of the text file after “FATAL ERROR” is relevant.

STEAM COMPATIBILITY

MISERY is fully compatible with the Steam version of S.T.A.L.K.E.R. Call of Pripyat.