S.T.A.L.K.E.R.: Call of Pripyat

S.T.A.L.K.E.R.: Call of Pripyat

How to fix this error?
Game crashes when I try to begin the expedition to Jupiter Underground, and then I can't load any of my saves w/o my game crashing. Checked the logs and this was the error. I'm also being bland and playing without mods. I've tried uninstalling/reinstalling, disabling steam overlay, and verifying cache.


FATAL ERROR

[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 : ...lker call of pripyat\gamedata\scripts\xr_meet.script:630: attempt to index local 'meet' (a nil value)
< >
Showing 1-2 of 2 comments
Pete Mar 14, 2020 @ 11:04am 
Since this is one of the top results in google, when googling the error, I'll leave the solution here, cause it's not trivial and it took me way too much time to find it.

You need to lower your graphic settings to minimal.

Then turn off the game and edit alife.ltx file - change switch_distance to 20.

optional: If you don't have alife.ltx, file, which you probably don't, you need to unpack the .db files in resources folder, with the unpacker or find the alife.ltx file online. If you chose the former, which I did, just google "stalker unpack .db". Unpack the archives, find the file and put it in gamedata/configs folder and edit as mentioned.

Now try to load the last working save (or save that was crashing). Save the game again. Get out of the game, restore switch_distance to 150, turn on the game again and turn back graphics settings to what you had before.

It's a clusterf... I had the same problem years ago and it made me drop the game. But this time I was too invested in it and had to find the solution to this bug :steammocking:
Last edited by Pete; Aug 27, 2023 @ 11:31am
lvcfr Aug 17, 2023 @ 12:31am 
Originally posted by Pete:
Since this is one of the top results in google, when googling the error, I'll leave the solution here, cause it's not trivial and it took me way too much time to find it.

You need to lower your graphic settings to minimal.

Then turn off the game and edit alife.ltx file - change switch_distance to 20.

If you don't have alife.ltx, file, which you probably don't, you need to unpack the .db files in resources folder, with the unpacker or find the alife.ltx file online. If you chose the former, which I did, just google "stalker unpack .db". Unpack the archives, find the file and put it in gamedata/configs folder.

Now try to load the last working save (or save that was crashing). Save the game again. Get out of the game, restore switch_distance to 150, turn on the game again and turn back graphics settings to what you had before.

It's a clusterf... I had the same problem years ago and it made me drop the game. But this time I was too invested in it and had to find the solution to this bug :steammocking:
thx man... if you hadn't mentioned the gamedata/config path, i would never have dealt with this problem. i had an identical situation. at first i decided not to do anything, but a few days ago I wanted to play cop so much. so these days i've been reading various forums, but i haven't found an answer... thanks to you i realized i don't have gamedata folder. then i remembered that before the game started crashing, i moved it to another drive. i decided to open steamapps folder on the disk where the game was installed before. and i found the gamedata folder there... despite the fact that i deleted the game from the previous disk through steam itself, and on the new disk i already checked the integrity of the files several times. i tried a million different ways, but it turned out i just needed to transfer the gamedata folder to the game folder on the new drive. thanks again, without you idk how much more i would've suffered with this game... :Heartyou:
< >
Showing 1-2 of 2 comments
Per page: 1530 50

Date Posted: Jan 1, 2018 @ 9:30am
Posts: 2