Custom Resolution Utility (CRU)

[ApolloPM]

Hi,

I have a OLED Monitor (FO32U2P) with a default HDR EDID metadata of 465 nits, and I am trying to override this because it is too dim.

RTX HDR uses this EDID value to set the max peak brightness, so 465 nits of peak brightness is unusable, highlights are only at 465 nits and average brightness is only at like 150-200 nits, when this monitor can do peak 1050 nits in Windows HDR Calibration tool and AutoHDR.

In Windows AutoHDR it is properly displaying highlights of 1000 nits with average brightness of around 300-400 nits.

RTX HDR also ignores Windows HDR Calibration so that's not a usable alternative. Overriding the EDID is the only way.

I tried overriding using CRU method but it doesn't seem to work, is this related to the issues you guys are describing with Nvidia drivers recently? Here is how I am using CRU, maybe I skipped something?


1. Run CRU and made sure I am under "FO32U2P (active)" tab.

2. Double clicked on CTA-861 inside of Extension blocks.

3. Double clicked on HDR static metadata under Data blocks.

4. Changed Max Luminance (current: 103) and Max frame-avg (current: 79) to 139. (value of 139 equates to around 1000 nits, 103 is 465 nits)

5. Pressing OK to all subsequent windows until CRU finally closes.

6. Repeated Steps 1-5 to make sure the Max Luminance and Max frame-avg are still set to 139 - Confirmed.

7. Closed CRU and hit restart.exe (also tried restart64.exe).

8. Reboot computer for good measure.

Still shows up as 465 nits in RTX HDR.

[ToastyX]

(04-29-2024 08:18 AM)ApolloPM Wrote:  Hi,

I have a OLED Monitor (FO32U2P) with a default HDR EDID metadata of 465 nits, and I am trying to override this because it is too dim.

RTX HDR uses this EDID value to set the max peak brightness, so 465 nits of peak brightness is unusable, highlights are only at 465 nits and average brightness is only at like 150-200 nits, when this monitor can do peak 1050 nits in Windows HDR Calibration tool and AutoHDR.

In Windows AutoHDR it is properly displaying highlights of 1000 nits with average brightness of around 300-400 nits.

RTX HDR also ignores Windows HDR Calibration so that's not a usable alternative. Overriding the EDID is the only way.

I tried overriding using CRU method but it doesn't seem to work, is this related to the issues you guys are describing with Nvidia drivers recently? Here is how I am using CRU, maybe I skipped something?

Run this and post the test.txt here: https://www.monitortests.com/EDID-test.zip

[ToastyX]

(04-29-2024 06:21 AM)Bourbo Wrote:  also is there any way to make the nvidia gpu control the outputs, sorry if im being dumb, because i somehow can above 300mhz before reset this laptop

That depends on the laptop, but most laptops don't offer the option. You said it was like that before, which is why you added the custom resolutions.

[ApolloPM]

(04-30-2024 02:01 AM)ToastyX Wrote:  

(04-29-2024 08:18 AM)ApolloPM Wrote:  Hi,

I have a OLED Monitor (FO32U2P) with a default HDR EDID metadata of 465 nits, and I am trying to override this because it is too dim.

RTX HDR uses this EDID value to set the max peak brightness, so 465 nits of peak brightness is unusable, highlights are only at 465 nits and average brightness is only at like 150-200 nits, when this monitor can do peak 1050 nits in Windows HDR Calibration tool and AutoHDR.

In Windows AutoHDR it is properly displaying highlights of 1000 nits with average brightness of around 300-400 nits.

RTX HDR also ignores Windows HDR Calibration so that's not a usable alternative. Overriding the EDID is the only way.

I tried overriding using CRU method but it doesn't seem to work, is this related to the issues you guys are describing with Nvidia drivers recently? Here is how I am using CRU, maybe I skipped something?

Run this and post the test.txt here: https://www.monitortests.com/EDID-test.zip

Here you go, this is with my CRU settings still active.
The Gigabyte FO32U2P is the one that is named "GBT3215"

[Potty]

