Инсталирайте Steam
вход
|
език
Опростен китайски (简体中文)
Традиционен китайски (繁體中文)
Японски (日本語)
Корейски (한국어)
Тайландски (ไทย)
Чешки (Čeština)
Датски (Dansk)
Немски (Deutsch)
Английски (English)
Испански — Испания (Español — España)
Испански — Латинска Америка (Español — Latinoamérica)
Гръцки (Ελληνικά)
Френски (Français)
Италиански (Italiano)
Индонезийски (Bahasa Indonesia)
Унгарски (Magyar)
Холандски (Nederlands)
Норвежки (Norsk)
Полски (Polski)
Португалски (Português)
Бразилски португалски (Português — Brasil)
Румънски (Română)
Руски (Русский)
Финландски (Suomi)
Шведски (Svenska)
Турски (Türkçe)
Виетнамски (Tiếng Việt)
Украински (Українська)
Докладване на проблем с превода
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\.
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.
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)?
[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
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.
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.
Thank you. Helpful pointers.
Thank you. :)