Hi, i am proud to announce that i just got my Benq XL2411Z with V2 firmware. I play Starcraft 2 and Dota 2. At Starcraft 2 i play compatitive level. I use 120Hz both games. Input lag is awsome. The problem i have is the gamma. I can not configure it right. Its always too much or too low.
When i tryied 100Hz the gamma is much better and at 75 Hz even more better. So i got it. More Hz, low Input Lag, worst colors and Gamma. Less Hz, more input lag, better colors and gamma.
So my question is: What exacly VT Tweak does? Makes better colors for 120Hz, or i got it wrong? Thanks in adnvance!
(I am from Greece! Sorry for my bad English)
VT Tweak Question
Re: VT Tweak Question
VT Tweak makes input lag a bit less.
Re: VT Tweak Question
But this is only with Benq Blur Reduction enabled? Am I right?Q83Ia7ta wrote:VT Tweak makes input lag a bit less.
VT tweak also increases the brightness and decreases the ghosting.
-
Falkentyne
- Posts: 2805
- Joined: 26 Mar 2014, 07:23
Re: VT Tweak Question
Yes only with blur reduction, and preferably only WITH a VT tweak, because without it, strobe phase 100 doesn't make the bottom of the screen clear enough. You need a strobe phase so high that it overflows and starts lowering the persistence (ms) values (even though the strobe duty value doesn't change). And only because you can set the crosstalk zone to have the image appear one frame ahead of its actual location instead of one frame behind. TBH it's just strobing at work. There's basically a 'leading' edge in your overdrive artifacts, the primary image, the primary trail and the secondary trail (both behind the image). By using the VT tweak and a strobe phase higher than 54, you basically make the leading edge the primary image and turn the original primary image into the 'leading trail'.
You can actually see this by REMOVING the VT tweak, running the toastyx driver restarter, then setting strobe phase to 60 through the service menu, while running testUFO alien invasion. You can't do this with the vertical tweak--if you try, the backlight will shut completely off because the persistence will go below 0.01 ms (if the strobe phase gets too high and the strobe pulse occurs too early in the frame cycle, the strobe phase stops changing and the persistence (strobe duty) gets lower instead). But anyway, with a strobe phase of 060, you will notice that the top half of the screen, ABOVE the strobe pulse, will be one frame ahead of the bottom of the screen (the center of the screen will be a crosstalk blurry mess with -two- primary images next to each other). Now yes, you CAN do this with a strobe phase of 100, but without the VT tweak, the beginning and end of the strobe pulse isn't long enough, so the blurry mess will be covering the bottom third of the screen. TBH, That's why the monitor defaults to strobe phase 100 in the first place--Benq wanted to make the top of the screen without settling errors, just like lightboost does, while also giving you an improvement of frame of input lag. But if you compare strobe phase 000 with strobe phase 100, you will see that strobe phase 000 keeps the top of the screen looking decent enough while the bottom of the screen has the blurry mess lower down the screen than strobe phase 100, but STILL not completely off the screen, but looks better, while part of the edge of the top of the strobe pulse is visible at the the very top.
What the VT tweak actually does is, by increasing the dot clock and giving the panel more time to complete the transitions, it actually EXTENDS the distance between the TOP and BOTTOM of the strobe pulse, thus making more of the screen look good (lightboost does this through the LC panel). TBH it simply pushes the bottom of the strobe pulse LOWER while the top of it remains at the same spot. If you compare strobe phase 000 without the VT tweak AND strobe phase 000 WITH the VT 1500 tweak (at the same refresh rate, lets say, 100 hz, so you don't have to worry about 120hz fps being cut in half in internet explorer), you will see that the TOP of the crosstalk pulse remains at the exact same position both with and without the VT tweak, while the BOTTOM blurry mess gets pushed off the screen completely. Because of this, adjusting the strobe phase with the VT tweak from 000 to a higher value will MOVE the top crosstalk pulse FARTHER down the screen than it would without the VT tweak. So once you reach strobe phase 047 (the highest value that can be set through the windows utility), it looks like strobe phase 100 does WITHOUT the tweak. Once you go past 047, depending on the refresh rate and the current persistence (duty), the screen may start getting darker. This is because, if you try, for example: strobe phase 000 and strobe duty 006, with the VT 1500 tweak (1.0ms persistence), if you LOWER the strobe duty to 003-001, you will see the TOP of the crosstalk pulse get pushed off the top of the screen, while if you raise the strobe duty and go down to 030, you will see the crosstalk pulse get pushed towards the middle of the screen--just by adjusting the persistence. So adjusting the persistence ALSO has an effect on the strobe phase position, just not as much. WITHOUT the VT tweaks, the strobe phase does NOT affect the strobe duty at all (the persistence won't change from 000 to 100 strobe phase), which is how the monitor was tested. It was not tested with the VT tweaks (Obviously) so using VT tweaks, while extending the distance between the top and bottom of the strobe pulse, causes bizarre stuff to happen when the VT tweak is being used, if the strobe pulse *POSITION*-not the # in the service menu, extends past the equivalent "100" value of no VT tweak (and the monitor uses the 60 hz backlight pulse widths also, when the VT tweak is active, which stops the 'display mode' settings from working correctly.
Also, 50 hz single strobe doesn't work at all (unless you use the VT tweak to force the 60hz pulse widths instead of the 50 hz pulse widths!)--either the backlight just comes on at an excessive brightness (can damage the LED's), the screen resets itself from overcurrent, or the backlight just turns off right away (depending on the strobe pulse). I don't think 50hz single strobe was tested, as you would never want the seizure enduring flicker anyway (you can see what it's like by using a VT 1260 @ 50hz to force the 60hz backlight pulses). 50 hz double strobe works perfectly, as this was the intended behavior in the original v001 firmware--the screen was supposed to double strobe at 50 and 60 hz. V002 added a single strobe option for 60hz for console and 60hz game features, but 50hz doesn't work (maybe on the 24" screens it does, as the HT total, sync and pulse widths are different (2080, 48/3 , 32/5 instead of 2200, 88/4, 44/5).
You can actually see this by REMOVING the VT tweak, running the toastyx driver restarter, then setting strobe phase to 60 through the service menu, while running testUFO alien invasion. You can't do this with the vertical tweak--if you try, the backlight will shut completely off because the persistence will go below 0.01 ms (if the strobe phase gets too high and the strobe pulse occurs too early in the frame cycle, the strobe phase stops changing and the persistence (strobe duty) gets lower instead). But anyway, with a strobe phase of 060, you will notice that the top half of the screen, ABOVE the strobe pulse, will be one frame ahead of the bottom of the screen (the center of the screen will be a crosstalk blurry mess with -two- primary images next to each other). Now yes, you CAN do this with a strobe phase of 100, but without the VT tweak, the beginning and end of the strobe pulse isn't long enough, so the blurry mess will be covering the bottom third of the screen. TBH, That's why the monitor defaults to strobe phase 100 in the first place--Benq wanted to make the top of the screen without settling errors, just like lightboost does, while also giving you an improvement of frame of input lag. But if you compare strobe phase 000 with strobe phase 100, you will see that strobe phase 000 keeps the top of the screen looking decent enough while the bottom of the screen has the blurry mess lower down the screen than strobe phase 100, but STILL not completely off the screen, but looks better, while part of the edge of the top of the strobe pulse is visible at the the very top.
What the VT tweak actually does is, by increasing the dot clock and giving the panel more time to complete the transitions, it actually EXTENDS the distance between the TOP and BOTTOM of the strobe pulse, thus making more of the screen look good (lightboost does this through the LC panel). TBH it simply pushes the bottom of the strobe pulse LOWER while the top of it remains at the same spot. If you compare strobe phase 000 without the VT tweak AND strobe phase 000 WITH the VT 1500 tweak (at the same refresh rate, lets say, 100 hz, so you don't have to worry about 120hz fps being cut in half in internet explorer), you will see that the TOP of the crosstalk pulse remains at the exact same position both with and without the VT tweak, while the BOTTOM blurry mess gets pushed off the screen completely. Because of this, adjusting the strobe phase with the VT tweak from 000 to a higher value will MOVE the top crosstalk pulse FARTHER down the screen than it would without the VT tweak. So once you reach strobe phase 047 (the highest value that can be set through the windows utility), it looks like strobe phase 100 does WITHOUT the tweak. Once you go past 047, depending on the refresh rate and the current persistence (duty), the screen may start getting darker. This is because, if you try, for example: strobe phase 000 and strobe duty 006, with the VT 1500 tweak (1.0ms persistence), if you LOWER the strobe duty to 003-001, you will see the TOP of the crosstalk pulse get pushed off the top of the screen, while if you raise the strobe duty and go down to 030, you will see the crosstalk pulse get pushed towards the middle of the screen--just by adjusting the persistence. So adjusting the persistence ALSO has an effect on the strobe phase position, just not as much. WITHOUT the VT tweaks, the strobe phase does NOT affect the strobe duty at all (the persistence won't change from 000 to 100 strobe phase), which is how the monitor was tested. It was not tested with the VT tweaks (Obviously) so using VT tweaks, while extending the distance between the top and bottom of the strobe pulse, causes bizarre stuff to happen when the VT tweak is being used, if the strobe pulse *POSITION*-not the # in the service menu, extends past the equivalent "100" value of no VT tweak (and the monitor uses the 60 hz backlight pulse widths also, when the VT tweak is active, which stops the 'display mode' settings from working correctly.
Also, 50 hz single strobe doesn't work at all (unless you use the VT tweak to force the 60hz pulse widths instead of the 50 hz pulse widths!)--either the backlight just comes on at an excessive brightness (can damage the LED's), the screen resets itself from overcurrent, or the backlight just turns off right away (depending on the strobe pulse). I don't think 50hz single strobe was tested, as you would never want the seizure enduring flicker anyway (you can see what it's like by using a VT 1260 @ 50hz to force the 60hz backlight pulses). 50 hz double strobe works perfectly, as this was the intended behavior in the original v001 firmware--the screen was supposed to double strobe at 50 and 60 hz. V002 added a single strobe option for 60hz for console and 60hz game features, but 50hz doesn't work (maybe on the 24" screens it does, as the HT total, sync and pulse widths are different (2080, 48/3 , 32/5 instead of 2200, 88/4, 44/5).