Custom Resolution Utility (CRU)

[GGoki]

(12-22-2025 04:55 PM)ToastyX Wrote:  

(12-22-2025 04:01 PM)GGoki Wrote:  CRU 1.5.3, nvidia 591.44 studio driver, ASUS RTX 5070ti prime


CRU cannot read native resolution of some displays anymore(LS32DG800S, MAG401QR)

how can I solve this?

By anymore, do you mean the EDID changed? Or do you mean for some newer displays? 42 is a different type of data block that CRU doesn't support yet. It will be a while before I add support because it's annoying to edit (varying descriptor sizes) and needs a new UI. It's basically a shorter way of defining resolutions using the CVT standard, so it doesn't give full control over the timing parameters. You can still add detailed resolutions separately, or delete the block and add the resolutions back manually. This is the first time I've seen the data block in the wild, so if you can export the EDID and post it here, that will help when I add support for it later.

On RTX 5000-series graphics cards with the latest drivers, the native refresh rate no longer appears in CRU.
I’m not sure why this is happening, but I believe it’s an issue with the latest driver. The native refresh rate definitely used to be visible a few months ago.
Even in the case of the MAG401QR, this is not a cutting-edge display, and it is well within the pixel clock limit.
Or it could just be my misunderstanding, or it might only apply to the LS32DG800S.
Either way, I’ll extract the EDID file and share it with you later.