Custom Resolution Utility (CRU)

[ToastyX]

(09-11-2017 02:25 AM)BLUuuE Wrote:  Hey ToastyX,
it seems that AMD has removed the 56 blanking limit and I can run a blanking lower than that. I was messing about with the timings, trying to decrease them as much as I could and testing it on a 70Hz refresh rate rather than my 72Hz. This is the lowest I could go without my monitor going a bit fuzzy. https://puu.sh/xwN1K/7751135576.png

However, when I tried these timings on 72Hz, my monitor became fuzzy, which means that to achieve higher refresh rate you need looser timings (similar to RAM)? But looser timings means higher pixel clocks which is usually the limiting factor when overclocking monitors.

Also, what do the range limits do?

The 56 blanking limit is still there for me. Are you using the pixel clock patcher? I found a way around the limit and added it to the patch last year.

There's no reason to reduce the blanking that low when "LCD reduced" will go up to 76 Hz while keeping the pixel clock from exceeding 165 MHz without going below the 56 horizontal blanking limit. Monitors often can't handle values that are too low. Other than pixel clock limits in the graphics driver, which the pixel clock patch can get around, the limiting factor is usually the monitor's firmware. Most monitors are "locked" in the sense that the firmware will only accept a certain range of refresh rates and timing parameters. The hardware itself can probably handle at least 200 MHz pixel clock, and the panel itself could probably handle 100 Hz if the firmware allowed it.

The range limits are informational. I only added it because AMD decided to use the range limits to control the FreeSync range with DisplayPort monitors. Other than that, CRU doesn't include the range limits by default because it's not needed.