Page 32 of 35

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 27 Apr 2017, 15:54
by Elixir
I'm using a custom mode set in Nvidia as 180hz, 1500 VT, Area 0, Intensity 10, but no idea how to get into the factory menu. Is it not the same as the service menu? Do you have any idea how to get into it for the XL2540? I tried holding down button 3+4 while turning the monitor on, didn't work.


Using this, the ghosting on text even while scrolling websites is honestly pretty noticeable right now.

Only using 1500 VT because someone else that has this monitor did, not sure if it's the best.

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 27 Apr 2017, 16:07
by Falkentyne
Factory menu should be holding button #3 and #4 while powering on the monitor, then button 5 enters it.

At least this is how you did it in the XL2735, XL2730, the previous Z series monitors with touch buttons (XL2720Z, etc) and other people said this worked in the XL2540.

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 27 Apr 2017, 19:06
by Elixir
Alright, got it. Next question: should I have AMA set to Off, High or Premium?

Also if anyone has any VT suggestions for this monitor please share. 1500 at 180hz works but I don't know if it's optimal.

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 04 May 2017, 13:47
by Chief Blur Buster
Easier Testing & Discovery Of Large Vertical Totals

(Applies to reducing strobe crosstalk on XL2540).
Here's a new Blur Busters tip that will greatly aid in discovery of proper Vertical Totals, if you're using that to reduce strobe crosstalk.

Easy ToastyX CRU Steps

1. Choose a working high-Hz mode (e.g. 240Hz)
2. Lock the dotclock (put radio button on Dotclock, make sure it DOES NOT change)
3. Now lower the refresh rate indirectly via increasing the vertical total. DO NOT edit refresh rate directly
4. Stop increasing vertical total once the calculated refresh rate fully lowers to near your targeted refresh rate. (It may be fractional, e.g. 180.002Hz or 119.998Hz, do not fix the fraction)

You will have weird VTs (e.g. VT2136 or VT1844) and weird fractional refresh rates (e.g. 124.999Hz or 144.001Hz) but you'll be skipping time-consuming experimentation in trying to find large vertical totals. No more out-of-sync errors*

Explanation why this works more reliably on some panels

With a bit of fiddling, it's possible to keep both Horizontal Scanrate (KHz) and Pixel Clock unmodified while changing refresh rate. That's how VESA Adaptive-Sync and FreeSync works -- scanrate & clock never changes but refresh rate varies by varying the vertical total. We're simply borrowing this latent panel capability (unadvertised), to help discover working large vertical totals for fixed non-VRR refresh rates.

The name of the game is to fiddle with Vertical Total until you create a different compatible refresh rate without changing Horizontal Scan Rate nor Pixel Clock of a very well-working mode. Say, you've got a good 240Hz mode with a 599.640MHz dotclock (or whatever dotclock your perfectly working 240Hz mode was). Now you want to maintain EXACTLY the same dotclock WHILE lowering your refresh rate.

In ToastyX, you simply lock this maximum dotclock of the maximum perfectly working refresh rate. This can help you find the biggest possible exact working vertical total (at least if the panel is FreeSync compatible) for a fixed refresh rate. It can result in weird vertical totals such as VT2631 or VT1844, usually super-humongous at low refresh rates (e.g. 60Hz) and almost same as vertical resolution at maximum refresh rate (e.g. VT1100 or less for 1080p).

Note: When increasing Vertical Total -- it may be better to focus on only increasing Sync (or Front Porch). Generally, avoid increasing Back Porch. Depending on how the GPU output does it, increasing Back Porch may increase input lag by delaying the beginning of the refresh cycle. This is because Back Porch pads the beginning of a refresh cycle. I understand that FreeSync keeps the porches constant while changing Vertical Sync on the fly. For maximum compatibility with Large Vertical Totals on generic LCD panels, you will probably want to focus on changing "Sync" as the method of increasing Vertical Total

Done. Now you've created the biggest possible vertical total for a specific resolution, to help your strobe crosstalk. By locking to the dotclock of 240Hz, you've maintained the scanout velocity of 240Hz, while lowering your refresh rate. You will get weird Vertical Totals such as VT2379 or VT1644 or VT1328 etc, when you're looking for the biggest possible Vertical Total for a specific exact refresh rate. Weird numbers are normal, but at least they work.

- Faster to find a maximum Vertical Total for a specific refresh rate.
- You don't have to experiment to find those "magic working numbers" anymore!
- You also avoid "out-of-sync" of non-working modes (at least on fully FreeSync-compatible panels*).

By keeping dotclock and horizontal scanrate the same -- this can make discovery of working Vertical Totals easier for a desired refresh rate, if you have a need for a Large Vertical Total (e.g. reducing strobe crosstalk).

This rapid Vertical Total discovery trick only works very reliably on VRR-compatible panels to create a fixed Hz mode with fast scanout (and when Blur Reduction does not modify scanout velocity). XL2540 is one of the models where Large Vertical Totals successfully reduce strobe crosstalk. Although not officially FreeSync, it has been reported to work with FreeSync VRR when forced to do so via ToastyX CRU (48Hz-240Hz range). As a result, this "rapid Vertical Total discovery trick" significantly simplifies your life.

Remember, this came from Blur Busters.
Credit us please, if you document this timesaving trick elsewhere.

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 04 May 2017, 14:23
by Falkentyne
The Benq XL2735 does not support freesync, but the SCALER Supports freesync. However the freesync identifier is missing in the displayport specification (editing the extension block should make freesync work over HDMI, but displayport may/will ignore this freesync identifier), so these same tweaks SHOULD work on the XL2735. (VT was tested up to 1825 at 120hz, and 1852 with a reduced horizontal total). 144hz only went up to 1260 I believe. Vega was the one who tested this, but he sold the monitor.

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 04 May 2017, 14:32
by Chief Blur Buster
Falkentyne wrote:so these same tweaks SHOULD work on the XL2735.
- As long as it can scan out synchronously to the LCD panel (aka instant mode / lagless mode).
- As long as its strobe mode synchronizes to any refresh rate, and has adjustable strobe phase.

AFAIK Vertical Total tweaking already helps strobe crosstalk on these models: XL2411, XL2420, XL2720, XL2735, XL2540 (and probably XL2546)

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 07 May 2017, 21:33
by jmcsmfpc
Hey, is the ama still the same thing
If u set it to high or premium do you still see the black trail?

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 07 May 2017, 22:30
by Falkentyne
You can go into the factory menu and change OD gain to make the ghosting as you like it.

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 08 Jun 2017, 16:28
by ranejt
Has anyone done any side by side comparisons of 120hz ulmb vs 180hz ulmb vs 240hz?

Re: Presenting the ZOWIE XL2540 240Hz

Posted: 24 Jun 2017, 07:42
by casinca

I was wondering :?: does playing with less than 240fps on a 240hz monitor would still feel better than playing on 144hz ?

if it's worst, to what extent ?
Is it worth the hassle to change refresh rate every time, 144hz for games where you can't get 240+ steady fps then switch back to 240hz when you can get 240+ fps ?