I've been creating a mod of OL2.2 with 1.005 that seems to be causing a problem when loading the Pripyat level. The level will load just fine the first time I enter Pripyat and all the scripted sequences are yet to occur (Veterans/followers, Monolith - ambush troops etc.) however when I return to Pripyat at a later stage when the game starts to load varied mutants and stalkers the game will CTD during the Pripyat load screen when the 'client is synchronising'. The same problem will occur if I load the level, die and then try to reload. the log states the following - * MEMORY USAGE: 367291 K stack trace: 001B:02F955E1 xrGame.dll Has anyone else had a similar problem or know of a fix? The mod is just about ready to release, but with this 'show stopper' / CTD bug there is no point.... Edit. - upon causing the error again I wrote down the following info - EAX=34067024 EBX=371884B0 ECX=00000063 EDX=344B0700 ESI=34067024 EDI=32FD9EB0 FLG=00210206 EBP=34067020 ESP=0032D478 EIP=02F955E1 CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=00 System Error: ----------------------------------------- 0x00000012 - There are no more files. Does anyone know what 'CS= ' and 'EIP= ' are in reference to?
Anyways, since both those threads are massive by now and overloaded with posts, I'll give you the run down: This is a generic error that is being worked on for OL3.0. It happens when you don't have the game disc in your disc drive. So, rather than use a no CD crack, either pop the game disc into your disc drive, or copy it so you can set it up via a virtual drive which the game can read from.
If you are using an illegally obtained version of the game, then suffer. That's the only help you will get for that. It's even stated in the rules here to not bother asking for help if you're not using a legal version as they're known to have issues.
What I do rather than putting the game disc in or copying it is just save rather constantly while in Pripyat. Like, every time I go a distance comparable to half of 1 of the apartment buildings there. And don't use quick save... The game HATES quick save for whatever arsed reason.
If you start getting CTD's immediately after you load, then either go from the auto save when you first entered Pripyat (annoying to make all that distance again, but necessary), or a save file from before that. (It's best to have a save file from right before you went through the portal to Pripyat, the auto save of when you were in the portal, and a save file for any time you're IN Pripyat.) Also: Avoid loading ANY game/save while in Pripyat... If you have to do that, then close SoC and load it up again from "scratch."
Valid retail disc is located in my DVD drive along with the retail .exe file and although I am aware that reloading a previous save game or simply loading the game again can temporarily rectify the issue, I'd rather resolve the bug for good. I don't recall having this error while running an unmodified version of OL2.2, but I have no way of isolating the error with any changes I've made due to the lack of specific information in the crash log text. Unless I start from scratch and add the many changes I've made one at a time to try and find what is the cause. The problem with that is the fact that I doubt I'd have enough time to do it thoroughly.
Now you say "This is a generic error that is being worked on for OL3.0", so in that case, do you have any more specific info as to how that is being conducted?
No, because I'm not a member of that mod team. I'm not a member of any mod team, tbh. :p I can only say what Kanyhalos has already posted in the OL thread when I (and others) brought up the issue. But, if you're getting it without a "no CD crack," then you're the first I have ever heard of such. If you are, however, using a no CD crack, then don't. Take it off/out.
The only advice I can give is to do what you suggested: Go through and add each modified part 1 at a time. It should be common sense to try that first before asking for help... As there are people out there who will tell you to do that before they offer any suggestions.
Regardless, I don't know enough, and never intended to sound like I do. Guess I've been lucky that what modifications I have done have not made OL2.2 behave any way outside of how it did when I first installed it unmodified. Too bad Kanyhalos also outright states he won't support modified versions of OL... (Forgot that part in my last post.) But it doesn't hurt to post in the appropriate thread(s). People tend to check those more often than they come here. And it's not against the rules or whatever to post in there.
Yes, on the basis that it is not a OL2.2 specific error I haven't bothered Kanyhalos with it and he is working on OL3 afterall. As for posting in one section or another, it seems it does not matter where/how I post a question about my mod, as soon as I say 'modified version of OL2.2', someone always seems to respond that I should post it elsewhere.... Anyway, I did make the post in case someone was already aware of a quick fix, that could save me a hell of a lot of time, because now I'll have to add a small section of modifications, start a new game to ensure the changes take affect, try and rush to Pripyat and then wait and see if the error will occur, adnauseum. Time not being a luxury for me at this point.
if you check the log and you see the xr_kamp script in the log description then:
its an xr_kamp.script bug which could be fixed. it has nothing to do with nocd or nodvd fixes, it was discussed to death on gsc forums many times... :)
actually, not the file change helps, but the quit and save reload... an experienced scripter could backtrace the error and fix the bug.
Thanks dezodor. I am aware of the xr_kamp script error, but that is not the problem that I am experiencing and although I know people think one thing first when they see the words Pripyat and CTD together, I can assure you I am using a retail disc and retail .exe. From what I have read on Metacognix - Crashes in the STALKER-SoC Game, I am guessing it has as much to do with memory allocation as anything else. On the basis that comparing the log file of OL2.2 and my mod when the Pripyat level is succesfully loaded shows a greater use of memory for my mod. Which is not surprising due to the extra weapon resources that I've set to be in use, if nothing else for eg. Obviously the Pripyat level is a resource intensive level to begin with, so I'll have to try and reduce the amount of data used to see if that has a beneficial effect.
you can try to reduce respawn rates or the amount of already spawned mutties, maybe it will help. :)
Yeah, I've already limited the amount of weaponry that is listed in the ' character_desc_pripyat.xml ' file, but that won't be of much benefit once the ' character_desc_simulation.xml ' NPC's come into play enmasse. So I've also limited the type of mutants listed in the level and the amount of items that are listed in the Pripyat all.spawn .ltx.
Now I'm going through as many .ltx files as I can and deleting redundant data such as the coding comments, unused variables and any other extraneous data.... fun times....
Well, I'm glad that there's an actual answer, instead of my crappy, limited one. Which I am glad there is an actual answer. Should no doubt help more of us. :D So, thanks Dez! ^^