Custom Resolution Utility (CRU)

[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"