Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
When an Integer isnt closed properly you might get a memory leak.
I don't think Nvidia' driver update addressed it, nothing in notes.
Also, Stalker 2, big patch coming in February.
Secondly, manually updating with DLSS4 with DLL's from Cyberpunk, using Upscaler DLSS4 and Framegen4 (before nvidia's driver patch,) also didn't resolve Stalker 2 framegen issue.
Therefore, while I'm updating my driver now, i have ZERO faith anything will be fixed UNTIL GSC releases their BIG patch in February.
(I'll update this thread once I have an hour to 3 test DLSS4 driver-update, framegen DLSS4 forced, memleak.)
TL:DR - I believe new driver + Framegen DLSS4 forced, fixes Framegen Leak. At least in my limited testing, VRAM usage is not only lower overall, but I didn't see the usual gradual rise after 30mins-45mins of play.
One thing to note, Nvidia app currently only allows DLSS override for Framegen, not DLSS upscaler. (Apparently nvidia believes its not optimal and therefore upscaler DLSS4 for this title at least is considered, unsupported/unavailable for now.)
Back on topic, I played for 40mins and DLSS4 framegen on my 4090, I see an extra 12-18 FPS increase.
Monitored VRAM usage between Pripyat and Rostok and VRAM was noticeable lower and no-longer under an hour playthrough.
VRAM 10GB initial load in pripyat.
(4k, Dlss quality, epic settings, framegen-On, HDR on.)
Moving between cities, VRAM 11-13GB, but would steadily fallback to near 11GB or 10GB in a single play-session.
I THINK DLSS Framegen mem-leak IS fixed via new nvidia driver and official DLSS4 implementation.
(I did not test DLSS framegen without forced DLSS4 to see if Nvidia driver truly fixed or the FrameGen 4 actually provided the fix or both together.)
Unreal Engine s#@%s, why the f#@% does it need to copy/move all the game files to a new location while patching them? cant it just patch/replace the existing files?
Because of how a SSD works its also causing extra wear to your SSD, but most SSD's now can handle much more read/write cycles than a few years back, but still this method of updating really s#@%s because it takes much longer than simply replacing a few MB or GB of files.
I force Super Resolution with Nvidia Profile Inspector. Works great and looks good.
The visual improvement is huge. I use model K.
I don't wanna take a performance hit with new DLSS Upscale Preset K.
(I love the extra frames I gained from FrameGen DLSS4
I wonder why Nvidia doesn't think this game is ready via their app for DLSS Upscale Preset - Odd.
You can update S.T.A.L.K.E.R. 2: Heart of Chernobyl to DLSS 4 using DLSS Swapper:
https://github.com/beeradmoore/dlss-swapper