xl2730z

[Falkentyne]

It's because of the scaler.

The scaler will display any resolution entered within a custom vertical total within the range of 1300-1350 (1200-1250 displays out of range but has a signal) and most VTs higher than 1350 just black screen, but around 1481-1485 suddenly you get a screen again but the OSD shows "out of range" even though the image still appears. Then from 1487-1496 is black screen out of range again, then suddenly, VT 1497-VT 1502 show a perfectly working image without any errors (just like VT 1350 and below).

Why? I don't know for sure, everything I'm saying is a pure guess. I would need someone with a pre blur reduction "T/TE" series Benq to test the same vertical total tweaks to see if they get an image or not.

I think the 1497-1502 VT range is what Lightboost mode uses internally for lowest crosstalk, because 120hz Lightboost mode 10% (persistence 1.4 ms) has the EXACT same crosstalk at the EXACT same position on the screen as Benq blur reduction 120hz with Vertical total 1500 and Strobe duty set to 009 (1.5ms persistence) and strobe phase (Area) 000.

What's bizarre is what the scaler reports (not the OSD, the scaler) in the factory menu.
Some examples:
1920x1080@100hz default timings (1133 vertical total), scaler reports 1920x1080@100 in factory menu.
1920x1080@100, 1125 Vertical total (Instead of 1133), scaler reports 1400x1050@100hz in factory menu. OSD shows 1920x1080@100
1920x1080@120hz, 1144 default VT, shows 1920x1080@120 in factory menu
1125 VT shows 1400x1050 again.

1920x1080@100hz, 1350 vertical total ->scaler reports 1280 for the vertical resolution (I forgot the horizontal).
1920x1080@100hz, 1497-1502 vertical total ->Scaler reports 1280x1440 (!). Notice the vertical is larger than the physical panel size (this is why the strobe crosstalk is lower! the extra crosstalk is off the screen).

What's really bizarre is the 1481-1485 VT range.
You get an out of range popup on the OSD but you still get an image. You can close the OOR error and still get into the factory menu (you can't get into the OSD though, the OOR error just comes up again). The scaler reports.......1920x1440 !!!!!
That's why you get the out of range error but still get a screen...1920x1440 is completely out of the panel specs and the scaler is reporting it

Yet from 1497-1502 VT, the scaler shows 1280x1440 instead of 1920x1440 and theres no out of range error at all....for some reason in this small VT range, the scaler accepts this as valid. I assume this is what lightboost uses internally. And if someone with a T series finds that these VTs work on those, then that explains everything.

So since we know that 1497-1502 work, we can do scaler supersampling by creating a higher resolution since we know the scaler can accept a 1440 if its tricked into doing it:

toastyX CRU Custom timings:

2560x1440
100hz (60hz does NOT work. because 60hz wont accept a VT higher than 1350 yet 61hz accept VT 1502). 61 hz works too.
front porch 48 pixels, 3 lines
sync width 32, 5
Horizontal Total 2656 (reduced from the normal HT for this resolution; if its too high it black screens)
Vertical total: 1497-1502.
Pixel clock: 398 mhz.

OSD reports 2560x1440@60hz (ANY custom VT that is not default reports 60hz and the backlight uses the 60hz pulse width settings for blur reduction)
Says recommended is 1920x1080.

120hz works but with pixel corruption due to physical scaler pixel clock limits.

[PanzerIV]

toastyX CRU Custom timings:
2560x1440
100hz (60hz does NOT work. because 60hz wont accept a VT higher than 1350 yet 61hz accept VT 1502). 61 hz works too.
front porch 48 pixels, 3 lines
sync width 32, 5
Horizontal Total 2656 (reduced from the normal HT for this resolution; if its too high it black screens)
Vertical total: 1497-1502.
Pixel clock: 398 mhz.

OSD reports 2560x1440@60hz (ANY custom VT that is not default reports 60hz and the backlight uses the 60hz pulse width settings for blur reduction)
Says recommended is 1920x1080.

120hz works but with pixel corruption due to physical scaler pixel clock limits.

Damn, it's getting more and more complicated lol. Now it's time for bed but if you say the following in the quote works at 2560x1440@100Hz with Blur Reduction on the XL2730Z then I'm gonna try those custom values for sure. I just don't know why there's a pixel clock limitation even with the AMD Patcher as the default Mhz at 144Hz is 580Hz and have no issue with a DisplayPort cable so why would I need to get under 400?

By tricking the monitor, it is gonna show 60Hz even if your custom res is at 100Hz you mean? If yes, then is it gonna strobe like a 60Hz CRT and hurt my eyes or it is still gonna strobe normaly like my good old XL2420Z at 100Hz, even though the OSD will report 60Hz?

[Falkentyne]

No I'm talking about the XL2720Z (this applies to the XL2420Z also, over displayport). I was just saying that the strobe crosstalk on my XL2720Z with that 2560x1440 scaler downsampled setting is equal to the crosstalk on your XL2730Z, andwhat the OSD/scaler reports on mine.

It has nothing to do with the xl2730Z directly.

[tomb233]

Hi

I was just wondering if anyone has had this problem with the XL2730Z, never seen this before.

http://imgur.com/a/FMQqi

[Falkentyne]

Hi

I was just wondering if anyone has had this problem with the XL2730Z, never seen this before.

http://imgur.com/a/FMQqi

What video card is that?
That looks like what happens to the ROG Swift when it dies, also. RMA the panel.

[tomb233]

Hi

I was just wondering if anyone has had this problem with the XL2730Z, never seen this before.

http://imgur.com/a/FMQqi

What video card is that?
That looks like what happens to the ROG Swift when it dies, also. RMA the panel.

Using a 980 at the minute, but it's happening over HDMI,DisplayPort and DVI. Also happens when using an Xbox One and PS4.

I put in an RMA today but I wasn't sure what the name of the problem was.

Thanks for your help.