Custom Resolution Utility (CRU)

[Nazar]

(08-16-2015 12:27 PM)ToastyX Wrote:  What video card? Are you using the pixel clock patcher? Both AMD and NVIDIA have 400 MHz pixel clock limits for VGA in their drivers, but the AMD pixel clock patch can get around that. I don't have a solution for NVIDIA.

AMD Radeon™ HD 6870. I attached the resolutions I was able to run in a file. All of them work smoothly.

After setting the resolution to 2560*1920@60 (399.35 Mhz) I used PowerStrip (because the AMD 60xx series is the last supported by it -- newer ones can not be tweaked in advanced hardware mode) to increase the refresh rate still higher. I was able to attain around 62 Hz refresh (over 410 Mhz pixel clock). When increased beyond that the screen went black.

(08-16-2015 12:27 PM)ToastyX Wrote:  What about the INF files that CRU creates? That should have been fixed in 1.0.1 based on your feedback.

Checked it now, and yes, the .INF files created by CRU work too. I was just always converting the DAT files from CRU to .INF with MonInfo just to be sure everything goes fine, because previously I remembered the .INF files from CRU failed to function as monitor drivers (don't remember the specifics at this moment). But now I just checked (created an .INF with CRU for extra high resolutions and used it as a driver) and they do work without any problems.

Thanks again for your wonderful work.

P.S. There was a conflict I reported earlier where AMD drivers after 13.12 failed to pick up the custom refresh rates (which worked fine on versions up to 13.12). Later I found out that this conflict only occurred when I used the VGA cable with a removed pin 9 (don't know why the pin was removed from that cable, but this was the thick high quality VGA cable that came with the monitor), which resulted in the monitor being detected as non-PnP. After I used a cable with all the pins, the newest drivers started working with all the custom resolutions, both in PnP and non-PnP modes (which can be set in drivers).

P.S.2 The .INF files can also be used in Windows 10, but driver signature checking needs to be turned off for their installation.