Full concept MODIFICATION of S.T.A.L.K.E.R. Call of Pripyat that touches every game aspect including textures, sfx, music, weapons, A.I., items, weather, mutants, difficulty and much more!

Forum Thread
by member
  Posts  
xray engine crash.. (Mods : MISERY : Forum : Mod optimization : xray engine crash..) Post Reply
Thread Options
Apr 22 2013, 1:56pm Anchor

Hello everyone! So i bought this new laptop:

8gb ddr3 ram
intel i5 dual core processor 2.5
nvidiagforce gt 635m 2gb
1tb hd

I've installed a clean call of prypiat 1.6.02, when I ran it, it worked perfectly. But then, when I try to launch misery, the game crashes with no aparent reason, I cant even start it. Does anyone know hos is this possible?

Apr 26 2013, 7:11am Anchor

I just did a completely fresh install of Cop through steam for the first time. Installed the mod, then the patch, and booted up the game. I can get to the main menu and see that Patch 2 is installed, however when I try to start a new game it crashes saying the engine stopped working.

My laptop pc has an intel i7 processor, nvidia gt335 at 1gb and I have 4gb ram.

Anyone please help!!!

May 29 2013, 4:06pm Anchor

Same problem here :P

Jul 31 2013, 6:31pm Anchor

Same problem.

Jul 31 2013, 8:43pm Anchor

yep getting the same here, cant even load my game

Jul 31 2013, 10:41pm Anchor

Run as administrator

Aug 1 2013, 4:53am Anchor

Me too. I run as an admin on windows 7

Aug 1 2013, 6:56am Anchor

Don't know if it is related, but I play in DX9, even though I have a mighty rig. Haven't suffered any random CTD's, only occasional stuttering.

Aug 1 2013, 12:25pm Anchor

I can run Misery with maximum quality and DX11 (but without Antialiasing)
My PC is quadcore i5 cpu with 16GB RAM and HD7950.

On my PC Stalker Misery takes nearly 4GB RAM.
Because Windows itself and hard disk cache also use RAM, you should have more than 4GB RAM.
Windows 32bit only supports 3GB RAM, so you should habe Windows 64bit.

If Misery used RAM goes above 4GB then crash to desktop, xray 1.6 stopped working.
So if xrengine.exe uses nearly 4GB RAM then you have to reduce RAM usage
by cutting down e.g. shadow quality, so that shadow map size is reduced.

You can see xrengine.exe RAM usage in windows task manager
total = "used ram" + "commit size"

Edited by: moddbplayer

Aug 1 2013, 1:05pm Anchor

Loading from an earlier save fixed it (so far) for me.

P.S. I play on a laptop with 12 gigs of ram.

Aug 1 2013, 7:46pm Anchor
moddbplayer wrote:I can run Misery with maximum quality and DX11 (but without Antialiasing)
My PC is quadcore i5 cpu with 16GB RAM and HD7950.

On my PC Stalker Misery takes nearly 4GB RAM.
Because Windows itself and hard disk cache also use RAM, you should have more than 4GB RAM.
Windows 32bit only supports 3GB RAM, so you should habe Windows 64bit.

If Misery used RAM goes above 4GB then crash to desktop, xray 1.6 stopped working.
So if xrengine.exe uses nearly 4GB RAM then you have to reduce RAM usage
by cutting down e.g. shadow quality, so that shadow map size is reduced.

You can see xrengine.exe RAM usage in windows task manager
total = "used ram" + "commit size"



Pretty much none of this will change the problem, though.

Aug 1 2013, 8:08pm Anchor

Same here

Aug 1 2013, 9:58pm Anchor

I had the same issue too. I tried changing to DX10 @ medium settings (enhanced dynamic lighting) and it will crash immediately after loading or it will randomly crash at certain point when i change to DX9 @ maximum (enhanced dynamic lighting). However, it didn't crash when i changed to DX11 @ maximum settings which makes me wondering what is wrong with it?

Aug 2 2013, 8:58am Anchor

Try deleting your CoP file in your document folder. If it's the crash I think it is, it's an old one. Deleting the file will reset your preferences, and fix the crash. Bear in mind if you have a save, back it up first.

Aug 2 2013, 11:22am Anchor
FireFly081 wrote:Try deleting your CoP file in your document folder. If it's the crash I think it is, it's an old one. Deleting the file will reset your preferences, and fix the crash. Bear in mind if you have a save, back it up first.


