Ok let's see if I can write this up properly.
First you will need the pixel clock patcher if you intend to test this over DVI. I think its best that you test this over both DVI and DP, just in case the VT tweaks work over DVI but not over DP.
http://www.monitortests.com/forum/Threa ... ck-Patcher
There's an Nvidia one also, although no idea why someone would use this monitor over a gsync one on an Nvidia card, especially with the half working blur reduction at the moment.
Then you need the toastyX CRU utillty
http://www.monitortests.com/forum/Threa ... tility-CRU
There's a driver restarter there also for testing resolutions without rebooting. Unfortunately, the Nvidia control panel allows you to instantly test a resolution without applying it. AMD's CCC has a far more limited, almost worthless version of this, limited to just some custom HDMI type refreh rates, so whenever you try a custom resolution, it's best to set the video drivers to 60hz or 144hz first. (you may not be able to do 144 hz over DVI on this monitor, only over displayport, but 120hz over DVI WAS tested successfully with the pixel clock patcher on this monitor)
Even though you are going to test both DP And DVI, patch the driver anyway (you can always unpatch it).
Run the driver restarter after patching (part of CRU).
Now comes the fun part.
First, set the monitor to 60hz (or 144 hz if on displayport).
Then create a new custom "manual" resolution that should already be shown as 2560x1440, and enter the refresh rate at 120 hz, without changing the other values.
The horizontal and vertical totals shown should be the defaults for that monitor.
You can double check by also creating a 100hz manual resolution and seeing if the HT and VT (horizontal and vertical total) are the same.
On the 1080p screens, the default horizontal total is 2200 and default vertical total is 1125. This will obviously be much higher on the 1440p monitor.
Do not save or exit CRU yet (just keep it open; the custom res should not be in the registry yet).
Now, here comes the hard part.
First, open this test and open it as full screen (F11).
http://www.testufo.com/#test=photo&phot ... &height=-1
enable blur reduction and set the refresh rate to 120hz (it should be using the default settings still).
Go to the blur reduction OSD settings and set the "Area" to 000. Make sure it is NOT set to 100.
Now, as far as the Intensity, this value is different than on the older blur reduction monitors, but it serves the exact same purpose: controls persistence (dimmer screen=lower persistence=more blur reduction, smoother motion but less brightness).
On the older Z series (Before the XL2430T), this was called "Strobe Duty" and the lower the strobe duty, the dimmer the screen and the more blur reduction you would have. The dimmest value was strobe duty 001, which, at 144hz refresh rate, would have a persistence as low as 0.08 ms (!). That's very dim.
On the XL2730Z, either Intensity 001 or intensity 025 is the dimmest value, I'm not sure which. Find out which one makes the screen the dimmest, then raise (or lower) the Intensity by 6 points. Make sure OSD brightness is set to 100% so you can actually see stuff.
Now in this test:
http://www.testufo.com/#test=photo&phot ... &height=-1
Pay close attention to the strobe crosstalk you may see at the top and especially at the bottom of the screen. . Try changing the area up and down from 0 to 100 (you are doing this BEFORE making CRU changes). You should notice a big double image thick blurry mess of UFO's in a band area, move up and down the screen. I Think you will notice that above the band and below the band, it seems that the UFO's move "ahead" or "back" one frame (this is true); having an Area of 100 puts everything ahead one frame and improves input lag by exactly 1/(current hz), but don't worry about that now. After you have fun seeing the effect on the frame position, set the area back to 000 and leave it there.
Now the fun part.
Set the refresh rate back to 60 (or 144 hz), do not leave it at 120hz, you don't want an out of range error by leaving the current refresh rate as the one you are editing
Go to the 120hz custom resolution, in CRU of 2560x1440 that you made, and increase the vertical total by 100.
Save it and exit CRU.
Restart the driver.
Set the CCC to 120hz. If you get a valid signal, apply it and go back to the testUFO page.
Check the position of the strobe crosstalk around the bottom of the screen.
It should have moved LOWER by 100 vertical rows of pixels.
If you didn't detect any change but you at least got a screen, go back to 60hz and increase the VT by another 100.
Test again.
keep testing until you get an out of range error, then go back by 25, 50, or 75 until you find the limit to where it works.
If you do not get an out of range error, but you start getting strange shimmering images over the DVI port, switch to displayport, you're probably exceeded what the DVI cable (not the monitor, but the cable) bandwidth can send. Or you can just test directly over DP, but I was just curious if the 120 and 144hz only strobe bugs might be fixed if using DVI.
Once you find the Vertical Total limits (I'm guessing it should be close to "2000"), test it and compare the strobe crosstalk at the bottom of the alien invasion screen, with the "default" (without a VT Tweak) crosstalk.
This will tell us if VT tweaks work with this monitor.
IF they do, then try the same thing but at 100hz refresh rate, and see if the monitor will strobe without stuttering. (On current firmware and default settings, 60hz and 100hz will strobe at 120hz pulses, causing a stutter, unpleasant and worthless image, even on V002, only 120 and 144hz seem to work correctly).