NVIDIA 174.74 (beta) drivers new 3D setting

[Einherjer88]

Hi!

But wouldn't it be more logical that there is, if even so, the same or less input lag?
Imagine the GPU is still rendering on one frame, with this setting to lets say 5, the CPU precalculates during this time in best case this 5 frames and they're queed up right ready for GPU to take them. For GPU there would be no change, cause as soon as it finishes rendering the one frame, it takes out the first of the 5 already from CPU precalculatet frames to render this frame.
There would still be 4 more allready calculated frames in que and cpu just needs to calculate one more frame for filling up que to 5 and then has time to play chess against ram or something else...
This cenario could be in a game with not much geometry (work for CPU) but much effects, lightsources,.... (much to render on one frame for GPU when got CPU geometrysetup) where GPU needs in this example 4-5 times longer for finishing one frame than the CPU.

So where would there be more input lag? Because if the GPU needs so long time to calculate one frame it should make no difference if there are waiting 2 or 4 (depending on new driver setting) more frames in CPU precalculated que....

 

[BenSkywalker]

So where would there be more input lag? Because if the GPU needs so long time to calculate one frame it should make no difference if there are waiting 2 or 4 (depending on new driver setting) more frames in CPU precalculated que....

You set off a grenade in front of you then go to spin fast and grab the guy behind you. Your GPU bogs a bit due to the smoke- say it goes down to 20FPS, your CPU meanwhile ques up the next 5 frames, you go to spin and resume shooting as soon as the grenade goes off. So, you hit the brief framerate drop but then need to wait for the que to clear, even if your FPS was right back to 60FPS your ability to interract with the game would be effectively 12fps(how long it would take to dump the frames in que). If you didn't have those frames qued, as soon as you came out of the framerate dip, you would be right back to the higher level of performane.

Queing up frames prolongs dips in performance as far as input responsiveness is concerned.

 

[emilyek]

Reducing pre-rendered frames to 1, from 3, is an Oblivion tweak that was popular when that game was first released, which should give you some idea of how long it's been an option to 'fix' GPU intensive games.

As its name suggests, it stops the frame buffer from being spammed. 'Lowering pre-rendered frames's primary job is to reduce mouse lag (as well as a pause-y, jerky image while moving), since the frame buffer can appear to spam and then un-spam the display.

AFAIK it doesn't improve FPS, only how smoothly the frames are presented-- at least that's how it worked(s) in Oblivion.

The current Nvidia control panel warns, correctly-- I assume, that lowering the setting will actually lower FPS.