S.T.A.L.K.E.R. 2: Heart of Chornobyl

S.T.A.L.K.E.R. 2: Heart of Chornobyl

データを表示:
RAM going up uncontorllably 32 gb
Hi, i have 32gb ram memory
all drivers up to date, bios, chipset, all taht stuff
and in end of compiling shadersscreen i have over 13gb of ram used by game
and it rises ingame and after few minutes crashes due to maxxing out ram
i need help fast
< >
1-15 / 17 のコメントを表示
13gb only ? bro my game is eating 20gb
Snack の投稿を引用:
13gb only ? bro my game is eating 20gb
my friend on same settings and resolution has like 5gb of ram usage
Hi. Many users, including myself [i9-12900K | RX 7900 XTX | 32GB (2x16GB) DDR4-3600 CL14 here], experience the same issue. The shader recompiling process triggered each time the game is launched consumes almost all of the system's free memory, depending on your in-game settings. As a result, performance can degrade considerably over time during gameplay. This mismanagement of the system memory (RAM) and probably VRAM too, contributes to the game’s well-known and officially acknowledged "memory leak" issue.

I managed to work around the issue by using the ISLC tool (Intelligent Standby List Cleaner) by Wagnardsoft -the developer of Display Driver Uninstaller (DDU), to keep my free system memory under control and to prevent the performance degradation over time. So, I'd suggest launching ISLC, using its default settings, or just setting the "Free memory is lower" condition value (MB) to half of the "Free Memory" ISLC reports on the desktop before launching the game. After that, click the ISLC "Start" button, minimize it, and launch the game. ISLC will operate in the background performing its functions. I recommend not altering other ISLC features, such as timer resolution settings and the ISLC polling rate (1000 ms; the default value is optimal).

Download the latest ISLC version from here:

https://www.wagnardsoft.com/content/Intelligent-standby-list-cleaner-ISLC-v1034-Released
最近の変更はRodroGが行いました; 11月24日 4時43分
RodroG の投稿を引用:
Hi. Many users, including myself, experience the same issue. The shader recompiling process that occurs each time the game is launched uses a significant portion of the system's free memory. As a result, performance can degrade considerably over time during gameplay. This mismanagement of the system memory (RAM) and probably VRAM too, contributes to the game’s well-known and officially acknowledged "memory leak" issue.

I managed to work around the issue by using the ISLC tool (Intelligent Standby List Cleaner) by Wagnardsoft -the developer of Display Driver Uninstaller (DDU), to keep my free system memory under control and to prevent the performance degradation over time. So, I'd suggest launching ISLC, using its default settings, or just setting the "Free memory is lower" condition value (MB) to half of the "Free Memory" ISLC reports on the desktop before launching the game. After that, click the ISLC "Start" button, minimize it, and launch the game. ISLC will operate in the background performing its functions. I recommend not altering other ISLC features, such as timer resolution settings and the ISLC polling rate (1000 ms; the default value is optimal).

Download the latest ISLC version from here:

https://www.wagnardsoft.com/content/Intelligent-standby-list-cleaner-ISLC-v1034-Released

[SystemSettings]
r.PSOWarmup.WarmupMaterials=0

add this line in your engine.ini and recompiling is turned off
TR0N の投稿を引用:
RodroG の投稿を引用:
Hi. Many users, including myself, experience the same issue. The shader recompiling process that occurs each time the game is launched uses a significant portion of the system's free memory. As a result, performance can degrade considerably over time during gameplay. This mismanagement of the system memory (RAM) and probably VRAM too, contributes to the game’s well-known and officially acknowledged "memory leak" issue.

I managed to work around the issue by using the ISLC tool (Intelligent Standby List Cleaner) by Wagnardsoft -the developer of Display Driver Uninstaller (DDU), to keep my free system memory under control and to prevent the performance degradation over time. So, I'd suggest launching ISLC, using its default settings, or just setting the "Free memory is lower" condition value (MB) to half of the "Free Memory" ISLC reports on the desktop before launching the game. After that, click the ISLC "Start" button, minimize it, and launch the game. ISLC will operate in the background performing its functions. I recommend not altering other ISLC features, such as timer resolution settings and the ISLC polling rate (1000 ms; the default value is optimal).

Download the latest ISLC version from here:

https://www.wagnardsoft.com/content/Intelligent-standby-list-cleaner-ISLC-v1034-Released

[SystemSettings]
r.PSOWarmup.WarmupMaterials=0

add this line in your engine.ini and recompiling is turned off

