Going by the images you posted, uncapped reflex doesn't seem all that better latency-wise when compared against gsync+vsync+reflex.tsarri wrote: ↑26 Jan 2026, 18:48Uncapped frames + Reflex is still king for latency in high fps games even if the difference becomes marginal at higher refresh rates. You don't have to believe me but it's what tests like this suggest. Regardless I don't think its that important when the difference is so small. I'm really wondering how Pulsar stacks up to ULMB2 though at lower refresh rates (75–200Hz). There should be a big improvement in theory but it seems to have some issues. Getting the XG27AQNGV tomorrow to test.
A latency reduction of 0.7 ms for a ~200 fps increment seems pretty weak and likely bottlenecked in some fashion, but I digress.
I couldn't answer you regarding the strobing, since I also haven't found any info about its behaviour when the frame rate is above the refresh rate. Nonetheless, basic VRR advice should apply. So, if are using a limiter, you must set it within the appropriate VRR range to prevent the display from reverting to standard vsync when near or above its max refresh rate. "gsync+vsync+reflex/ullm" already handle this automatically, and both RTSS and Special K will recommend you a similar value to stay within that range. There is no point in disabling vsync if you are staying within range, but you could do it for little to no benefit whatsoever and at worst, you might see occasional tearing.Alennartsson wrote: ↑26 Jan 2026, 14:293. If its not pulsing at 500+fps i should lock my FPS to 360FPS and it will start pulsing again, aka "4x effective motion clarity". Is it better to lock it to 360Hz with vsync: OFF than using vsync: ON and get 320~ FPS?
