64-bit Engine 1.7.6 for S.T.A.L.K.E.R. - Call of Pripyat
Added Support for 8 Cores and 16 Threads
32GB RAM Usage MAX
Engine will now utilise 99% of your GPU
MSAA AND ALPHATEST WORKS!
With this Engine you can use 8K Textures with no problem, If you have good GPU!
This is latest Engine with many fixes and improovements
Older version is not compatible and you need to remove them!
Installation:
Simlpy copy all files to your Call of Pripyat Directory, and remove your gamedata folder, there are a lot of script files that are edited to make this work!
Starting 64 bit engine, there is a CMD file called start_x64.bat
NOTE: Do not replace any of the original bin files from bin_x64
This Engine use its own binaries, so it comes in seperate folder!
Enjoj, and let me know how does it work!
_NightRider_
Hey mate is this engine compatible with any other visual enhancements I can download off moddb?
Yeah, sure.
Can install mods like MISERY over it ? will it work?
This engine does not supprt 8 cores and 16 threads I have never once seen it use 6 core and 12 threads. The CPU pipeline is actually single threaded and is only multithreaded when a game save is being loaded. Other than that the engine has no support for more than 2 threads at high usage.
The engine doesn't use 99% of my GPU all the time I am mostly CPU bound so 99% usage isn't a feature or a function.
The engine also has very bad stability problems when loading saves and just in general where you will crash before you can even start and or finish the first mission.
32gb RAM usage is expected since any 64bit program supports more than 4gb of RAM.
Don't delete the comment this time just change the false description since it is falsely advertising features of the engine and it's actual cpabilities. I had respect for you but not if you can't even take criticism on something you didn't even make but are trying to get people to use why post it and it's details if they are wrong? If deleted I'll keep posting.
The only things you should be advertising about this engine is that it supports multithreaded texture loading and that it only speeds up loading times.
8k texture support is worth advertising like you did and MSAA and alphatest.
But 32gb ram support needs removved, you'd hope an engine supporting 8k would support 32gb or more of ram.8 core and 16 thread support needs removed it is literally a lie. So is the GPU usage.
why are you insistent on being hostile.
Support for 'x' c/t does not mean 'Uses' that amount... are you sure you understand what the word Support means. Get over yourself. Why the hell are you expecting a jank engine like Xray would use so many cores and threads anyway, seek help.
waht changes make this mod in the game?
OpenAL: Can't create sound device.
system is fully updated
win7 ultimate x64 sp1
havent idea what to do... the original \bin works
Initializing Engine...
Starting INPUT device...
Loading DLL: xrRender_R2.dll
Loading DLL: xrRender_R3.dll
refCount:m_pAdapter 1
Loading DLL: xrRender_R4.dll
* D3D11: device creation failed with hr=0x887a0004
command line
Executing config-script "user.ltx"...
[c:\users\admini~1\docume~1\stalker-cop\user.ltx] successfully loaded.
Loading DLL: xrRender_R1.dll
Loading DLL: xrGame.dll
* [win32]: free[-175712 K], reserved[58716 K], committed[116932 K]
* [ D3D ]: textures[0 K]
* [x-ray]: crt heap[18627 K], process heap[18627 K], game lua[0 K], render[0 K]
* [x-ray]: economy: strings[7957 K], smem[0 K]
SOUND: OpenAL: enumerate devices...
SOUND: OpenAL: EnumerationExtension Present
dir[0]=C:\GOG Games\S.T.A.L.K.E.R. Call of Pripyat\bin_x64\
dir[1]=C:\GOG Games\S.T.A.L.K.E.R. Call of Pripyat\
dir[2]=C:\GOG Games\S.T.A.L.K.E.R. Call of Pripyat\bin_x64\
dir[3]=C:\Windows\system32\
CleanDeviceSpecifierList
CleanDeviceSpecifierList
devices
SOUND: OpenAL: system default SndDevice name is
Windows update KB2670838 is known to cause issues with DX10/DX11.
I know it gave me a headache until I uninstalled it.
Also make sure you have the required redistributables to run this engine
Support.microsoft.com
install x86 + x64
you can also try updating your directx as well.
Crashes after a couple minutes for me with a x-ray engine 1.7 error.
yea its working, but it's totally bugged - engine is not playable - crash on crash...
Do I need to edit fxgame.ltx and change $game_data$ from false to true so it loads gamedata folder?
does this work with AtmosFear and Absolute Nature?
This comment is currently awaiting admin approval, join now to view.