AMD/ATI Pixel Clock Patcher

[ToastyX]

(03-05-2017 07:49 PM)hannes69 Wrote:  I tried driver 16.11.5 and tried patched and not patched. The behaviour is the same like described above. What can we conclude from that?
Is it really coincidence that both of my devices (TFT monitor and DLP projector) can exactly go down to hblankmin 57 and not any further? If so, then AMD seems to have made a useful restriction, if normal devices (I consider I have "normal" devices) can´t go below 57 hblank.

The driver limit is 56, not 57, so you're running into a different limitation. It could be a coincidence, or maybe your video card can't go below 57 for some reason. I have no trouble going under 56 with 16.11.5. For 56, try something like 16/24/16 instead of 1/1/54.

(03-05-2017 07:49 PM)hannes69 Wrote:  I myself can´t test if it is the driver or the device, because how will I know that the resolution is "fired" through the DVI/HDMI port (so no restriction of the driver) or not?

The only way I know for sure is to use a monitor that I know can handle lower values. The driver won't send a signal if it doesn't detect a monitor.