I didn't make it!
I played the game the whole way through the first time and had no bugs.
The second time I had no issues until I had gotten to the Pripyat section. I actually went mostly through it and left to get more med kits/bandages.
When I returned the game began to crash. I tried going back a bit and starting the game a bit before Pripyat but seemed to have issues when I finally got to Pripyat.
The error says:
Any ideas? I downloaded the latest three official patches and other then some second delays when the graphics were on the high end, well, as I said, no problems the first time playing it through.
Here are the stats for my computer and it's Vista, business edition:
Operating System: Windows Vista™ Business (6.0, Build 6000) (6000.vista_gdr.071009-1548) Language: English (Regional Setting: English) System Manufacturer: Dell Inc. System Model: Dell DXC061 BIOS: Phoenix ROM BIOS PLUS Version 1.10 2.3.2 Processor: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz (2 CPUs), ~1.9GHz Memory: 2046MB RAM Page File: 1942MB used, 2365MB available Windows Dir: C:Windows DirectX Version: DirectX 10 DX Setup Parameters: Not found DxDiag Version: 6.00.6000.16386 32bit Unicode
--------------- Display Devices --------------- Card name: 256MB ATI Radeon X1300PRO Manufacturer: ATI Technologies Inc. Chip type: Radeon X1300/X1550 Series (0x7183) DAC type: Internal DAC(400MHz) Device Key: EnumPCIVEN_1002&DEV_7183&SUBSYS_0D021028&REV_00 Display Memory: 1018 MB Dedicated Memory: 255 MB Shared Memory: 763 MB Current Mode: 1024 x 768 (32 bit) (75Hz) Monitor: Generic PnP Monitor
Stalker has a lot of Issues with Vista. Go to your Stalker Directory C:/Program Files/THQ/Stalker Make sure there are no Folders named Gamedata,If there is.Delete it. What Patch Version are you running?
Find your log file inside that zip file, [COLOR=Sienna]bishop026[/COLOR]. Or find it in the appropriate user directory. For SoC (I assume that's the game you are playing), it is in %ALLUSERSPROFILE%\Documents\STALKER-SHOC\logs\ and it is called xray_.log, so it might be xray_sam.log if you log in as "sam".
At the end of that file is some information on the crash. Usually it is in the form of a few lines starting with [error]. Post those lines and a couple of lines before and/or any "stack trace" information that appears.
You can also see the crash info right after the game CTDs, by opening up a text editor and pressing ctrl-V.
There is a problem with the vanilla game -- even the patched versions -- in that it has an error on top of an error and it reports the second -- and useless -- error instead, referencing _g.script and claiming a nil second argument to format().
You can fix this by using bardak's bug fix attempt for patch 1.0003, or for later patches use the Zone Reclamation Project (ZRP). In that case, the ZRP 1.05 test version is recommended. You do not need to start a new game with either bug-fix mod.
In many cases, these bug-fix mods also correct the original problem. The ZRP has a feature that permits you to get around any show-stopping bugs by restarting the game, then selecting a chapter in the storyline (e.g., Pripyat) to resume play from that point of progress. See the docs.