Hello! Please help to understand. I have a monitor Gigabyte m27q. When connecting to my old laptop, I cannot use extended 2560x1440 60Hz. Through the program, I realized that I can only use the general pixel frequency limits of no more than 225 Mhz. I don't understand why this is so, because when installing any of the linux, I can use the extension 2560x1440 60Hz as well as 1920x1080 120Hz. On the Windows system, it can only be 1920x1080 96Hz and 2560x1440 55Hz, but no more

[Tealc]

(03-29-2023 03:30 PM)PLU Wrote:  

(03-26-2023 09:43 PM)ToastyX Wrote:  That's all you need to do to add the resolution. Make sure to delete the old resolution in the other extension block so that doesn't take effect.

Ok so that was the issue and now it's applying, however if I edit the vertical blanking until it downclocks or use CVT-RB(2) it can go down to 200 Hz but the monitor starts to perform really poorly. There's a noticeable input delay and the refresh rate definitely isn't 165 Hz even if it's reported as such. I can't say for sure but it feels and looks like it's just 60 Hz. Even the UFO test says it's 165 Hz but maybe it's just reading what Windows is reporting.
I tried copypasting my default 165 Hz timings (that trigger max VRAM clock) to make sure what I'm editing actually works and yes, it does perform as it should.

This is how CRU looks by default, I copy the top resolution timings, delete the extension block and add a new DisplayID 2.0 one with the pasted timings and then edit them. If I apply that and restard I only have two selectable refresh rates in Windows: 60 Hz (I'm assuming this is the detailed resolution in the main window of CRU at the top) and the 165 Hz one I created.

Hello!

I have the same monitor and the same issue as you. Have you managed to find a solution?

Thanks!

P.S. I managed to make mine work at 155Hz with no apparent loss in performance, but it's the maximum before the limit hits.

[ToastyX]

(04-30-2024 02:08 PM)Potty Wrote:  Hello! Please help to understand. I have a monitor Gigabyte m27q. When connecting to my old laptop, I cannot use extended 2560x1440 60Hz. Through the program, I realized that I can only use the general pixel frequency limits of no more than 225 Mhz. I don't understand why this is so, because when installing any of the linux, I can use the extension 2560x1440 60Hz as well as 1920x1080 120Hz. On the Windows system, it can only be 1920x1080 96Hz and 2560x1440 55Hz, but no more

The GPU's driver limits the pixel clock. It must be a very old GPU to have that limit.

[ToastyX]

(04-30-2024 05:25 AM)ApolloPM Wrote:  Here you go, this is with my CRU settings still active.
The Gigabyte FO32U2P is the one that is named "GBT3215"

That seems to be one of the monitors impacted by the NVIDIA driver bug. The driver ignores EDID overrides for monitors with the extension override data block even if the data block is deleted. Are you using HDMI? What happens if you use DisplayPort?

[ApolloPM]

(05-02-2024 12:15 AM)ToastyX Wrote:  

(04-30-2024 05:25 AM)ApolloPM Wrote:  Here you go, this is with my CRU settings still active.
The Gigabyte FO32U2P is the one that is named "GBT3215"

That seems to be one of the monitors impacted by the NVIDIA driver bug. The driver ignores EDID overrides for monitors with the extension override data block even if the data block is deleted. Are you using HDMI? What happens if you use DisplayPort?

No luck with both HDMI and DP.
I think I'm just going to wait for a firmware update at this point.

[Nyaako]

Need help in getting modified VRR range to stick on a LG 27GR95QE-B with HDMI 2.1.

Modified VRR range from 48-240 to 85-240 in both "Range Limits" and "FreeSync range" because I'm trying to mitigate as much VRR flickering as I can using LFC.
When I game at 60-80fps+ and it shows VRR working with the refresh rate at 120Hz+ and such after using restart64.exe, but the issue is after I restart my entire PC and suddenly the VRR range is messed up and doesn't activate LFC at 60-80fps+ unless I limit the game to 57 fps or below (CRU still shows the modified VRR ranges at 85-240). Have to use reset-all.exe and re-configure the VRR range again.

For the record, this seems to be an issue when using HDMI 2.1 on my end. When I use DisplayPort, the modified VRR range works as intended even after restarting my PC. The reason why I'm not using DisplayPort is to avoid relying on DSC for 1440p 240Hz (and using HDR).