This package will update Call of Chernobyl 1.4 to 1.4.09. Please read the description:
MAY REQUIRE A NEW GAME
Beware that updating can ruin your game if you are using addons that alter the changed files in the patch.
Installation:
- Extract into your S.T.A.L.K.E.R.- Call of Chernobyl directory and overwrite. Make sure relative paths are the same (ie. database should be extracted over S.T.A.L.K.E.R.- Call of Chernobyl\database)
Addon Compatibility With Patches:
- If you see anything in your STALKER-CoC\gamedata directory that is in the file changes, then it's like you don't have the patched version of that file. If you see that you are using modified gamedata that was changed, then avoid the patch and wait for all your addons to be updated.
- Due to the nature of mods, it's impossible to keep compatibility with every patch. The gamedata directory overwrites files stored in the .db files, even the patches. This loading order is dictated by the order in fsgame.ltx. This means it's possible addons will not break when you install patches but your game will be using old files. It's up to the addon creator to unpack the patches and release a compatible addon for the current CoC version.
- AO3, OWR3, STCOP will most likely always be compatible and are currently the only TeamEPIC supported addons for Call of Chernobyl. Purely comestic mods (textures/meshes) should always be compatible as well.
Technical Information about Patches:
- Patch information will be stored in xpatch_01_*.db files. These are split up intentionally so that patches can be small as possible. For example, if a script or config update was made, it will only be a small 500kb re-download of xpatch_01_config.db.
- Versioning is done like Major.Minor.Patch.
REQUIRES A NEW GAME.
Rememdies an issue caused by closecaption to corrupt physic objects that played sounds, which caused things like the arena to be broken or megaphones to not work. Since the issue causes permanent damage to a save it is highly recommended you start a new game. You can still probably use the patch if you don't want to start a new game (CoC is hardy and can actually run with broken corrupt saves unlike CoP). But you will most likely see crashes or strange issues.
Thank you :)
A patch a day keeps the bugs away, or in today's case three of them.
best testing team I've ever seen. I don't mind start again if that keeps the crashes at minimum.
We don't have a testing team anymore. Only for 1.2 did we have like 20+ testers. All you guys are the testers now. :)
Alright i'll forgive you for using us as lab rats,because you guys gave us the best mod ever! :D
Thanks a lot, you guys are a wonderful Dev team. The arena bug was very annoying
Quick question: I'm patched to 1.4.07. Can I simply install this one to bring it up to 1.4.09?
Yes, but: If you see anything in your STALKER-CoC\gamedata directory that is in the file changes, then it's like you don't have the patched versions of that file. If you see that you are using modified gamedata that was changed, then avoid the patch and wait for all your addons to be updated.
Cool. I think what I'll do is do a complete new installation since I have just been patching and have a few addons. That way I will have a fresh start. This is the way I usually do it and it gives me minimal issues, if any ;). Let me know if you think I should do something differently ;)
*Install game in it's own directory on my gaming hard drive.
*Install the current patch.
*Unpack the db files into the gamedata folder.
*Verify all files are there.
*Move all the db files into my archive hard drive.
*Launch game and verify proper version is listed and the game initiates a new game properly.
*Once above is verified, I configure game settings to my liking.
*Verify any addon I want to use has been tested / approved for the current COC version I have installed.
*Unpack said addons if need be.
*Merge the files from the unpacked addon files to the gamedata folder in the COC directory.
*Launch game and verify all is well.
*Edit the files I like to edit.
*Start stalking!
Thanks for the quick patch, now to try my luck at the arena again
Sorry to be the bearer of bad news but I've found a few more bugs. The issue with being stuck in the arena isn't happening anymore thankfully. Though in the mutant arena on the first fight with the pseudodog I did the bet for killing it in 30 seconds for triple the reward and I succeeded, (master difficulty, one knifed its face) and when I turned in to the guy he gave me 0 rubles.
Also another thing, on the loner choice for character selection it says he spawns with a chaser 13 but he still spawns with pmm like last patch, also he doesn't spawn with a medkit like he did last patch oddly enough. I do not recall the rest of what the loadout was saying on the screen but I spawned with knife, pmm with like 100 rounds, some canned food (2 I think) and a piece of bread and anti radiation meds.
Disregard the stuff about the inventory loadout from up above. It randomizes each time I click on it on each faction but when I spawn in it is correct to what it was stated. Ex. Tried bandit and he got black kite, tried him again and he got sip-t m200.
The creature arena thing still is a bug though, gonna go check the other bets now for that. Sorry for the mix up on the inventory.
Update:The other bets are giving me 0 in the creature arena but the fight is activating and ending as it should. Just no reward.
Loadout is random now. I threw a fix for the mutant arena rewards in the current patch, re-download it if you want.
I really should reload the page before I keep making comments haha, thanks for the quick look. I'll check it out.
Update:Everything is working properly now in the arena it seems. Thank you a lot for fixing this so quickly. I'll be sure to post anymore bugs I find.
I got blue screened after going into the wild lands and shooting at some rodents, had 3 followers with me and i started out in yantar.
Good job ! right on time !! :)
Btw there is a small error in the description : you mentioned in download that this is patch 1.4.10 but in description it says
"This package will update Call of Chernobyl 1.4 to 1.4.09. [...] "
Bonjour
Ces patches sont-ils cumulatifs ?
En cas d'une installation nouvelle celui-ci est-il seul utilisable ?
Merci
----------------google trad
Hello
Are the cumulative patches ?
Cumulative there are patches in case of a new installation?
That is what this is. This patch brings all versions of 1.4 to 1.4.10
Merci
Thank you !
Still getting quicksave crashes.
.10 patch with AO3 .4.
New game, Cordon. Quicksaved at the bridge.
stack trace:
0023:08143BE7 xrGame.dll, CxIOFile::Open()
0023:08159881 xrGame.dll, CxIOFile::Open()
[error][ 87] : The parameter is incorrect.
Also getting this one, quick saving worked well until I went to Cordon, started as duty in the farm just south of Freedom base
Talking to a random stalker nets me "ZAT_B7_STALKERS_VICTIMS_DIALOG_11"
Besides this minor bug, I've yet to run into anything big yet.
Happened during a prolonged firefight:
FATAL ERROR
[error]Expression : <no expression>
[error]Function : handler_base
[error]File : xrDebugNew.cpp
[error]Line : 935
[error]Description : pure virtual function call
stack trace:
0023:002764AA xrCore.dll, xrDebug::_initialize()
0023:00436DCF xrEngine.exe, CRenderDevice::SecondaryThreadProc()
0023:0027C60C xrCore.dll, thread_spawn()
stack trace:
0023:722FFE42 lua51.dll, lua_newstate()
0023:722C763A lua51.dll, lua_rawgeti()
0023:08B5099E xrGame.dll, CDialogHolder::UseIndicators()
0023:08DA955E xrGame.dll, CDialogHolder::IgnorePause()
0023:0046105E xrEngine.exe, CInput::OnFrame()
0023:00436470 xrEngine.exe, CRenderDevice::message_loop()
0023:004363AE xrEngine.exe, CRenderDevice::Run()
0023:00469F83 xrEngine.exe, CApplication::CApplication()
0023:00469AD6 xrEngine.exe, CApplication::CApplication()
0023:00433453 xrEngine.exe, CObjectList::o_crow()
0023:74D062C4 KERNEL32.DLL, BaseThreadInitThunk()
0023:77CB0609 ntdll.dll, RtlSubscribeWnfStateChangeNotification()
0023:77CB05D4 ntdll.dll, RtlSubscribeWnfStateChangeNotification()
stack trace:
0023:722FFE42 lua51.dll, lua_newstate()
0023:722C763A lua51.dll, lua_rawgeti()
0023:08B5099E xrGame.dll, CDialogHolder::UseIndicators()
0023:08DA944B xrGame.dll, CDialogHolder::IgnorePause()
0023:751CE84A USER32.dll, DispatchMessageW()
0023:751CE480 USER32.dll, DispatchMessageW()
0023:751D8AD9 USER32.dll, MsgWaitForMultipleObjectsEx()
0023:77CBFEF6 ntdll.dll, KiUserCallbackDispatcher()
0023:77CEDC00 ntdll.dll, LdrSetAppCompatDllRedirectionCallback()
0023:77CB05D4 ntdll.dll, RtlSubscribeWnfStateChangeNotification()
CoCh v.1.4.10 + Arsenal Overhaul v.4 + Light Nanohud mod + better torchlight mod + Duty Faction. Game crashes while shooting at mutant or a zombie.
FATAL ERROR
[error]Expression : xml_doc.NavigateToNode(path,index)
[error]Function : CUIXmlInit::InitStatic
[error]File : ui\UIXmlInit.cpp
[error]Line : 156
[error]Description : XML node not found
[error]Argument 0 : cs_enemy_health
[error]Argument 1 : ui\ui_custom_msgs.xml
stack trace:
0023:09501FD2 xrGame.dll, CDialogHolder::IR_UIOnKeyboardHold()
0023:09465C9F xrGame.dll, CDialogHolder::IR_UIOnKeyboardHold()
OK. I solved the problem. The problem was that I checked "Show enemy health" in option menu. And I think it's not compatible with Light Nano hud mod. Now the game is not crashing.
A rather small typo for the mutant arena, when you get to fight this zombie later on called the Beast the buy in for the match is 4000 even though in chat it says 5000.
Also another little bug where the door doesn't shut sometimes all the way, just don't stand in the way of it and even if you do for a moment it almost always shuts again. I just had it happen twice though where when I came in for another mutant round that the door was already opened and the match wouldn't start. Not sure if it can really be fixed so to speak so just a heads up, don't block the door. A case of the "I said come in, don't stand there!"
i have problem with Saves when i load 2 time it crashes why??
1.4.10
FATAL ERROR
[error]Expression : <no expression>
[error]Function : handler_base
[error]File : xrDebugNew.cpp
[error]Line : 935
[error]Description : pure virtual function call
stack trace:
0023:007864AA xrCore.dll, xrDebug::_initialize()
0023:00436DCF xrEngine.exe, CRenderDevice::SecondaryThreadProc()
0023:0078C60C xrCore.dll, thread_spawn()
Saved game during an emission in the ship at Zaton. Now, whenever I load that save I instantly die even before the game is fully loaded. Also, I've noticed something off with the physics, as sometimes enemies will fly off upon death.
Story mode is not working for bandits. Why?
Currently I'm playing CoCh 1.4.08 + AO v.4 + Light Nonohud and better torchlight. Freedom faction. I was playing CoCh 1.4.10 but it was too laggy for some reason. I don't know why. I went back to 1.4.08. Game runs smooth now. But I have problem in Cordon and Jupiter location. Game is crashing while reloading my saved game.
This is when game crashed in Cordon. Same as in Jupiter:
FATAL ERROR
[error]Expression : <no expression>
[error]Function : CScriptEngine::lua_error
[error]File : ..\xrServerEntities\script_engine.cpp
[error]Line : 193
[error]Description : fatal error
[error]Arguments : LUA error: ... chernobyl\gamedata\scripts\alife_storage_manager. script:31: attempt to index a nil value
stack trace:
0023:00B571FC xrCore.dll, xrDebug::fatal()
0023:092863A1 xrGame.dll, CDialogHolder::IgnorePause()
0023:09285DE7 xrGame.dll, CDialogHolder::IgnorePause()
0023:5A4CEA0E MSVCR120.dll, _RTDynamicCast()
load all save , all quicksave = lost in the zone.????????
Some bugs I've encountered: I can't go to garbage, I click yes when it asks me to change level, but nothing happens.
Some times I can't save.
Sometimes I have CRASHes, when I make quick save.
Noticed only on the Cordon, for now, in other places, not yet.
P.S.
Look like I figured out, how to fix it.
If somebody have quick save CRASH:
Just open menu, load last save, after that make a normal save (not quick) and delete all quick saves.
Seems it work, anyway ... for now.
I'm sure this is a temporary solution, because it`s don`t fix the cause of the crashes, but at least some solution.
P.S.S.
English isn't my native language, so please excuse any mistakes.
what about absolute structures and nature? is there a better texture pack out there seeing as that is out of date?
Shooting a Bloodsucker in Cordon. It was for a mutant quest, however the other Bloodsucker was still alive.
No other mods. Fresh install. DX9 Enhanced.
stack trace:
[error][ 183] : Cannot create a file when that file already exists.
Full log: Hastebin.com
Small but useful tip:
If you play story mode, DON'T eat anabiotic when quest to "Protect scientists bunker from zombies" start - it will CRASH.
Shaking screen is annoying, of course, and interfere to shoot accurately, but in that whole "salt".
So... stock up on ammo, BEFORE you ask Saharov about psy-helm and be patient, when f... err... zombies start coming.
P.S.
English isn't my native language, so please excuse any mistakes.
Hi.
I ordered a sniper rifle to Nimble. It delivered to me the SVU-A from Max. But then loading the game (there had given me CTD) the rifle became an SVU.
I played 1.4.10 with STCoP Weapon Pack 2.8.0.7 (v.2).
Something wrong in the Pripyat Outskirts.
I have a few CRASHes. Just CRASH and all, no system messages like "FATAL" or something.
After third or fourth crash, I checked log file and found this:
FATAL ERROR
[error]Expression : <no expression>
[error]Function : handler_base
[error]File : xrDebugNew.cpp
[error]Line : 935
[error]Description : pure virtual function call
stack trace:
0023:007864AA xrCore.dll, xrDebug::_initialize()
0023:00436DCF xrEngine.exe, CRenderDevice::SecondaryThreadProc()
0023:0078C60C xrCore.dll, thread_spawn()
Getting alot of this:
FATAL ERROR
[error]Expression : <no expression>
[error]Function : handler_base
[error]File : xrDebugNew.cpp
[error]Line : 935
[error]Description : pure virtual function call
stack trace:
0023:002864AA xrCore.dll, xrDebug::_initialize()
0023:00436DCF xrEngine.exe, CRenderDevice::SecondaryThreadProc()
0023:0028C60C xrCore.dll, thread_spawn()
Sometimes if I'm lucky I might get 20 minutes of play. Happens alot on Zaton.
AO does not seem to work,what do?
Ok so a few things that I have noticed or experienced.
1- There are times when you are not able to save. It will not save the game or over rite a saved file.
2- There are times when trying to reach Garbage from Cordon using the portals near farm (the ones by the tunnel) you will not be transported to garbage. Only way to fix is exit game and restart, and sometimes that does not work.
3- Unable to complete the escort scientist task both in Jupiter or in the Great Swamp. No matter what you do when you escort the scientist back to camp when given the update, when you speak to the character that gave you the task, no option to inform the task is done.
Any ideas what could be causing these issues?
Ok so a few things that I have noticed or experienced.
1- There are times when you are not able to save. It will not save the game or over rite a saved file.
2- There are times when trying to reach Garbage from Cordon using the portals near farm (the ones by the tunnel) you will not be transported to garbage. Only way to fix is exit game and restart, and sometimes that does not work.
3- Unable to complete the escort scientist task both in Jupiter or in the Great Swamp. No matter what you do when you escort the scientist back to camp when given the update, when you speak to the character that gave you the task, no option to inform the task is done.
Any ideas what could be causing these issues?
The last one isn't a bug, have you talked to the scientist after you escorted back to the camp?
Yeah I tried that. Unless I missed a dialogue option, no joy. I'll double check later this evening when I play some more and let you know. Thx.
Hey Mihzvol...update: same deal happening. Only way I can complete the mission is to save the game when I escort them back to camp, exit the game, and reload that save game file. then I get the dialogue when I speak to the ecologist and the tasks completes.
I ran into problems 1 and 2 aswell, try typing " vid_restart " in console when you run into those problems. Not a real fix ofc, but at least you wont have to restart the entire game everytime until a patch rolls out.