Scaled Resolution Editor (SRE)

[Nickoglas]

(04-20-2025 10:13 PM)ToastyX Wrote:  

(04-19-2025 06:36 PM)Nickoglas Wrote:  I used to use SRE to create a custom res of 2304x1440 240hz, I installed my 50 series card yesterday and noticed I can no longer use SRE, also can't seem to set the res up in CRU either sadly.

Happened to read a few posts above where someone also just installed a 50 series and can no longer use SRE, so just assuming we have to wait for a fix on nvidias end?

Yes, but you should be able to use CRU. If the monitor can't handle the resolution, you can try GPU scaling.

I managed to create the res in CRU since I last posted. Sorry if this is a stupid question; but what is the difference between display ID 1.3 and 2.0?

I tried to google it but couldn't seem to find out. If I use the extension block and use DisplayID 2.0 I can create the res at 240hz+ but If I try just Display ID 1.3 or the normal detailed resolution etc I can only go up to 179hz.

[ToastyX]

(04-25-2025 10:21 AM)Nickoglas Wrote:  I managed to create the res in CRU since I last posted. Sorry if this is a stupid question; but what is the difference between display ID 1.3 and 2.0?

I tried to google it but couldn't seem to find out. If I use the extension block and use DisplayID 2.0 I can create the res at 240hz+ but If I try just Display ID 1.3 or the normal detailed resolution etc I can only go up to 179hz.

Both DisplayID 1.3 and 2.0 should allow higher refresh rates:
DisplayID 2.0 allows 3 decimal places up to 16777.216 MHz pixel clock.
DisplayID 1.3 allows 2 decimal places up to 167772.16 MHz pixel clock.
EDID allows 2 decimal places up to 655.35 MHz pixel clock.

DisplayID is intended to replace EDID, but it hasn't happened yet. Usually I see DisplayID 1.3 used as an extension block. DisplayID 2.0 is newer and not as common currently.