Blur Busters Forums

New Viewsonic XG2431. OSD buttons not working: https://www.youtube.com/watch?v=QEXBhmIHBhY

Made at the request of Viewsonic support.

So it seems like PureXP > GSync in terms of FPS games. I wasn't aware, good to know I have it enabled.

hi , it seems that i cant get onto viewmode of my settings , anyone facing the same issue?

At the same time i have a problem that i cant select PureXP in my settings

An update: I've received a replacement XG2431 from Viewsonic via my Australian retailer Scorptech. The OSD buttons are now working fine! All of the buttons work easily. Good service from Viewsonic and Scorptech.

Chief Blur Buster wrote: ↑

30 Oct 2022, 17:31

woland wrote: ↑

25 Oct 2022, 15:07

Thank you for the detailed explanation. I'm interested in lowest lag PureXP, so I'm using it without any sync tech. Additionally my game of choice (Apex) cannot run a frame rate higher than 300 fps. I've managed to get my FPS consistently above 240, hence the question of whether I should lock at 240, 239.76, or something else entirely (or if it doesn't matter )?

Right tool for right job.

VSYNC OFF is good if you can just spray brute framerate (e.g. 300+fps) in competitive games like CS:GO. Strobe backlights can have a perceptual "aim stabilizing" effect (less motion blur during gun recoils) which is why some vendors call strobe backlights an "Aim Stabilizer", and it works fine at unsynchronized frame rates.

However, some games stutter so much and strobing can amplify jittering (strobe jitters). So framerates that fluctuate near Hz (e.g. 200-250fps) can look extremely jittery. For that, I recommend lowering refresh rate and using RTSS Scanline Sync to improve your aiming. framerate=Hz may have a smidge higher latency, but there's far less latency volatility.

...

Let me rephrase my question: if I mostly care about latency and am using blur reduction for the aim stabilizing effect (for competitive esports), doesn't it make more sense to just cap fps at refresh rate rather than use scanline sync? Blur reduction works better when hz=fps, but why should I do that with scanline sync for my use case? It seems like screen tearing is mostly just ugly and doesn't have an impact on aim/clarity, meanwhile Fr33thy's tests showed about a 4ms input lag difference between scanline sync at 360 fps VS just capping fps at 360fps.

Am I missing something?

Thanks again for your insight.

woland wrote: ↑

12 Dec 2022, 10:59

It seems like screen tearing is mostly just ugly and doesn't have an impact on aim/clarity

Depends. If you're doing things that are jitter-sensitive, then random tearline jitter above/below your eyegaze adds an amplified stutter effect as you're rapidly seeing a lagged/lesslagged frame in super-rapid succession (and sometimes a highly variable latency)

woland wrote: ↑

12 Dec 2022, 10:59

meanwhile Fr33thy's tests showed about a 4ms input lag difference between scanline sync at 360 fps VS just capping fps at 360fps.

Depends on your goals, but for FPS aim-stabilization, in-game cap is usually fine. But beware of the sawtooth latency effect of a slowly-rolling tearline. Frameslices are individual latency gradients. Lag is lowest right below a tearline, and lag is highest right above a tearline. Stabilizing tearline = stabilizing latency.

But [0..1/360sec] latency variance of an unsynchronized imperfect 360 cap (one may be 359.9365 other may be 360.11231234) But you can simply force the tearing to be randomized instead, to improve latency consistency in an unsynchronized VSYNC OFF. For example, say cap 503fps or 517fps or whatever, and you might get slightly better latency-variance results.

If you want framerate=Hz AND latency consistency (no latency sawtooth graph), you need RTSS Scanline Sync.

Do you prefer consistent latency or do you prefer lowest absolute latency?

Chief Blur Buster wrote: ↑

12 Dec 2022, 16:02

Depends. If you're doing things that are jitter-sensitive, then random tearline jitter above/below your eyegaze adds an amplified stutter effect as you're rapidly seeing a lagged/lesslagged frame in super-rapid succession (and sometimes a highly variable latency)

I'm still determining whether the distraction of the tearline adds more latency to my reaction time than the latency inherent to scanline sync.

Chief Blur Buster wrote: ↑

12 Dec 2022, 16:02

But [0..1/360sec] latency variance of an unsynchronized imperfect 360 cap (one may be 359.9365 other may be 360.11231234) But you can simply force the tearing to be randomized instead, to improve latency consistency in an unsynchronized VSYNC OFF. For example, say cap 503fps or 517fps or whatever, and you might get slightly better latency-variance results.

Unfortunately Apex cannot run at 500 fps, if I don't use scanline sync I really do have to match fps to hz rather than brute forcing my way with high fps.

You mentioned lag is lowest right below a tearline; does the value I choose for moving the tearline in scanline sync affect latency?

> You mentioned lag is lowest right below a tearline; does the value I choose for moving the tearline in scanline sync affect latency?

Theoretically yes. So in a FPS game you might scanline sync to about 1/3rd of the way from top edge of the screen, because most enemies are along the centerline and at crosshairs, and that is the band of lowest lag.

But in Apex Legends, enemies can be all over the screen, top edge, bottom edge, center, so you may prefer to keep tearlines above top edge. Some Apex players switch to 180Hz-240Hz (instead of 360Hz) and enable strobing combined with Scanline Sync, because the reduction of motion blur can speed up reaction time enough (you can see everything while scrolling = react faster mid-scroll, because you saw something before you ended your scroll/panning = react sooner). I know some BenQ 240Hz users use 180Hz RTSS Scanline Sync with DyAc+ in Apex -- it is amazing (no blur, no tearing, no stutter, no jitter) with the perfect TestUFO-smooth pans.

Better if you QFT it (e.g. 180Hz refresh cycles in 1/240sec or 240Hz refresh cycles in 1/360sec, via ToastyX CRU Vertical Total Calculator) to reduce strobe lag. You need slight amount of refresh headroom for larger VBI to simultaneously (A) QFT to reduce strobe crosstalk and (B) QFT to have bigger VBI to hide tearline between refresh cycles.

Does anyone know if this photo is BenQ official or no?
Source: https://me.ign.com/en/pc/203936/feature ... ts-monitor



It's confusing because from description it sounds like IGN made it but it has BenQ logo in top corner and stuff.

Anybody know what Pure XP and overdrive settings are ideal for PS5/Xbox 120hz?