AMD/ATI Pixel Clock Patcher

[eucalyptux]

Hello, i just tried to do the VT1500 trick+ tight timing with my freshly flashed XL2411Z v4, r9 290 and Catalyst 15.7
But i have a black screen (more like no backlight) when i switch to 120hz, is the 15.7 incompatible or im doing something else wrong ?

edit: vt1350 with default timing work but artefact

edit2: same with 15.5 beta

[Screemer]

(07-10-2015 03:42 PM)yasamoka Wrote:  Is your 290X overclocked? Some users have reported trouble with overclocking their monitors with the 290 / 290X if they have a GPU core or memory overclock.

no it isn't. i think the problem is the accell-adapter. 82Hz is not a problem. just below 330MHz pixelclock limit of the unpatched driver. with a nv card the adapter makes 144Hz without any problems. my guess is that there is something else to patch if a dp->dl-dvi-adapter is used.

would love to assist toastyx to find a solution. that would be very helpfull for fury x users, which doesn't have a dvi-port, with korean monitors.

[ToastyX]

(07-06-2015 01:41 PM)Screemer Wrote:  Now i am trying to overclock with a active dp->dvi-adaptor from accell. It's the following one. Other are using it with a native 144Hz-Monitor and it's working up to 120Hz with 1440p.

I haven't heard of anyone getting 2560x1440 @ 120 Hz with that adapter. It can only handle around 100 Hz with 18-bit color (6 bpc). 1920x1080 @ 144 Hz is still under 330 MHz, so that wouldn't affect 144 Hz monitors.

(07-06-2015 01:41 PM)Screemer Wrote:  but the highest refreshrate is 81Hz with standard timings and 82Hz with reduced lcd timings. same behavior as without the pixelclock patch. i tried the different extensionblocks as well with no avail. do you have any idea about that?

That's weird because the 330 MHz dual-link DVI limit shouldn't affect DisplayPort with an active adapter unless AMD changed something recently. Other people have used that adapter with AMD cards, so I don't know why you're seeing this limit. The limit should be 360 MHz with 24-bit color (8 bpc) and 480 MHz with 18-bit color (6 bpc). Is the limit actually 330 MHz, or is it something else like 327 MHz or 360 MHz?

[ToastyX]

(07-11-2015 02:56 PM)eucalyptux Wrote:  Hello, i just tried to do the VT1500 trick+ tight timing with my freshly flashed XL2411Z v4, r9 290 and Catalyst 15.7
But i have a black screen (more like no backlight) when i switch to 120hz, is the 15.7 incompatible or im doing something else wrong ?

edit: vt1350 with default timing work but artefact

edit2: same with 15.5 beta

You might have to reduce the crosstalk setting as described here: http://forums.blurbusters.com/viewtopic.php?f=13&t=1689

[eucalyptux]

it seem that my crosstalk setting was stuck
going in the service menu, moving things around have fixed the probleme
thanks

[falkentyne]

(07-12-2015 12:18 AM)ToastyX Wrote:  

(07-11-2015 02:56 PM)eucalyptux Wrote:  Hello, i just tried to do the VT1500 trick+ tight timing with my freshly flashed XL2411Z v4, r9 290 and Catalyst 15.7
But i have a black screen (more like no backlight) when i switch to 120hz, is the 15.7 incompatible or im doing something else wrong ?

edit: vt1350 with default timing work but artefact

edit2: same with 15.5 beta

You might have to reduce the crosstalk setting as described here: http://forums.blurbusters.com/viewtopic.php?f=13&t=1689

Yes,
When using the VT tweak, the maximum "strobe phase" setting is reduced. The basic rule is, when using a VT 1500 tweak, the higher the refresh rate, the lower the max Strobe Phase will be.

Here are some limits I have found myself.
125 hz: VT 1498: Strobe phase 047 (Vt 1500 is laggy at 125hz on my xl2720z)
120 hz: VT 1500: Strobe phase 049
100 hz: VT 1502: Strobe phase 059
91 hz: VT 1502: strobephase 065 (custom refresh rate/resolution for call of duty)

Going 1 higher strobe phase past these will set the persistence to 0 ms which effectively shuts off the backlight (turning off blur reduction will bring the screen back).

A more indepth, but non confusing explanation of why the strobe phase is limited with a VT tweak is the first post by masterotaku here:

http://forums.blurbusters.com/viewtopic.php?f=13&t=560

I have a post somewhere explaining in a bit more detail exactly what the vertical total is doing to the monitor scaler. ToastyX could probably explain much better, but in the factory service menu#2 (V4 firmware only; power off, hold button 3+4 for 5 seconds then press power at the same time; button 1 and 2 on XL2411z), using a VT 1500 makes the scaler report that the vertical screen size is 1440 instead of 1080, which effectively "moves" the bottom strobe crosstalk off the physical end of the monitor and into some sort of virtual zone (which if you think about it, explains why the maxiumum strobe phase is lower with a VT tweak).

[eucalyptux]

Thank you for taking the time to explain this, its a bit more clear for me now

