Custom Resolution Utility (CRU)

[ToastyX]

(06-22-2016 07:11 PM)Magicool Wrote:  My question is regarding the timing:
With the "native" timing I can reach max 66Hz@1080p@163.35Mhz (I dont want to patch the GPU drivers yet).
With the "standard" timing I can go up to 71Hz@1080p@164.96Mhz.
So what are the pros and cons of these timings and what are they there for?
Is there a disadvantage using the "standard" timing which woudl allow me to go up to 71Hz without patching the driver?

It doesn't matter. Just use whatever works. The only disadvantage is the video card might not clock down when idle if the vertical blanking is too low, but that shouldn't happen with standard timings. Standards exist to make sure certain values are always supported, but that's not guaranteed when trying refresh rates that are not officially supported by the monitor.

(06-22-2016 07:11 PM)Magicool Wrote:  I also read somwhere when using the Nvidia control center I don't need to patch driver because it automaticly overlocks the pixel clock?

That depends on what you're doing. Single-link DVI monitors always expect a single-link signal, so single-link DVI always requires the patch to go beyond 165 MHz pixel clock. Dual-link DVI needs the patch to go beyond 330 MHz pixel clock when using CRU but not when using the NVIDIA control panel. HDMI doesn't need the patch in either case if you add an HDMI support data block in the extension block.

(06-22-2016 07:11 PM)Magicool Wrote:  Edit: Something else just caught my eye.
In the Nvidia control panel it doesn't say HDMI anymore but DVI.
Is this normal?

HDMI is treated as single-link DVI if an HDMI support data block is not defined in the extension block. If you add an HDMI support data block in the extension block or import one of the hdmi.dat files, you won't need the patch to go beyond 165 MHz pixel clock.