BENQ XL2720Z 27" of goodness :) [Version 2 firmware is good]

[masterotaku]

What were the settings in CRU (or Nvidia CP) that you used for 120hz?

I've posted my settings somewhere else, but I'll write them in text, in the same order as they appear:

1920 1080
48 3
32 5
2080 1500
+ -
180KHz 120Hz Pixel clock: 374.4000 MHz

Same settings for 100Hz and 85Hz, but obviously the last line (the one with frequencies and pixel clock) changes. Lower frequencies needed different settings.

1500/120hz vertical total is WAY too high and just makes the monitor go out of sync at 120hz (pixel bandwidth is over 350 MHz, 330 is the driver limit unpatched) while its either 312mhz (will always work) or 330 MHz bandwith (may need the patch) at 100hz (depending on if you used 2080/1500 (for 24") or 2200/1500 for 27". You may still need a patch if it's 330.00 MHz at 100hz.

Are you sure that 1500 is actually working? Check the pixel bandwidth; if it's higher than 329 MHz, your VT's probably didn't work at all, as the driver ignored them (I'm suspicious because there should be no way you got VT 1500 for 120hz). You need to use toastyX's pixel clock patcher (on his forum) to have >330 pixel clock on AMD or Nvidia cards (there's a patcher for each one).

I'm already using ToastyX's Pixel Clock Patcher. At 120Hz it doesn't skip any frame, and the strobe is perfecly synchronized. I think I'd have noticed anything strange if that weren't true. The double image is hidden almost completely, but my complaints about overdrive artifact still remain at all frequencies.

[Falkentyne]

Ok, thanks masterotaku,

I verified that these settings with the v1500 total DO work at 120hz on the 2720Z, but only if you use the 24" settings.

The 27" screen uses a 2200 default horizontal total, instead of 2080 (it also uses 88/4 and 44/5 defaults for porch and sync), but since the panels are made by the same manufacturer, the 24" timings (2080 instead of 2200, and 48/3, 32/5) seem to work fine on the 27".

2200 works at 100hz also, although that makes the pixel bandwidth jump from 312 (2080) to 330 (2200) so I'm using 2080/1500 for 100hz also.

And the V1500 tweak works even better than the V1350.

[Chief Blur Buster]

And the V1500 tweak works even better than the V1350.

That's great to hear that the V1500 tweak works reliably now!

