Custom Resolution Utility (CRU)

[ToastyX]

(03-24-2023 10:52 PM)Jenno7 Wrote:  I did 78hz before, it's been about 1 year but i cant again 1024x768 75hz and 78hz

How did you do it before? With CRU or some other way? 1024x768 is not the native resolution. You can't add non-native resolutions on laptops with CRU because they don't have scalers. The old GPU method doesn't work for laptop screens, only external monitors.

[ToastyX]

(03-24-2023 11:04 PM)PLU Wrote:  Hi, I've been trying for a while to make my VRAM idle at 165 Hz but I haven't been able to yet.
I have an RX 5700XT connected via DP 1.4 HBR3 to an MSI Optix MAG274QRF-QD (1440p/165Hz) and at 60/120Hz the VRAM clocks can properly idle at 200 MHz but when set to 165 Hz it goes all the way up to max clock speed (1740ish MHz). Under "detailed resolutions" I only have one for 60 Hz so I edited the 165 Hz one under "extension blocks". My vertical blanking is set to 22 and I can only raise it until 65 before the frequency values go red. Also all the timing options give me a red "refresh rate".
Am I doing something wrong?

The first post tells you why it turns red and what to do.

[ToastyX]

(03-25-2023 02:01 AM)sofakng Wrote:  Thanks so much for the fantastic utility!

Quick question... I'm using an LG 34GN850 which is 3440x1440 (native) and supports 60, 100, 144, and 160 Hz refresh rates. It does not support 120 Hz.

However, when I use CRU to add custom resolutions that are higher (3456x2160 with 60 and 120 Hz), the Nvidia control panel automatically adds 120 Hz for 3440x1440.

Is this a bug? It seems like Nvidia assumes if my monitor supports a higher resolution at the same refresh rate then it must be supported at a lower resolution.

If I test 3440x1440 @ 120 Hz, the monitor freaks out so it really doesn't appear to be supported which seems very strange but regardless...

This is normal behavior for refresh rates in Windows. Refresh rates are automatically propagated down to lower resolutions by the graphics driver as scaled resolutions. I don't see why the monitor would freak out because it's supposed to be scaled to the higher resolution.

[ToastyX]

(03-25-2023 01:46 PM)ozgu Wrote:  @ToastyX First of all I'd like to thank you for this super beneficial tool, it is much appreciated!

Secondly, because I couldn't find an answer for my specific question I wanted to ask it here.

Since the monitor I use has variable refresh rate feature I have tried to use it but couldn't succeed.
Whenever I activate the Gsync from the Nvidia control panel and start a game or 3d application screen starts to blink and turns black.

According to the data sheet of the monitor following are the frequency ranges:
*DP (v. 1.4): fh:15~120 kHz, fv:24~75 Hz
*HDMI (v. 1.4): fh:15~120 kHz, fv:24~75 Hz

Then by using the CRU I changed the default vertical frequency range from 24-75 to 48-75 and the problem is fixed.
But my question is the reason why the monitor can't handle the 24-75 range for variable refresh rate is because the monitor has some sort of a fault or because the connection cable I use, or the variable refresh rate range is not as broad as it is specified in the data sheet?

The Gpu I use is Nvidia Gtx1080, and the monitor is connected with a Displayport cable which's version I assume is 1.2.
Also, it should be noted that the default Freesync range in the Data blocks section is 48-75.

I would be appreciated if you could help me about it.
Thanks in advance!

The frequency range in the specs is not necessarily the frequency range supported with FreeSync. You didn't mention what monitor you have. What is the advertised FreeSync range? If there's already a FreeSync data block by default with the range 48-75 Hz, then that might be the correct range. DisplayPort doesn't normally use the FreeSync data block, so maybe NVIDIA's driver is using the range limits instead. If the range limits is used for FreeSync, the horizontal range should be two equal values like 120-120 kHz.

[ToastyX]

(03-25-2023 02:29 PM)AntiGod Wrote:  Hello, thank you very much for this utility. I have been using for several years and for me it is essential software. (There should be a hall of fame for such things).

Anyway I am sure I'm just looking in the wrong place, but I'm still confused about what some of the HDMI 2.x Support settings do.

I am using an LG C1 OLED as a display with nvidia 3080 gpu. I attached my current settings. I have Max FRL at 48 Gbps and TMDS rate set to 660 and I know what these do. I have deep color up to 48-bit enabled and understand these. I know what DSC is but don't use it.

Most of the other ones I'm clueless: Fast Vactive and ALLM and FAPA start are enabled but I'm unsure if they should be. M delta, Cinema VRR, and Negative M VRR are all disabled. I'm curious in particular what these last three do and if they might be useful for me?

