Custom Resolution Utility (CRU)

[ToastyX]

(09-29-2023 02:45 PM)Dinkles Wrote:  Ahh that’s a shame, why would they build the monitor this way, it’s a new monitor with modern standards (connectors/aspect etc) why would they allow it to register the wrong native res?

I’ve no tried removing them all yet, what would be the bedt way to approach this and remove all resolutions. which fields etc. are safe to remove etc?

Under TV resolutions for example, 5120 isn’t present?
Under displayID 1.3 the only resolution present is 5120 with multiple HZ?
Under standard resolutions 5120 isn’t present?
Under detailed resolutions 5120 isn’t present?

I can drop sone screens of that helps?

Delete all detailed, standard, established resolutions in the main window. In the CTA-861 extension block, delete all detailed resolutions and the TV resolutions data block. That should leave you with only the resolutions in the DisplayID 1.3 extension block.

DisplayID is a standard meant to replace EDID, but adoption has been slow because it's not backward compatible. The AG493UCX is 3.5 years old. Back then I only saw DisplayID being used as an EDID extension block to add higher resolutions and not much else. There should also be a display parameters data block to define the native resolution, which I planned to add to CRU, but when I tested it, the graphics drivers just ignored it. I'll have to revisit that and see if the data block has any effect now. Another issue is HDMI decided to stick with EDID and CTA-861, and CTA-861 has their own method of defining higher native resolutions, so now there are two competing standards that need to be implemented. Actually there are three standards because DisplayID 2.0 has a different format for the display parameters data block. I wanted to implement all this stuff for CRU 2.0, but it probably won't be out until next year because I'm doing a complete rewrite and redesign to better accommodate all these standards with an easier to use interface.