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
I turned a corner while driving and the car just disappeared for a couple of frames.
what i did notice was that when i booted the game back up, dlss had switched to fsr3 by itself and i had to switch back in options.
You should be okay with just DLSS for real.
After some stuffing around for the last couple of days, here's what I've discovered:
Forcing V-Sync on has stabilised frame gen.
Using 'On' instead of 'Ultra' for latency has stopped the freeze & reset issue.
Killing the 'GameBar.exe' process via Task Manager (just disabling it Windows Settings was not enough) has stopped a crash-to-desktop I was having.
A bit of digging around in Event Viewer gave me some ideas; thought I'd give them a shot and so far so good.
Oddly enough, patching this new DLSS 4 stuff into Indiana Jones fixed the frame gen in that game while the new DLSS 4 FG was pretty broken in Cyberpunk until I messes around a bit with it and my monitor.
You might even think about finding the newest streamline dlls online from nVidia's GitHub.
With Path Tracing at 1440p+ even with a 4080 Super+ you still need frame generation.