Hello,
I got a question. I have a benq 2546 240hz monitor but my gpu dont show the 1280x960 resolution.
Whats is better? Lcd standar, lcd native or lcd reduced for 240hz and good clock?
LCD standar: 240hz / 259.201 kHz / 373.25 mhz
LCD native: 240hz / 237.125 kHz / 341.46 mhz
LCD reduced 240hz / 234.005 hHz / 320.12 mhz
Display scaling or gpu scaling?
Thanks!
CRU question 240hz
- Chief Blur Buster
- Site Admin
- Posts: 12146
- Joined: 05 Dec 2013, 15:44
- Location: Toronto / Hamilton, Ontario, Canada
- Contact:
Re: CRU question 240hz
Depends on your goals.
If you're wanting (A) strobing and/or (B) Quick Frame Transport benefits, then the largest vertical total is usually the best.
However, if you're using DyAc, sometimes you will want to use a lower refresh rate if reduced strobe crosstalk is a priority for your situation.
Now, if you're simply focussing on lowest latency VSYNC ON, much of this doesn't matter much and you can simply use reduced for maximum compatibility.
I've seen display scaling be better and I've seen GPU scaling be better. These days, it's much easier to use GPU scaling since NVIDIA Control Panel is easy to do and not all monitors supports 240Hz reliably at non-native resolutions. So it's often easier to piggyback on the standard 1080p timings and do 1280x960 within that using the GPU instead.
Some displays don't add scaling lag, while other displays do. In this case, the tables can turn (GPU scaling vs display scaling) on what is lower-lag in scaling.
Bottom line: Test the playfeel. Fine-tuned esports players will notice 1-refresh latency delays even at 240Hz.
This isn't felt directly but felt as a "I seem to be aiming more poorly" in tight-tracking situations and stop-mouse-on-target situations. (4ms mistime = 40 pixel overshoot/undershoot at 10,000 pixels/sec mouseflick). Especially if you benchmark yourself using a common aimtrainer app. What happens is you get a sudden scoring loss in your favourite aimtrainer (or ultrahigh-framerate competitive game) as your brain/body attempts to retrain itself to the cues of the new latency chain, before your scoring improves again without the aiming oversteer/understeer behaviour appearing from the unexpected milliseconds-of-lag change.
You might not feel the difference, but a small percentage of competitive players definitely feel a 4ms change in aiming (one refresh cycle of lag at 240Hz), so the easiest way without measuring equipment is to: "Try the modes yourself and go with what feels better in aiming".
If you're wanting (A) strobing and/or (B) Quick Frame Transport benefits, then the largest vertical total is usually the best.
However, if you're using DyAc, sometimes you will want to use a lower refresh rate if reduced strobe crosstalk is a priority for your situation.
Now, if you're simply focussing on lowest latency VSYNC ON, much of this doesn't matter much and you can simply use reduced for maximum compatibility.
I've seen display scaling be better and I've seen GPU scaling be better. These days, it's much easier to use GPU scaling since NVIDIA Control Panel is easy to do and not all monitors supports 240Hz reliably at non-native resolutions. So it's often easier to piggyback on the standard 1080p timings and do 1280x960 within that using the GPU instead.
Some displays don't add scaling lag, while other displays do. In this case, the tables can turn (GPU scaling vs display scaling) on what is lower-lag in scaling.
Bottom line: Test the playfeel. Fine-tuned esports players will notice 1-refresh latency delays even at 240Hz.
This isn't felt directly but felt as a "I seem to be aiming more poorly" in tight-tracking situations and stop-mouse-on-target situations. (4ms mistime = 40 pixel overshoot/undershoot at 10,000 pixels/sec mouseflick). Especially if you benchmark yourself using a common aimtrainer app. What happens is you get a sudden scoring loss in your favourite aimtrainer (or ultrahigh-framerate competitive game) as your brain/body attempts to retrain itself to the cues of the new latency chain, before your scoring improves again without the aiming oversteer/understeer behaviour appearing from the unexpected milliseconds-of-lag change.
You might not feel the difference, but a small percentage of competitive players definitely feel a 4ms change in aiming (one refresh cycle of lag at 240Hz), so the easiest way without measuring equipment is to: "Try the modes yourself and go with what feels better in aiming".
Head of Blur Busters - BlurBusters.com | TestUFO.com | Follow @BlurBusters on: BlueSky | Twitter | Facebook
Forum Rules wrote: 1. Rule #1: Be Nice. This is published forum rule #1. Even To Newbies & People You Disagree With!
2. Please report rule violations If you see a post that violates forum rules, then report the post.
3. ALWAYS respect indie testers here. See how indies are bootstrapping Blur Busters research!
