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
- You cap framerate
- Real frames on screen are the ones you cap (lets say 60)
- Enable Frame generation
- Duplicate Real frames cap (you cap 60, it shows 120)
The frame cap is not ignored, frame generation works this way for game. is the perfect harmony of frame generation and cap frames.
If you want less fps drops, just take note of what's the real minium fps you get and stick the nearest possible to such number but never a higher number: example, if your minimum fps are 80 (on big hordes with lots of effects and particles on screen), don't cap at 90, instead cap at 60 fps and enable frame generation aaaand Tadaah! now you have very stable 120fps
it may drop or increase 2 frames per moments
In practice, frame generation doesn't double your FPS. With FG off, my FPS is about 80, and goes to around 120 with it on.
Guess I'll just use RTSS to limit FPS cap.
Took them months to finally implement frame gen and they still couldn't do it properly.
Look at how your FPS drops when you open the menu or if you use the battle barge mission selector.
You must be bottlenecked if your frames keep dropping. With frame gen on I set a 60fps cap and it stays at 120fps and never dips even in intense action.
As I said, FPS drop happens "when you open the menu (Esc) or when you use the mission selector". Two places that are certainly the opposite of intense.
Feel free to check yourself.
I have numerous times. The gpu load increases but 0 dropped frames or even a fps stutter.
Like I said your pc is bottlenecked either cpu not able to fully utilize the gpu or the gpu is at max.
It's super clear there is some frame generation bug at least on certain machines, that causes frame gen to not work during menus.
I can confirm this issue is still present, FG works fine until you scope your weapon or press tab to see objectives - then it drops to your base fps from which FG is calculated, fps-cap or no cap, this sucks.
It is interesting that with Losless Scaling program this is a non-issue - Frame Generated fps stays the same no matter what.
They need to fix Nvidia's FG implementation in this game.
playing on RTX4070 + i5-11600KF + 144Hz monitor
Same stable fps with DLSS FG 120limited
Looks like some global/nvidia settings are overwriting your ingame stuff since update, or other way around?
I have a solution :) (also if you don't want to use Lossless Scaling program, see above)
If you want consistent framerate with the in-game Frame Generation, without it dropping to base framerate when scoping, or when in menus, you need to do the following:
Cap your framerate via RTSS instead of using the in-game cap, but first enter RTSS -> setup -> general and set 'enable frame rate limiter' to "NVIDIA Reflex" - this needs to be selected so that RTSS does not induce input lag when capping framerate.
Adittionally i have "Enable passive waiting" ticked-off, but i don't know how much that helps.
Works also in Cyberpunk (noticeable less input lag when capping frames via RTSS instead in-game. The in-game cap also breaks immersion - f.ex. 45 cap in order to achieve 90, will still drop down to 45 in menus, unless you cap frames via RTSS)
Enjoy :) works for me at least... and i have HPET turned off in windows btw.
This is very interesting indeed, so RTSS defaults the framerate limiter to "async" mode, but I'm guessing with many games using Frame Gen these days I should change it to "Nvidia reflex" then (since most games using FG auto enforces Reflex), so the issue of FG implementation can be consistent.
Your "Enable passive waiting" to OFF idea is also a godsend. You see in CP2077 I limit my FPS with RTSS, but for some strange reason the FPS always drops below what I set it to even though it shouldn't. For example, without a cap my game is always 110+ FPS. Therefore, if I implement an 80 FPS cap using RTSS, I should *never* see it drop below 80, yet it often does and it introduces these annoying little stutters.
Curious by what "Enable passive waiting" does, I googled and lo and behold, I found this https://forums.blurbusters.com/viewtopic.php?t=10531
With FSR FG, I have not experienced any such problems.
Maybe the HAGS cause this?