Page 1 of 1

Vertical Total Trick on AMD GPU

Posted: 14 Jul 2017, 14:30
by hleV
I have long since set it up on my XL2411Z, however I'm using an NVIDIA GPU.
Today I attempted to do the VT1350 trick for a friend (also XL2411Z, however an AMD GPU), and the screen just won't become brighter!

The info on CRU here hardly helps. Could certainly improve the tutorial. It was my first time using the CRU and the steps shown in that page don't seem to provide the desired result, for me anyway.

What I did was create a detailed resolution 1080p @ 120Hz, with settings similar to the screenshot of NVIDIA counterpart. Then restarted the GPU driver (it says to restart the PC, tried that as well). What's confusing is the "switching to your newly-created mode". In Windows 10 monitor settings it's just "120 Hertz", which is already chosen. Switching to e.g. 144Hz and back to 120Hz doesn't help.

Would it be possible to get a more in-depth step-by-step tutorial for this? I searched for VT1350 for AMD and there aren't many results.

Re: Vertical Total Trick on AMD GPU

Posted: 15 Jul 2017, 00:40
by Chief Blur Buster
There's other instructions at http://www.blurbusters.com/strobe-crosstalk

Remember that this needs to be combined simultaneously with strobe phase (Area) adjustments -- it shifts the crosstalk band up and down.

With large vertical totals (as explained in the above link -- the way the monitors work), you can move more of the strobe crosstalk off the edge of the screen before it wraps around to the opposite edge. This results in thinner double-image bands at top/bottom and a taller mostly crosstalk-free zone (over 3/4ths the height of the screen). This is the most visible improvement that "Large Vertical Totals" brings.

Also, unfortunately, brightness is no longer affected as BENQ fixed that "bug" in newer firmwares. However, you can still get a thinner band of strobe crosstalk. VT1350's primary purpose is not to make the screen brighter, but to reduce strobe crosstalk.

Re: Vertical Total Trick on AMD GPU

Posted: 15 Jul 2017, 06:28
by hleV
Oh, I see. So VT1350 "bug" was fixed for newer FWs (I'm on V4 while friend has a newer, Zowie one). Right now I'm on 2.0ms persistence while friend has 4.0ms to see properly. Will tell him to use the UFO tests to adjust to his preference.