For Geeks: According to my calculations, the V1500 tweak creates a large 2.3 millisecond blanking interval at 120Hz. (This is because only 1080/1500ths of a refresh cycle is spent actually refreshing the panel (during a 1/120sec = 8.3ms cycle). So 6ms of actual panel refresh time and 2.3ms pause between refreshes. This allows most of the 1ms LCD GtG to complete between refreshes, essentially hiding most of the strobe crosstalk in the blanking interval.

I wonder if it's possible to use even larger blanking intervals during lower refresh rates (e.g. VT1600 at 100Hz, or VT2000 at 60Hz).

If you used ToastyX CRU to create this, you could export a .bin file for other people to import into their copy of ToastyX CRU.

[Falkentyne]

Ok here's the CRU settings I used.

I had to adjust all the 27" timings to 24" to make sure V1500 worked at 120hz.

I also removed a few non working/glitched timings from the default settings, that give improper cable errors or swimming pixels (1024x768@120 nonscaled=swimming right edge pixels, 1280x1024, 100/120='improper cable", 1440x900=same, etc.
This seems to be a manufacturer issue, as this exact same issue (including the 1024x768@120 default timing) does the same thing on the VG248QE, as well as the 1280x1024's cable errors, 1440x900, etc). The VG248QE only has 60hz timings for these though by default. (this is on an AMD card; YMMV with a GeForce).

Also put in 1920x1076@60 so you won't be forced into 50hz in buggy games like Crysis (which use the lowest available refresh rate)

This does not remove the 50 hz setting, which can cause the 27" to reset itself if you try to enable single strobe mode. I can't seem to remove 50hz at all; it's easily removable in the vg248QE by unchecking everything and only adding detailed resolutions but doesn't seem to work on this one. 50hz strobing apparently works on the 24" but not the 27" screen (someone needs to test that on a Geforce); 60 hz is fine, though..

[Falkentyne]

And the V1500 tweak works even better than the V1350.

That's great to hear that the V1500 tweak works reliably now!

For Geeks: According to my calculations, the V1500 tweak creates a large 2.3 millisecond blanking interval at 120Hz. (This is because only 1080/1500ths of a refresh cycle is spent actually refreshing the panel (during a 1/120sec = 8.3ms cycle). So 6ms of actual panel refresh time and 2.3ms pause between refreshes. This allows most of the 1ms LCD GtG to complete between refreshes, essentially hiding most of the strobe crosstalk in the blanking interval.

I wonder if it's possible to use even larger blanking intervals during lower refresh rates (e.g. VT1600 at 100Hz, or VT2000 at 60Hz).

If you used ToastyX CRU to create this, you could export a .bin file for other people to import into their copy of ToastyX CRU.

Would this add any noticeable input lag at 100 hz?

[masterotaku]

I wonder if it's possible to use even larger blanking intervals during lower refresh rates (e.g. VT1600 at 100Hz, or VT2000 at 60Hz).

If you are wondering why I didn't use VT1500 at all frequencies, it's because I get either a "Out of range!" error or a black screen. Higher VT values at 60Hz made it do double strobe instead of single strobe (and also some cable errors).
At 120, 100 and 85 Hz, I've tried values higher than VT1500, but it always goes out of range. Well, I still haven't tried tiny increments like 1505 or similar, because I tried in 25px increments. I've upgraded yesterday, I'll need more time to find absolute max values .
The general rule is: the lower the Hz, the lower the VT I could use. Sorry, but VT2000 at 60Hz doesn't seem possible. If someone can get greater values than mine, please tell us.

PS: I still couldn't find correct values for a single strobed 50Hz mode. Seems impossible with my monitor.

[Falkentyne]

What happens when you try 50 hz (including at the default 50hz in your video driver settings, without a vertical tweak?)? the monitor gets extremely bright, with no strobe active, and/or then hard resets? (as if you powered it off and on? if the brightness is over 30, it will cycle reset).

BTW I see your strobe phase settings. You go past what the blur reduction tool allows you to go past (047 is the max I think?). You're basically flipping the crosstalk band to the "other end" of the monitor (bottom instead of top), its sort of like repositioning that solid dark band on analog TVs. But going to the point where the screen gets dimmer and then almost completely blacks out seems like damage can result (chief? is that possible?). I already saw the non working 50hz single strobe setting cause the monitor to reset (if the double brightness gain from the non working strobe is too high...definitely have to be careful the backlight doesn't get damaged...)

[masterotaku]

What happens when you try 50 hz (including at the default 50hz in your video driver settings, without a vertical tweak?)?

I'm not at home right now, but I think it didn't strobe at all. Then I made a custom resolution with a very little change in VT, but it resulted in a double strobe. I'll try more values this evening.

Edit: I've found working values for 50Hz with VT1350.

1920 1080
48 3
32 5
2080 1350
+ -

Yesterday, I thought it was strobing wrong, but today I noticed that changing the strobe phase to high values makes the double image disappear. The bad side is that I couldn't hide the strobe crosstalk completely. As I increase the strobe phase, the double image goes down, but only half of the "bad zone" disappears at the bottom of the screen, because I hit the max value of strobe phase.
It flickers a lot. 60Hz looks flickerfree in comparison .

PS: VT1260 at 60Hz works for me, with CVT timings.

[Komraderu]

Benq XL2411T
vs
benq xl2720z

http://forums.blurbusters.com/viewtopic ... 5141#p5141

[GitDat]

phpBB [video]

I AM COMPLETE!!! All 3 monitors at V2 firmware!! READY FOR WAAAAARRRR!!

Special thanks to the Chief for all of his assistance!