benq xl2411z hz overclock

[turu]

Hi. Can i overclock to more than 144hz ?

Maybe 150hz at 1024x768 (or more if i can?)

I trying with std timings but got "out of range" problem, maybe special timings or whateva?

[falkentyne]

(11-11-2014 02:12 AM)turu Wrote:  Hi. Can i overclock to more than 144hz ?

Maybe 150hz at 1024x768 (or more if i can?)

I trying with std timings but got "out of range" problem, maybe special timings or whateva?

1024x768 doesn't matter, they are all downsampled 1920x1080 resolutions anyway.
144hz isn't even directly supported at normal timings. 144 hz requires reduced timings, so 150hz: no way. 144hz won't work with standard timings. Highest possible with standard timings is ~128-130, afaik.

Someone managed 146 hz with reduced timings.

If you're trying to get less motion blur, you should be using blur reduction anyway.

[turu]

i know i should use blur reduction, but i've got V1 firmware and haven't got second computer/laptop to uprage to V2 (and im linux nubblo :<)

[turu]

When i do 1024x768 @ 129hz in OSD i've got "1024x768 @ 120hz" @ std timings. (I creating resolution in nvidia control panel).

But when i create 1024x768 @ 129hz at CVT REDUCED BLANK, in OSD i've got "1024x768 @ 100hz"

This is OSD bug or that overclock don't work?

[falkentyne]

(11-24-2014 05:46 PM)turu Wrote:  When i do 1024x768 @ 129hz in OSD i've got "1024x768 @ 120hz" @ std timings. (I creating resolution in nvidia control panel).

But when i create 1024x768 @ 129hz at CVT REDUCED BLANK, in OSD i've got "1024x768 @ 100hz"

This is OSD bug or that overclock don't work?

Not an OSD bug. But rather the monitor getting timings it's not used to. When this happens, the monitor (internally) may use a different backlight pulse width than the one for that refresh rate (this is usually used and related to strobing only).

The OSD reports what the backlight pulse widths are set for (usually the refresh rate = pulse widths, but there are exceptions). Most of the 'issues' if the backlight pulse width (what the OSD reports) being different than the refresh rate selected, cause issues with blur reduction and strobing, particularly if single strobe is turned off.

Some of the problem are when using lower resolutions for an LCD, and LCD's are designed to be run at native resolutions, or CRT resolutions need to be used instead of LCD standard. So some strange things can happen if you create lower resolutions (below native) and you don't use CRT automatic timings.

Also I think CVT Reduced is for 144 hz (or refresh rates close to 144hz) as they reduce the vertical total and other timings.

Anyway:
Example, and this on a 2720Z:
1920x1080@85 hz (custom refresh rate) = perfect (OSD reports 1920x1080@85 hz)..
1024x768@85 hz (custom refresh rate)= "out of range" error--yet you still get a perfectly displayed screen anyway!
1920x1080@80 hz: 80 hz (TestUFO runs at 80 fps vsynced correctly), but the monitor doesn't like this strange setting and switches to 60hz backlight pulse widths. OSD reports 1920x1080@60 hz, at 80hz refresh rates.

Ordinarily this would be no problem, however the different pulse widths (without a different vertical total) cause blur reduction to act weird at 1920x1080@80 hz (the pulse widths are for blur reduction enabled. Blur reduction disabled just uses default refresh rate and pulse widths (for strobing) are not used):

Single strobe on: works fine. (60hz pulse widths used), custom settings work.
Single strobe off: STILL single strobes, since double strobe is only for 75 hz and lower, but the crosstalk settling error pulse starts off in the center of the screen and strobe duty/strobe phase settings do not work. (even though with VT tweaks active, 100hz and 120hz also report 60hz, they respond properly to strobe changes with single strobe "off".

1600x1200 @ 100 hz custom (LCD Automatic (manual)
OSD shows 144 hz. Polarity is ++, monitor using 144 hz backlight pulse widths. TestuFO@ 100 fps:
Strobing is completely utterly broken: a complete blurry mess (strobe is activated but looks worse than strobing disabled).

1600x1200@100 hz custom (CRT Automatic):
OSD shows 120hz
Polarity is +- (or -+)
Strobing works again, even though its using the 120hz pulse widths.

So if you get strange results with lower resolution detailed res settings, try using a CRT setting instead of a LCD one.