Thanks, but I don't have any Engine.ini file in %LOCALAPPDATA%\Stalker2\Saved\Config\Windows\.
create one or download from nexus mods
TR0N の投稿を引用:
create one or download from nexus mods

Ok, I will try. Anyway, the acknoledged memory leak and performance degradation over time issue will trigger regardless of this PSOWarmup tweak, so I will likely have to use ISLC anyway. That said, turning off the recompiling seems useful as this process is a bit annoying (in my case the PSO warmup is fast, but anyway) and it pushes one purge of the standby list & system working set mandatory.
Worth to check nexus mods regulary there are already several mods and ini tweaks to push performance
TR0N の投稿を引用:
Worth to check nexus mods regulary there are already several mods and ini tweaks to push performance

I'm aware, but most Engine.ini mods I've seen may mess with or degrade the game's image quality too much for my taste. Also, performance is not an issue for me in this game. My concern is the memory leak issue which ends up causing performance degradation over time, and the ISLC tool has worked very well to prevent this consequence till officially fixed.

A doubt about the creation/editing of the Engine.ini file, should I also add a [Core.System] section with all its corresponding Paths lines or it will work just by adding the two lines you provided ([SystemSettings] r.PSOWarmup.WarmupMaterials=0)?
works by just adding these lines

[SystemSettings]
r.MaxAnisotropy=16
r.Tonemapper.GrainQuantization=0
r.FilmGrain=0
r.NT.Lens.ChromaticAberration.Intensity=0
r.SceneColorFringeQuality=0
r.Tonemapper.Sharpen=0.8
r.Streaming.PoolSize=12288
r.PSOWarmup.WarmupMaterials=0

this is how my ini looks atm
i added few other lines to remove film grain, ChromaticAberration and boost vram usage
RodroG の投稿を引用:
Hi. Many users, including myself [i9-12900K | RX 7900 XTX | 32GB (2x16GB) DDR4-3600 CL14 here], experience the same issue. The shader recompiling process triggered each time the game is launched consumes almost all of the system's free memory, depending on your in-game settings. As a result, performance can degrade considerably over time during gameplay. This mismanagement of the system memory (RAM) and probably VRAM too, contributes to the game’s well-known and officially acknowledged "memory leak" issue.

I managed to work around the issue by using the ISLC tool (Intelligent Standby List Cleaner) by Wagnardsoft -the developer of Display Driver Uninstaller (DDU), to keep my free system memory under control and to prevent the performance degradation over time. So, I'd suggest launching ISLC, using its default settings, or just setting the "Free memory is lower" condition value (MB) to half of the "Free Memory" ISLC reports on the desktop before launching the game. After that, click the ISLC "Start" button, minimize it, and launch the game. ISLC will operate in the background performing its functions. I recommend not altering other ISLC features, such as timer resolution settings and the ISLC polling rate (1000 ms; the default value is optimal).

Download the latest ISLC version from here:

https://www.wagnardsoft.com/content/Intelligent-standby-list-cleaner-ISLC-v1034-Released

What memory leak issue? I've played for hours at a time without a single crash or performance loss. If it's not happening for everyone then it's not a memory leak... It's a "you" leak so stop peddling your third-party links here.
最近の変更はBacon Overlord®が行いました; 11月24日 5時27分
I suspect that there is a bug that can make the game suddenly consume all available memory and crash, not a memory leak over time.

I’ve had one crash (hang) so far, and I could see task manger reporting 98% memory used. Since then I’ve been watching memory usage and for me it starts at around 19g. Over a period of several hours in game I watched it float around and work its way down to as low as 16g. That not indicative of a memory leak.
TR0N の投稿を引用:
works by just adding these lines

[SystemSettings]
r.MaxAnisotropy=16
r.Tonemapper.GrainQuantization=0
r.FilmGrain=0
r.NT.Lens.ChromaticAberration.Intensity=0
r.SceneColorFringeQuality=0
r.Tonemapper.Sharpen=0.8
r.Streaming.PoolSize=12288
r.PSOWarmup.WarmupMaterials=0

this is how my ini looks atm
i added few other lines to remove film grain, ChromaticAberration and boost vram usage

Thank you. Helpful pointers.
TR0N の投稿を引用:
works by just adding these lines [...]

Thank you. :)
最近の変更はRodroGが行いました; 11月24日 5時33分
TR0N の投稿を引用:
create one or download from nexus mods
which mod to install and how to do this can u tell me ?
< >
1-15 / 17 のコメントを表示
ページ毎: 1530 50

投稿日: 11月23日 13時37分
投稿数: 17