Crash on Splash Screen Thread - MISERY mod for S.T.A.L.K.E.R.: Call of Pripyat

Not entirely sure where to put this since Misery doesn't have a dedicated topic for tech support, if this is the wrong place I'll gladly move it.

Anyways, the problem I'm having is that Misery constantly crashes at the splash screen when CoP is first launched. Vanilla CoP works fine, no lag or anything, but when I add Misery it just doesn't start. I would post my crash logs, but the problem is that no logs show up in the first place. Mini-dump files are created so I'm glad to supply those if someone needs them, but for the most part I'm clueless as to what might be the issue. My laptop is very powerful, with an i5-3230M Processor, 6 GB of RAM and 2 Nvidia GeForce GT 650M's so I don't think it's because my computer is unable to handle the mod. I've tried re-installing everything, running in compatibility mod for other versions of windows (running on Windows 8 and hating it), running it as an administrator (aren't we suppose to do that regardless of if we crash?) and even disabling Steam overlay and restarting my computer. Nothing has worked, anyone else have this bug? Anyone been able to fix it?

Seems like either the download was corrupted or it was installed incorrectly

I installed via the EXE and made sure to select the correct version (Retail or steam) so I guess the download was corrupted? I'll redownload and try again.

EDIT: No dice, tried 3 different download sites (Google Drive, Mega, and then finally ModDB) and none of them worked, starting to think it's more than just a corrupt download issue. Any other ideas?

Edited by: wu105

were you running it in dx10 before?..try deleting the user.ltx

Just tried that, no dice. Unless I deleted the wrong user.ltx, for the steam version it's in the _appdata_ folder in the main directory right?

Yup

Are you running any other dll hooks? (e.g Fraps, msi afterburner)

Tried verifying integrity in steam?

Other then that I can't think of anything else except it not being installed correctly

No other .dll hooks unless something's running behind my back (checked the processes running and I doubt it) and verified steam integrity, nothing was reported wrong. I'll try redownloading it again, and if all else fails perhaps manually installing the mod. Is that possible? Or is it a horrible idea?

It's quite possible, as long as you put everything in the right place.
Make sure you have downloaded Misery 2.0 + 2.0.2 patch + 2.0.2 quickfix

Misery 2.0 manual install
-unpack the 2.0 download

-copy the gamedata folder into your Cop main directory (make sure there is not a gamedata folder already in there. Delete it if there is)

-backup the Cop directory\bin folder

-copy Steam_xrEngine.exe from unpacked bin to cop dir\bin, then rename it xr_Engine.exe

-copy whichever fov.dll from unpacked\bin you want to play with (55 is standard CoP FOV. Its really personal preference but either 75, 83, or 85 would be the better choices) over to the CoP dir\bin folder, rename this xrGame.dll

-copy all the other dlls from unpacked\bin to CoP\bin folder

-in your _appdata_ make sure user.ltx and shader_cache folder is deleted

-back up Stalker-COP.exe in main CoP Directory, copy over the Stalker-COP.exe in the unpacked download

-check to make sure your fs-game.ltx in the main CoP dir looks like this:

;abbreviation           = recurs|notif|  root|                  add|        ext|            description
$app_data_root$         = true|  false| $fs_root$|            _appdata_\
$arch_dir$              = false| false| $fs_root$
$game_arch_mp$          = false| false| $fs_root$|            mp\
$arch_dir_levels$       = false| false| $fs_root$|            levels\
$arch_dir_resources$    = false| false| $fs_root$|            resources\
$arch_dir_localization$ = false| false| $fs_root$|            localization\
$arch_dir_patches$      = false| true|  $fs_root$|            patches\
$game_data$             = false| true|  $fs_root$|            gamedata\
$game_ai$               = true|  false| $game_data$|          ai\
$game_spawn$            = true|  false| $game_data$|          spawns\
$game_levels$           = true|  false| $game_data$|          levels\
$game_meshes$           = true|  true|  $game_data$|          meshes\|       *.ogf;*.omf|   Game Object files
$game_anims$            = true|  true|  $game_data$|          anims\|        *.anm;*.anms|  Animation files
$game_dm$               = true|  true|  $game_data$|          meshes\|       *.dm|          Detail Model files
$game_shaders$          = true|  true|  $game_data$|          shaders\
$game_sounds$           = true|  true|  $game_data$|          sounds\
$game_textures$         = true|  true|  $game_data$|          textures\
$game_config$           = true|  false| $game_data$|          configs\
$game_weathers$         = true|  false| $game_config$|        environment\weathers
$game_weather_effects$  = true|  false| $game_config$|        environment\weather_effects
$textures$              = true|  true|  $game_data$|          textures\
$level$                 = false| false| $game_levels$
$game_scripts$          = true|  false| $game_data$|          scripts\|      *.script|      Game script files
$logs$                  = true|  false| $app_data_root$|      logs\
$screenshots$           = true|  false| $app_data_root$|      screenshots\
$game_saves$            = true|  false| $app_data_root$|      savedgames\
$downloads$             = false| false| $app_data_root$
$game_class_assaulter$  = true|  false| $game_data$|          class_diversity\assaulter\
$game_class_recon$      = true|  false| $game_data$|          class_diversity\recon\
$game_class_sniper$     = true|  false| $game_data$|          class_diversity\sniper\

- Now try booting up the game

Patch 2.0.2
- Unpack and Copy base\gamedata into the CoP main directory. Overwrite any files it asks

- Unpack and copy new_game_version\gamedata into CoP main directory. Overwrite again

- Check to see if game loads

2.0.2 QF
- copy base\gamedata into CoP main directory. Overwrite any files it asks

Hope that all makes sense

I noticed something... All the FOV .dll's have 1602_ preceding the fov level. Is there suppose to be a special .dll for steam or is that irrelevant?

wu105 wrote: I noticed something... All the FOV .dll's have 1602_ preceding the fov level. Is there suppose to be a special .dll for steam or is that irrelevant?

That's the cop version number 1.602. That's the latest version of cop

So it's irrelevant. Manually installing it didn't work either, this is really starting to frustrate me. Any other ideas? Or should I just give up at this point?

Without installing it for you I have no other advice to offer

Well this sucks, I was looking forward to playing STALKER with Misery... Oh well, I may try again in the future.

same problem here and we are not the only ones
there are several posts in this board, although you posted the most detailed crashlog. My Netbook is able to start the whole shit but my PC isnt.. i guess its some cpu or gpu thing..

I tried one more time and this time I got a crash with some more information on it than before. Here's the Microsoft crash report:

Problem Event Name:	APPCRASH
  Application Name:	xrEngine.exe
  Application Version:	1.6.0.2
  Application Timestamp:	4b275197
  Fault Module Name:	xrCore.dll
  Fault Module Version:	1.6.0.2
  Fault Module Timestamp:	4b25fc61
  Exception Code:	80000003
  Exception Offset:	0001e12e
  OS Version:	6.3.9600.2.0.0.768.101
  Locale ID:	2057
  Additional Information 1:	fa59
  Additional Information 2: fa59da798eabc69fb5ab5e75a973798c
  Additional Information 3:	ba19
  Additional Information 4: ba19066422da638589876f2b79fbc6c1

Engine Crash Report (Archived): Mediafire.com

Thanks Yasti, I reinstalled it and it works now.

so,i can only play in assault class,if i choose another,game crash in starting new game