Blur Busters Forums

1000WATT wrote: ↑

04 Oct 2020, 10:31

speancer wrote: ↑

04 Oct 2020, 09:21

Just to let you know, I am especially curious how Reflex behaves in non-GPU-bound scenarios, so I'm looking forward to seeing your test results. I guess them results would give me the ultimate answer whether Reflex is completely useless for me or not, as I am never GPU-bound in my competitive play, my average framerate is 320-340 fps in competitive match with estimated average GPU usage between 35-40% (RTSS measurements).

Yes, it is interesting.
average GPU usage between 35-40%. Not an indication that the game is not tied to the GPU. With a GPU load of 30% and a heavy load on the memory of the video card, you can get delays above 300ms.

Video memory load is also low in my case, I checked it now. VRAM usage is just 1.1 GB max (out of 6GB of my GTX 980Ti), GPU load about 25-40%, average use would be around 30% (nothing too exact). Anyway, I'm surely not GPU-bound here at all.

speancer wrote: ↑

04 Oct 2020, 10:25

Are you able to estimate when would your Reflex and LLM-for-CS:GO test results come up?

I honestly have no idea at the moment. Nvidia is waiting on a second batch to be manufactured. All I know is I'm on that list. Rough ETA for delivery I was given is sometime this month.

Once received, I have to do some off-the-record testing to ensure I'm getting good data and performing best practices, but once I get the process down, everyone here can expect a semi-regular output of results in a variety of scenario and games.

Also, as a disclaimer, photodiode testing is limited where no sync is concerned (tends to equalize the differences between sync and no sync), so I will primarily be focusing on testing sync or no sync scenarios against secondary settings (like LLM, HAGS, Reflex, FPS limiters, etc), and not against each other.

jorimt wrote: ↑

02 Oct 2020, 12:30

blackstorm82 wrote: ↑

02 Oct 2020, 12:15

If it's not bound to the gpu, is it correct that the reflex doesn't work either?

Reflex eliminates the render queue. In GPU-bound situations, the render queue becomes saturated. In non-GPU-bound situations, the render queue is typically already near empty or empty.

blackstorm82 wrote: ↑

02 Oct 2020, 12:15

[144HZ]
GSYNC ON + VSYNC OFF
141 FPS CAP GPU 50%-70%
REFLEX ON+BOOST
-------------------------------
Reflex doesn't help in this situation, right?

Right.

blackstorm82 wrote: ↑

02 Oct 2020, 12:15

[144HZ]
GSYNC ON + VSYNC OFF
280 FPS [NOT CAP] GPU 95-99%
REFLEX ON+BOOST
95-99% Is it only turned on with a similar behavior to the low-latency mode?

When enabled, Reflex is "turned on" whether your system is GPU-bound or not. But since it removes the render queue, how much it reduces input lag depends on how full your render queue would be if Reflex was not enabled.

Reflex is a replacement to LLM. LLM only reduces the render queue. Reflex removes it.

LLM - ON/ULTRA
MPRF - Render queue "1" limit

REFLEX ON/BOOST
MPRT - Render queue "0" always

Can I think this way?

blackstorm82 wrote: ↑

06 Oct 2020, 13:15

LLM - ON/ULTRA
MPRF - Render queue "1" limit

REFLEX ON/BOOST
MPRT - Render queue "0" always

Can I think this way?

Yes.

Are there other benchmarks for reflex other than this fortnight one and this?

I think NVidia might be trying to pass this off as better than it really is and I'd like to see some more hard numbers.

Here's the thing:

Having 2 separate factories (CPU / GPU) for processing frames that are misaligned clearly leads to bad outcomes. Reflex addresses this by aligning the CPU factory just before the GPU one in cases where the GPU is the bottle neck. This takes care of some of the problems. But, and this is the issue I think NVidia is all too happy to gloss over in their marketing talk, the overall latency is still greater than CPU time + GPU time because you are delaying the CPU from starting to work on the task.

Here's an example with numbers:

In a GPU-heavy game the CPU frame processing time is 0, and the GPU frame processing time is 1 second per frame. At t = 0 the GPU start working on frame A. At t = 0.1s the user pressed the mouse button. With Reflex, the CPU will wait until just before t = 1 to start calculating frame B where the input can be taken into account, then at t = 1 the GPU will start processing frame B, and at t = 2 frame B can be displayed on screen. Total latency is 1.9s, which is significantly longer than CPU processing time + GPU processing time.

Without Reflex? The button press would still be displayed at t = 2, and Reflex had no effect.

In one sense the render queue has disappeared. But in another sense it merely moved to the front of the CPU processing.

From ignorant. What would be the best setting on Fortinite Competitive with DX12 (240hz)?
(Gpu 50% - Cpu 60%)

G-sync: ON
V-sync: OFF
LLM: OFF
Pre-rendering Frame: 0
Reflex: ON +Boost
Limit FPS in game: 237

There is something wrong?

When you are posting using VSYNC are you using regular VSYNC or VSYNC-Fast? for 144 and 240hz?

Hey guys,

I am still not sure after reading this, whether we should do some changes in Valorant in regards to the article for Optimal G-Sync settings.

I have:
240 Hz G-Sync Monitor
RTX 2080

Current settings:
LLM: ON
G-SYNC: ON
V-SYNC: ON
Frame Rate Limit: 237
NVidia Reflex: OFF


However, after reading this, it seems that Reflex should be ON and Max Frame Rate set to cca. 222 (just below 224, which is auto-set when Reflex is ON) ?
Also if you have Reflex ON do you se LLM to OFF?

Got confused here.

NIghtcorey wrote: ↑

28 Mar 2021, 03:32

I am still not sure after reading this, whether we should do some changes in Valorant in regards to the article for Optimal G-Sync settings.

My optimal G-SYNC settings were never directly intended for competitive shooters, they were intended for G-SYNC, which only has one optimal no-tear, low-lag single frame delivery configuration: G-SYNC on + V-SYNC on + minimum -3 FPS limit of current max refresh. So if you're using G-SYNC for comp shooters, and want the lowest lag no-tear method possible, that's still the most optimal setup.

Settings involving the pre-rendered frames queue, such as LLM and Reflex, were never directly related to G-SYNC input lag, and cause separate lag via the render queue that you'd get in any GPU-bound scenario, with or without G-SYNC. I only ever added recommendations for such settings to my Optimal G-SYNC settings upon repeat request for completion's sake.

If your GPU isn't maxed in Valorant, and your system can sustain the framerate at the set FPS limit, neither LLM nor Reflex will do much of anything until your GPU maxes out and your framerate drops below your set limit.

Since it's very easy to reach very high framerates on most configurations in Valorant, my assumption is the devs added Reflex for 1) marketing purposes, and 2) for situations where users are playing with G-SYNC off + VSYNC off + uncapped FPS, so when they reach very high framerates on a moderately performing PC, render queue input lag won't increase when/if the GPU usage maxes out.

As for LLM vs. Reflex, the latter is intended as a complete replacement to the former, so if you have Reflex enabled, it entirely overrides LLM, regardless of what it's set to.