Do you have any tip for the AMA setting ? I have hear that this had some change in v4, and what about the "hidden AMA" ?

Finally, what is the ideal contrast setting ?

There are people with a ton of knowledge of the subject on this forum and on blurbusters but i think it lacks a complete guide , I find that those informations are very scattered.

[falkentyne]

(07-12-2015 03:29 PM)eucalyptux Wrote:  Thank you for taking the time to explain this, its a bit more clear for me now

Do you have any tip for the AMA setting ? I have hear that this had some change in v4, and what about the "hidden AMA" ?

Finally, what is the ideal contrast setting ?

There are people with a ton of knowledge of the subject on this forum and on blurbusters but i think it lacks a complete guide , I find that those informations are very scattered.

You should post questions like these in the blur busters forum, as this is a bit off topic now.

But I have the XL2720Z and the AMA functions slightly differently on the 27" and 24" screens although BOTH screens still have too much AMA compared to a screen with REALLY nice overdrive (Like VG248QE) and I don't think this was fixed until the XL2730Z (much better AMA improvement, but broken strobe at 100hz and 60hz, go figure).

XL2720Z and XL2411/20Z normal V4 settings:
XL2720Z seems to have less aggressive AMA than XL 24" screens
XL2411Z AMA high seems to look like XL2720Z AMA premium.
Lightboost mode on XL2411Z looks MUCH better than Lightboost mode on XL2720Z.

XL2720Z contrast=40 seems to have half the inverse AMA overshoot intensity/artifacts of contrast=50. I don't know if this applies to XL2411z or not.

V4 firmware: on XL2720Z, turning on blur reduction and then setting AMA to high after blur reduction is already enabled, seems to reduce the AMA intensity by half or more (rather drastic), effectively making it look the same as Lightboost mode on the exact same screen, if you reduce contrast to 0 (lowest amount of ghosting AFTER you do this) to compare Lightboost and Benq MBR. Lightboost mode on the 24" XL's still looks better than it does on the XL2720Z, though. At default contrast of 43 (correct white point), the inverse artifacts are turned into normal ghosting (Very low amount of AMA) after doing this toggle. For best results after this toggle, reduce contrast to 15 or lower or you will have too much normal ghosting (XL2720Z only)
For Blur reduction, this is effectively "AMA Low" on XL2720Z.

On XL2411Z, this toggle only reduces the AMA slightly, instead of drastically. XL2720Z AMA premium seems to do this also--slight AMA reduction instead of drastic AMA reduction (that's why I think that XL2720Z premium= XL2411Z high).
I do NOT know why Benq did not include this "Low" hidden setting on the 2411z and 2420z and only threw in a 'slightly less than overly high" "setting. It also does not apply to blur reduction off either.

About contrast: experiment between contrast 40-50. Do not exceed 50.

The main reason with lack of information about V4 firmware is there is still no 'official' way to update, and Benq still has V2 on gaming download site, even though all monitors shipping since March should have V4.

[fragfeaster777]

Hi Toasty,

After using your (amazing) patcher and CRU tools without any issues for many AMD driver iterations, I too seem to be having problems with Catalyst 15.7. When running Patcher with Catalyst 15.7, I got the DVI/HDMI limit not found (1st line). All the other items were found and patched, but I tried applying my previous (completely unchanged) CRU settings and I would get a garbled screen upon reboot. Using the reset program in safe mode still works though.

I reverted back to Catalyst 15.6 and both Patcher and CRU work flawlessly. I tried then different settings for the monitor under CRU and Catalyst 15.7 but nothing would work. I also deleted 15.7 using the uninstall option and Display Driver Uninstaller, but to no avail. In all instances, reinstalling 15.6 worked without issues.

So maybe there is something going on with Catalyst 15.7, especially since Patcher couldnt find the DVI limit.

[broken pixel]

(07-13-2015 02:21 PM)fragfeaster777 Wrote:  Hi Toasty,

After using your (amazing) patcher and CRU tools without any issues for many AMD driver iterations, I too seem to be having problems with Catalyst 15.7. When running Patcher with Catalyst 15.7, I got the DVI/HDMI limit not found (1st line). All the other items were found and patched, but I tried applying my previous (completely unchanged) CRU settings and I would get a garbled screen upon reboot. Using the reset program in safe mode still works though.

I reverted back to Catalyst 15.6 and both Patcher and CRU work flawlessly. I tried then different settings for the monitor under CRU and Catalyst 15.7 but nothing would work. I also deleted 15.7 using the uninstall option and Display Driver Uninstaller, but to no avail. In all instances, reinstalling 15.6 worked without issues.

So maybe there is something going on with Catalyst 15.7, especially since Patcher couldnt find the DVI limit.

I noticed the same issue with the 15.7 drivers and using the latest version 1.3.4 of the pixel patcher and also reverted back to the 15.6 drivers. I noticed the pixel patch would work with the 15.7 drivers @ 100Hz but once you enable vsync it totally kills performance and my frame rate drops to the high 60s from 100fps synced.

Thanks for all the work & dedication ToastX.