Latest Nvidia Graphios Driver - Low Latency Option

[KillZoneGB]

I`ve just been playing with ultra-low latency, 2880X2880 Custom High VR Presets.

Seem`s a lot smoother, Don't know if its the driver or the SteamVR + WMR beta updates.

Haven't been in combat yet, that will be tested tonight.

Station, Surface, zipping around in supercruise and collecting DE EE mats all A-OK.

I7 4820K @ 4.3 GHz Water-cooled
32 Gigs DDR 3 @ 1600Mhz
I-Chill X3 Nivida 1080 @ Stock power plan.
WMR Lenovo explorer

Also tested out World Of Ships, 30ms ping 120FPS, so far CPU no strain on the pc

Anyhoo

Sorry for being too vague, it`s been a long night and I'm tired.
Good morning, and goodnight...

I`m out of here

 

[bapt33]

The low latency modes seem to work as advertised, though one would be hard pressed to notice the difference between 1 and 0 pre-rendered frames as far as input latency goes. I do see a mild frame rate hit to some more demanding areas in ED, but nothing serious. I wouldn't recommend the ultra-low latency/zero pre-rendered frames for anyone that is CPU limited.

You are tottally wrong, lower max pre-rendered frame is more cpu demanding cause cpu have to send new frame before the last frame in the buffer bein rendered by the gpu.
so if max pre rendered frame is 1, cpu have to render a frame as faster than a frame cycle (16.6ms for 60hz), then its more cpu demanding cause cpu have to be faster.
if max pre rendred frame is set to 3, cpu as more time (3 frame cycle = 49.8ms) to prepare a new frame, then its less cpu demanding, but add input lag cause the frame rendered is "old" due to 3 buffer frame queue.

 

[Morbad]

lower max pre-rendered frame is more cpu demanding

This is what I say in the post you've quoted. Why else would I recommend against reducing the queue size on CPU limited setups?

so if max pre rendered frame is 1, cpu have to render a frame as faster than a frame cycle (16.6ms for 60hz), then its more cpu demanding cause cpu have to be faster.
if max pre rendred frame is set to 3, cpu as more time (3 frame cycle = 49.8ms) to prepare a new frame, then its less cpu demanding, but add input lag cause the frame rendered is "old" due to 3 buffer frame queue.

Yes, though the buffer isn't guaranteed to be full.