Congratulations big time,
fiznerpin1962 :-bd You've got that damn chopper!
Particularly this one, and the additional "repercussions" (for stealing army box) events chopper in Cordon both fly high, so scoring on them is very difficult.
Pictures duly logged.
Grump642Some things seems to have changed in your files, as it's definitely not the decoder icon.
Mod files are correct. Just checked again.
This is, as you point out, snork-leg on file: monster_items pointing to icon_equipment: x=14 y=19
decoder, on the other hand, is in quest_items x=11 y=3
Both items pointing correct locations in the mod. I suggest the best and the easiest way is to reinstall the mod, or you can correct the changed file manually if you wish.
If you've enterd the room26 in Pripyat and took the decoder into your inventory then its there, no matter the icon files got haywire, in fact, you can still enter the lab even if you don't get the decoder.
KaidonniWhat you got over there is the engine problem Xray momentarily couldn't handle the particle process; it's so evident that the crash did not repeat on your reload. You will always have problem on and off
due to sudden engine glitches, it's the way the engine works, it's prone to it. Reloads will work fine.
Please do not change anything in script files comparing the symptoms with what you'd seen in ABC. Just reload, engine this time works fine. Keep your PC temps cools, stop all unnecessary processes. Rebooting your PC before starting the game helps with RAMs.
Horror-Times and Blowouts throw different skies it's not one set only. Sometimes you'll get rather washed out bright colours, sometimes very dark and moody ones, or between. You'll find one that you like along the way. We all find one.
EggChen Yeah, anytime you can start sending the awards, no hurry there.
You must be right to point to 64 bit as the cause there I believe, Quad-Core and 64 bit must be a double kick for stalker. That's bed, because I'm planning to go 64 bit soon, as this rig is OK with 64 as it is.
I believe you're using latest drivers of course. You say that it plays perfect for a few hours then it starts developing problems. Maybe we can explore some other matters as well, alongside that obvious Quad and possible 64 bit issues. I'm just guessing here of course, but have you monitored your Graphics Cards temperature, or, in fact, the CPU as well. Btw, while talking about temps, I'd like to remind you the RAMs, too. STALKER suffers some memory leak problem as well; maybe the problem accumulates over a certain period of time. I know, it's hell of a problem to do so, but have you tried rebooting your PC, a bit before the time that you've seen when the game starts developing problems? If it's a memory management problem, it should then help it. Guesses, guesses.
But, anyway, thanks for trying buddy, at least we've got a couple of good pictures from you, too.
) On my way to DV now... that damn chopper is back, and me with no heavy hitter to take the fkn thing out. ](./images/smilies/eusa_wall.gif "Brick wall")
, done a few laps around pirpyat before heading out and no CTD's due to pathing problems 
, theres no free ride in extreme mode thats for sure 
I did down my first chopper in DV though - found an RPG with one round left.... this is awesome! 
If you want anyone to survive.
