Custom Resolution Utility (CRU)

[ToastyX]

(12-16-2020 09:42 AM)diakou Wrote:  There seems to be not a single 360Hz resolution in the entire extension block displayed, the VRR ranges are indicated as 1-255 as well and lastly, why does detailed resolution showcase 60Hz and also I am not able to create a 360Hz profile no matter what.

In windows my display states as 360.113 - but through NVIDIAs custom resolution in NVCP, I changed my refresh rate to a round 360 and had it work out with CVT Reduced Blank timings set to Auto. The reason why I am primarily curious about all this, is because I've seen many manufacturers out of box at default run something like 239.760 for the 240Hz monitors etc, whenever I changed this to a round 240 with LCD Native in CRU - I'd have a very different game feel when utilizing the monitor. It was as if it got a lot, lot more smooth/responsive/fast. Odd, just curious if you had any answers or knowledge regarding stuff like this or if it's pure placebo. (also curious about the 360Hz thing, maybe CRU isn't supported yet for those monitors out of the box information?)

Refresh rates are arbitrary and don't have to be integers, so I don't see how rounding would make a difference except when displaying fixed frame rates, but then VRR should be able to handle that.

360 Hz is in the second extension block, which is a DisplayID extension block, but CRU can't read more than one extension block with NVIDIA because the driver won't provide it for some reason. NVIDIA also ignores overrides with default extension blocks, so you'll have to delete the default extension block and create one manually, but that might disable VRR. I have an idea to read the extension block directly from the monitor instead, but I'll need someone to test it because I don't have a monitor with 2 extension blocks. Will you be able to run some tests?

The problem with the range limits is they keep coming up with new ways to specify the refresh rate range. I know of three different methods (EDID range limits, AMD FreeSync data block, HDMI 2.1 data block), but your monitor seems to use another method. I don't know why because the EDID range limits can go up to 510 Hz. It might be in the DisplayID extension block, but I just checked the DisplayID standard, and it can't even define a range beyond 255 Hz.