I do not believe this is accurate, prerendered queue is 0 on Ultra, thus stuttering if CPU cannot keep up. Didn't see framerate limited either, was still at 60 for me with VSync.
Apex Legends, Battlefield V, Forza Horizon 4, Strange Brigade and World War Z now run even faster, retro and pixel games look better with Integer Scaling, modern games look sharper with NVIDIA Freestyle, and input responsiveness can be improved with our new low latency modes.
www.nvidia.com
Many G-SYNC input lag tests & graphs -- on a 240Hz eSports monitor -- via 2 months of testing via high speed video!
blurbusters.com
Low Latency Mode* Settings:
*This setting is not currently supported in DX12 or Vulkan.
- If an in-game or config file FPS limiter is not available, RTSS is prohibited from running, a manual framerate limit is not required, and framerate exceeds refresh rate:
Set “Low Latency Mode” to “Ultra” in the Nvidia Control Panel. When combined with G-SYNC + V-SYNC, this setting will automatically limit the framerate to ~59 FPS @60Hz, ~97 FPS @100Hz, ~116 FPS @120Hz, ~138 FPS @144Hz, ~224 FPS @240Hz, etc.
I trust these guys with their 1000 fps camera, nerding the crap out of vsync,gsync etc
As far as I understand all this gpu, buffers, scanout etc stuff, there is no "0" pre-rendered frames. There simply needs to be a buffer where the image is stored in.
However by limiting the frame rate below the vsync refresh rate you can keep this buffer from becoming full, which would enable the cpu to queue frames in the first place.
If you keep the buffer being stuck between "empty", which is the stutter you'll experience with ultra and "almost full", there won't be a queue.
However with 1 fps below hz you'll get 1 frame be displayed twice once per second.
If you limit 0.5 fps below hz, you'll get that 1 frame stutter every 2 seconds.
Anyway, I did the following just now:
rtss limiter off, content manager fps limiter off.
AC vsync off.
Nvidia panel:
vsync on, gsync active, low latency first at "on", then quit the game, put it to "ultra" and go on track again.
I made sure that I reached about 260 fps when not being in fullscreen mode so there won't be any bottleneck.
Hitting alt+enter in AC would go into fullscreen again and trigger nvidia vsync.
I put afterburner refresh cycle to 100ms and used the inbuilt benchmark for 45 seconds while being in fullscreen and not touching anything.
Here are the results:
Low Latency = "on":
15-06-2020, 21:29:53 acs.exe benchmark completed, 4483 frames rendered in 45.891 s
Average framerate : 97.6 FPS
Minimum framerate : 92.6 FPS
Maximum framerate : 99.8 FPS
1% low framerate : 59.0 FPS
0.1% low framerate : 53.0 FPS
Low Latency = "ultra":
15-06-2020, 21:31:50 acs.exe benchmark completed, 4382 frames rendered in 45.282 s
Average framerate : 96.7 FPS
Minimum framerate : 93.6 FPS
Maximum framerate : 97.2 FPS
1% low framerate : 79.6 FPS
0.1% low framerate : 55.9 FPS
To be honest I have no idea how the minimum, 1% and 0.1% happened, guess while saving the benchmark or something like that. Maybe I should run this for 10 minutes...
Anyway you can see that the maximum peak got limited by "ultra" about 2.7 fps below "on". The average is about 1 fps lower.
For me this indicates that blurbusters are right and that "ultra" introduces a limiter.
EDIT:
did one 10 minute run and one... well.. I forgot to stop it.. 26 minute run:
15-06-2020, 22:01:51 acs.exe benchmark completed, 60938 frames rendered in 613.344 s
Average framerate : 99.3 FPS
Minimum framerate : 96.6 FPS
Maximum framerate : 99.9 FPS
1% low framerate : 85.3 FPS
0.1% low framerate : 58.8 FPS
15-06-2020, 22:30:30 acs.exe benchmark completed, 160512 frames rendered in 1650.438 s
Average framerate : 97.2 FPS
Minimum framerate : 96.4 FPS
Maximum framerate : 97.2 FPS
1% low framerate : 97.0 FPS
0.1% low framerate : 96.9 FPS