Custom Resolution Utility (CRU)
|
04-29-2024, 08:18 AM
(Last edited: 04-29-2024, 08:34 AM by ApolloPM)
Post: #8157
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
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. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 61 Guest(s)