I don't have the HDMI 2.1 specification, and there isn't much info about this online, so I'm not sure what everything means.

Fast Vactive means the TV is capable of using a higher pixel frequency to complete the refresh scanout faster. I don't think this applies to VRR because VRR already does this inherently.

Auto Low-Latency Mode means the TV is capable of automatically switching to a low-latency mode when requested. I don't know if Windows drivers use this feature. This is probably something game consoles use.

FAPA start location has something to do with the frame accurate packet area.

Cinema VRR means the TV is capable of handling film refresh rates outside of the VRR range.

M delta and Negative M VRR have something to do with VRR calculations.

[ToastyX]

(03-26-2023 12:17 PM)ArtMov Wrote:  On another laptop with the same intel gpu driver, display overclocking works, permissions are added ( Pls tell me what else can be done? Is there another way? I have 10 gen graphics.

I don't control what Intel's driver does. You'll have to ask them. Their driver ignores EDID overrides on some laptop screens for some reason.

[ozgu]

(03-26-2023 03:39 PM)ToastyX Wrote:  

(03-25-2023 01:46 PM)ozgu Wrote:  @ToastyX First of all I'd like to thank you for this super beneficial tool, it is much appreciated!

Secondly, because I couldn't find an answer for my specific question I wanted to ask it here.

Since the monitor I use has variable refresh rate feature I have tried to use it but couldn't succeed.
Whenever I activate the Gsync from the Nvidia control panel and start a game or 3d application screen starts to blink and turns black.

According to the data sheet of the monitor following are the frequency ranges:
*DP (v. 1.4): fh:15~120 kHz, fv:24~75 Hz
*HDMI (v. 1.4): fh:15~120 kHz, fv:24~75 Hz

Then by using the CRU I changed the default vertical frequency range from 24-75 to 48-75 and the problem is fixed.
But my question is the reason why the monitor can't handle the 24-75 range for variable refresh rate is because the monitor has some sort of a fault or because the connection cable I use, or the variable refresh rate range is not as broad as it is specified in the data sheet?

The Gpu I use is Nvidia Gtx1080, and the monitor is connected with a Displayport cable which's version I assume is 1.2.
Also, it should be noted that the default Freesync range in the Data blocks section is 48-75.

I would be appreciated if you could help me about it.
Thanks in advance!

The frequency range in the specs is not necessarily the frequency range supported with FreeSync. You didn't mention what monitor you have. What is the advertised FreeSync range? If there's already a FreeSync data block by default with the range 48-75 Hz, then that might be the correct range. DisplayPort doesn't normally use the FreeSync data block, so maybe NVIDIA's driver is using the range limits instead. If the range limits is used for FreeSync, the horizontal range should be two equal values like 120-120 kHz.

Thank you for your reply.
The monitor is ViewSonic VA3209-2K.
Since this is my first time with a monitor that has variable refresh rate feature, I thought that the frequency range is also range for variable refresh rate.
I have checked the monitor's webpage and its manual but there is no advised/advertised range for variable refresh rate.

And your guess is correct, upper and lower horizontal range limits are equal to each other.

So, in this case is there any need to touch/change anything else other than vertical rate limits? For instance the other data blocks, such as colorimetry, hdr static metadata, video capability etc.

Thanks a lot!

[Jenno7]

(03-26-2023 03:39 PM)ToastyX Wrote:  

(03-24-2023 10:52 PM)Jenno7 Wrote:  I did 78hz before, it's been about 1 year but i cant again 1024x768 75hz and 78hz

How did you do it before? With CRU or some other way? 1024x768 is not the native resolution. You can't add non-native resolutions on laptops with CRU because they don't have scalers. The old GPU method doesn't work for laptop screens, only external monitors.

can i do 1366x768 (main res) 75hz? i did wtih CRU. i don't remember how i did it my gpu hd8670m i54200u (hd4400)

[PLU]

(03-26-2023 03:39 PM)ToastyX Wrote:  The first post tells you why it turns red and what to do.

Well, it says to add a DisplayID extension block but I don't know what I'm supposed to do after that. I've added a DisplayID 2.0 detailed resolution with CVT-RB/2 timings.

[Cronus]

AW2521h
When I set a custom resolution in Nvidia control panel, restart, then run CRU it does not show up it CRU
Also it seems if I make any changes at all to the extension blocks for 300hz and 360hz, they both stop working and forces 240hz only in Nvidia control panel, I can create 363hz on Nvidia control panel and CRU but cannot make any changes on CRU, it only allows me to use "Automatic PC" timing