Well that doesn't sound like a good fix. That sounds like a broken mod. I'll wait for it to get patched/fixed.

Aug 3 2013, 5:00pm Anchor
Kuzkula wrote:
moddbplayer wrote:I can run Misery with maximum quality and DX11 (but without Antialiasing)
My PC is quadcore i5 cpu with 16GB RAM and HD7950.

On my PC Stalker Misery takes nearly 4GB RAM.
Because Windows itself and hard disk cache also use RAM, you should have more than 4GB RAM.
Windows 32bit only supports 3GB RAM, so you should habe Windows 64bit.

If Misery used RAM goes above 4GB then crash to desktop, xray 1.6 stopped working.
So if xrengine.exe uses nearly 4GB RAM then you have to reduce RAM usage
by cutting down e.g. shadow quality, so that shadow map size is reduced.

You can see xrengine.exe RAM usage in windows task manager
total = "used ram" + "commit size"



Pretty much none of this will change the problem, though.


Yes it is to understand the reason for xray engine crash.
If the problem is "out of memory" you have to solve the RAM problem.
If it is not then the devs need fix something in map or script...
Maybe anyone can post here settings which reduce RAM usage?

Aug 3 2013, 5:08pm Anchor
TheLoneStalker wrote:Hello everyone! So i bought this new laptop:

8gb ddr3 ram
intel i5 dual core processor 2.5
nvidiagforce gt 635m 2gb
1tb hd

I've installed a clean call of prypiat 1.6.02, when I ran it, it worked perfectly. But then, when I try to launch misery, the game crashes with no aparent reason, I cant even start it. Does anyone know hos is this possible?


drag and drop the texture folder that fixed it for me

Aug 3 2013, 6:19pm Anchor
moddbplayer wrote:
Kuzkula wrote:
moddbplayer wrote:I can run Misery with maximum quality and DX11 (but without Antialiasing)
My PC is quadcore i5 cpu with 16GB RAM and HD7950.

On my PC Stalker Misery takes nearly 4GB RAM.
Because Windows itself and hard disk cache also use RAM, you should have more than 4GB RAM.
Windows 32bit only supports 3GB RAM, so you should habe Windows 64bit.

If Misery used RAM goes above 4GB then crash to desktop, xray 1.6 stopped working.
So if xrengine.exe uses nearly 4GB RAM then you have to reduce RAM usage
by cutting down e.g. shadow quality, so that shadow map size is reduced.

You can see xrengine.exe RAM usage in windows task manager
total = "used ram" + "commit size"



Pretty much none of this will change the problem, though.


Yes it is to understand the reason for xray engine crash.
If the problem is "out of memory" you have to solve the RAM problem.
If it is not then the devs need fix something in map or script...
Maybe anyone can post here settings which reduce RAM usage?



Mine blows it's cork before even hitting 2gb of ram. I checked to make sure, and it's set to handle >3gb, so it's not an issue there.

Sep 11 2013, 5:36pm Anchor

Same problem here, i tried the texture swap -> not working.
On my 32bis netbook everything runs, but my 64bit rack cant even get me to the splash screen :(
God, that sucks... i was watching this mod for months and am trying desperatelly to get it to work since release

Yastiandrie
Yastiandrie The new Badmin
Sep 11 2013, 6:33pm Anchor
Kuzkula wrote:
FireFly081 wrote:Try deleting your CoP file in your document folder. If it's the crash I think it is, it's an old one. Deleting the file will reset your preferences, and fix the crash. Bear in mind if you have a save, back it up first.


Well that doesn't sound like a good fix. That sounds like a broken mod. I'll wait for it to get patched/fixed.


- Actually you should delete your user.ltx and shaders cache if you are installing overhaul mods and redo your settings or you could encounter crashing

- Also if you are trying to run it in dx10 and it's crashing on the menu either uninstall windows update kb 2670838, make sure any dll hooks (fraps, msi afterburner, steam overlay, etc) are not running, or both

- People running 32 bit systems will be more likely to run into problems hitting memory caps (It doesn't say high-end PC required for the sake of it).

- If you are getting a crash while trying to launch the game then you've done something wrong with the install, or it's some other problem on your end. No amount of patching can fix that

- Not supplying crash logs won't get you any help. If we can't replicate the problem or know exactly what the problem is, we can't fix it

Sep 12 2013, 11:43am Anchor

Two days ago the gmae started crashing a LOT. I have no idea what i did and i don't get any crashlogs...

Reply to Thread
click to sign in and post

Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.