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 | ||
---|---|---|
Crashing when I save | Locked | |
Thread Options | ||
Oct 17 2017 Anchor | ||
Every time I try and save it crashes. With both quicksave and hardsave. I have done the fix for 2.1 and am Not sure that might be the problem? |
||
|
Oct 17 2017 Anchor | |
|
||
Oct 17 2017 Anchor | ||
How do i check the logs? I am playing 2.2 and using a hardsave fix I saw in a 2.1.1 thread that helps make quicksaves less corrupting gamey |
||
|
Oct 17 2017 Anchor | |
Read the link in my post |
||
Oct 17 2017 Anchor | ||
So in my logs folder I have a text file with nothing in it and a Mdmp file? |
||
|
Oct 17 2017 Anchor | |
So, you got an empty log crash. You can load your last save and play it, but not save it? If so, try lowering your alife.ltx switch distance 100m. See if you can load and then save. If that doesn't work, try another 100m less. If you can get it to save, exit, and upload your entire log file. We can check it for any signs of corruption. |
||
Oct 18 2017 Anchor | ||
How would I upload my log file? And lower the alife distance |
||
|
Oct 18 2017 Anchor | |
You can use a free file hosting service like dropbox which has plenty of room in the free version to post logs and save files. Edit configs/alife.ltx with notepad or notepad++ and change the line that says switch_distance = ### which is probably 300 followed by a semicolon and several other numbers. Change the first number right of the equals sign to a lower number. Save the file. be sure NOT to change the file type from .ltx to.txt or xray won't recognize it. |
||
Oct 18 2017 Anchor | ||
So editing my alife distance down 100 meters worked. Anyways what does it do when lowered? |
||
|
Oct 18 2017 Anchor | |
The switch_distance is a radius around the actor in which alife or more simply life is active and drawn on the map. Outside that radius, their activity is simulated in memory only. The vanilla switch distance was 150m or less. At the default of 300m, there is 4x as much active life and 4x as much being drawn. Combining that with much more life per 1000 square meters and the fact that many mutants are actively agitated so they will react to being shot at and it's a considerably higher workload for a PC. I don't think I got your system specs, but lower CPU core speeds, having less than 8GB of system RAM, or to a lesser degree a slower GPU can have large impact on how well the game behaves for you. Rename your log to anything else, and the game will make a new one. If you get set up with a service so you can upload the log, looking at it may help show if anything else is going on. You can try playing a little while at 100m and then gradually increase it 50m at a time and see if your problems stay away. You will definitely have smoother play at lower switch_distances if your system was being pushed a little too hard. Stutter improves to some degree with higher switch distances, but it can introduce other problems. The camouflage system will scale according to your switch distance, so while you can see enemies further at 300m distance, they can also see you better. |
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.