Full concept MODIFICATION of S.T.A.L.K.E.R. Call of Pripyat that touches every game aspect including textures, sfx, music, weapons, A.I., items, weather, mutants, difficulty and much much more!
Posts | ||
---|---|---|
constant crashes when loading saved games (not quick saves) | Locked | |
Thread Options | ||
Jan 16 2018 Anchor | ||
im finishing in Jupiter and its happening so often now that the game is unplayable
anyone have any ideas? ive tried lowering my settings to medium and deleting most of my old saves its completely broken, about 50% of my saves get corrupted now. im having to replay huge portions of the game, most recently the bandit ransom - it autosaves after you pay them, then when i want to load back (because when you leave I roll a "give me you all your stuff" tax from the second bandit) it crashes of course... Edited by: ceran5 |
||
Jan 16 2018 Anchor | ||
At the Jupiter plant? Zombies without weapons can cause crashes when the game loads. Try lowering switch distance to 30 metres, loading, and then if successful, move away and save again, then set your switch distance back |
||
Jan 16 2018 Anchor | ||
near the container warehouse , outside the train station, it doesn't matter . the most recent save i make is always corrupted now |
||
|
Jan 16 2018 Anchor | |
I've played at least 4500 hours of 2.2, and never had problems like that. I suggest backing up your saves and doing a fresh installation following these directions: Dropbox.com I'll quote myself from the front page "Controllers, psy beasts and zombies DO NOT CORRUPT SAVES. If you are unable to load a save by lowering your switch distance to 20 or 30, loading save, and saving again, then restoring your switch_distance, post a link to your full log and we can verify if you have an otherwise corrupted save. Saving within switch_distance of alerted zombies can make your save not load, but it is not corrupted. the above work-around works EVERY time." |
||
Jan 16 2018 Anchor | ||
thanks a lot it worked! although i got another crash after another hour and a half of play, at least I know a workaround now.. thx again |
||
|
Jan 17 2018 Anchor | |
The real workaround is not to save without finishing off nearby alerted zombies. |
||
Jan 17 2018 Anchor | ||
hmm it stopped working - the latest crash i mentioned was near the parking lot anomaly in Jupiter, changing the switch distance to 10 or 15 still results in a crash, including a previous save at the Mobile Lab. The save before that (at the train station) works even with my default 300 switch distance. I might have seen some zombies in between the train station and the other saves but are you sure they're the problem? a few days ago I was in the middle of the Jupiter plant, literally saving with several zombies chasing me, and the games loaded fine |
||
|
Jan 17 2018 Anchor | |
The scan(f) crash is quite unique. Is that what is in your log? |
||
Jan 17 2018 Anchor | ||
|
Jan 17 2018 Anchor | |
Scan(f) is related to zombies, if that IS NOT what you have, it is something else, post your log. That fix is for the zombies, not a 'fix all'. |
||
Jan 17 2018 Anchor | ||
|
||
|
Jan 17 2018 Anchor | |
scanf() is only related to zombies. The case you found is from years ago, not 2.2. The only fix remains the same reduce your switch-distance, kill any zombies within your radius, save, restore your switch_distance, and resume. |
Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.