Custom Resolution Utility (CRU)

[ToastyX]

(Today 06:38 AM)Winterfalke Wrote:  Hi, can someone help me understand this?
I have a 45GX950A monitor running at 5120×2160 and 165 Hz. From what I understand, the pixel clock should be around 1900 MHz before DSC (Display Stream Compression) kicks in. DSC is supposed to activate once the display clock exceeds roughly 1620 MHz, and at that point, NVIDIA’s driver should ignore EDID overrides.

However, EDID overrides for HDR do work for me.

Why does the override still work on an RTX 5090? Is this something unique to the monitor, perhaps related to its dual-mode behavior even when it’s not active, or is there another explanation?

I don't know if the limit applies to 5000-series GPUs. So far nobody with a 5000-series GPU has reported the issue.

[Winterfalke]

(Today 11:03 AM)ToastyX Wrote:  

(Today 06:38 AM)Winterfalke Wrote:  Hi, can someone help me understand this?
I have a 45GX950A monitor running at 5120×2160 and 165 Hz. From what I understand, the pixel clock should be around 1900 MHz before DSC (Display Stream Compression) kicks in. DSC is supposed to activate once the display clock exceeds roughly 1620 MHz, and at that point, NVIDIA’s driver should ignore EDID overrides.

However, EDID overrides for HDR do work for me.

Why does the override still work on an RTX 5090? Is this something unique to the monitor, perhaps related to its dual-mode behavior even when it’s not active, or is there another explanation?

I don't know if the limit applies to 5000-series GPUs. So far nobody with a 5000-series GPU has reported the issue.

Thank you for the quick reply. That would explain a few things, since on the same monitor CRU worked for some people but not for others. From what I can tell, the latter had 40-series GPUs.