Monitor Tests Forum

(09-29-2023 10:45 AM)Dinkles Wrote: [ -> ]Thanks for checking this for me, here is the attached test file as requested, and a screenshot of the NCP showing that the "recommended" resolution vs the actual native resolution.

The monitor is connected via DP and i have tried both DP1/DP2 neither of which make a difference.

I am using a very expensive DP cable capable of DP2.0 8k VESA certified etc.

The monitor works fine, but if i switch to my 4k TV it defaults back to the "recommended" resolution when return and scaling in games simply scales to the incorrect resolution.

Anything you can do to help would be much appreciated.

I checked the test.txt file and the monitor actually doesn't report the native resolution using any of the newer standards, so it's using the first detailed resolution as the native resolution, which has that 4095 limitation. None of the other stuff you mentioned is relevant to the problem. Did you try deleting all the other resolutions like I mentioned? That would leave 5120x1440 as the only option and should make it the recommended resolution in Windows.

(09-29-2023 02:14 PM)ToastyX Wrote: [ -> ]

(09-29-2023 10:45 AM)Dinkles Wrote: [ -> ]Thanks for checking this for me, here is the attached test file as requested, and a screenshot of the NCP showing that the "recommended" resolution vs the actual native resolution.

The monitor is connected via DP and i have tried both DP1/DP2 neither of which make a difference.

I am using a very expensive DP cable capable of DP2.0 8k VESA certified etc.

The monitor works fine, but if i switch to my 4k TV it defaults back to the "recommended" resolution when return and scaling in games simply scales to the incorrect resolution.

Anything you can do to help would be much appreciated.

I checked the test.txt file and the monitor actually doesn't report the native resolution using any of the newer standards, so it's using the first detailed resolution as the native resolution, which has that 4095 limitation. None of the other stuff you mentioned is relevant to the problem. Did you try deleting all the other resolutions like I mentioned? That would leave 5120x1440 as the only option and should make it the recommended resolution in Windows.

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?

(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.

(09-29-2023 03:34 PM)ToastyX Wrote: [ -> ]

(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.

So i think i have done it correctly...
There was an extension of sorts in the bottom block, but i may have deleted the entire thing, i cant remember? I think it was a CTA-861 extension block but its gone now after i removed some data?

However, it still seems to have worked as the monitor now registers 5120 as its recommended res (as per screenshot) and NIS now shows BLUE which means i can use scaling/sharpening again! Fantastic!

However, should i reinstall the monitor, do it again and be more careful, as i may have removed something important from that data block in the extension block or is it all good?

Hopefully you can get 2.0 out with features to fix issues such as these for others, profiles etc for specific monitors etc. as this is a massive fix for me, it essentially fixes all scaling NIS/DLSS etc for me AND stops the monitor resetting every time i switch it off/on or disable and re enable it. Massive help and honestly allows me to use features i was previously unable to use again!

Also the monitor has an option to enable or disable DDC/CI is this of any relevance in this scenario?

Cheers Toasty

(09-29-2023 04:04 PM)Dinkles Wrote: [ -> ]So i think i have done it correctly...
There was an extension of sorts in the bottom block, but i may have deleted the entire thing, i cant remember? I think it was a CTA-861 extension block but its gone now after i removed some data?

However, it still seems to have worked as the monitor now registers 5120 as its recommended res (as per screenshot) and NIS now shows BLUE which means i can use scaling/sharpening again! Fantastic!

However, should i reinstall the monitor, do it again and be more careful, as i may have removed something important from that data block in the extension block or is it all good?

Hopefully you can get 2.0 out with features to fix issues such as these for others, profiles etc for specific monitors etc. as this is a massive fix for me, it essentially fixes all scaling NIS/DLSS etc for me AND stops the monitor resetting every time i switch it off/on or disable and re enable it. Massive help and honestly allows me to use features i was previously unable to use again!

Also the monitor has an option to enable or disable DDC/CI is this of any relevance in this scenario?

Cheers Toasty

The CTA-861 extension block had audio and HDR information in it, so deleting it would disable those features. If you don't use those features, then it doesn't matter. The CTA-861 extension block would be required for HDMI support, but for DisplayPort, it's not required. You can run reset-all.exe and restart to restore the original EDID if you want to edit it again.

DDC/CI allows programs to communicate with the monitor to control settings that are in the monitor's menus, so if you're not using any software for that, then it doesn't matter. Generally there's no need to disable it.

Hello peeps hope for some help!

Got an Samsung g7 1440p. 240hz. When i Enter a lower res at 1600x1200 for cs i get 320hz and for 1770x990 360hz. Pasning ufo tests etc

Heres the Big problem. I love playing 4:3 stretched in cs. Buuuut here we go as soon as i go to amd driver enable gpu scaling to fill the screen it goes Down to 240hz… if i disable gpu scaling i Can run it at 360hz. But want it stretched. Is there a work around for this ???

5800x3d
7900xtx
B550 board
2x16 gig 3800c14

(09-30-2023 07:27 AM)Nord Wrote: [ -> ]Hello peeps hope for some help!

Got an Samsung g7 1440p. 240hz. When i Enter a lower res at 1600x1200 for cs i get 320hz and for 1770x990 360hz. Pasning ufo tests etc

Heres the Big problem. I love playing 4:3 stretched in cs. Buuuut here we go as soon as i go to amd driver enable gpu scaling to fill the screen it goes Down to 240hz… if i disable gpu scaling i Can run it at 360hz. But want it stretched. Is there a work around for this ???

GPU scaling is for scaling to the native resolution, which only has 240 Hz. You need to change the scaling in the monitor's menu.

(09-30-2023 01:39 PM)ToastyX Wrote: [ -> ]

(09-30-2023 07:27 AM)Nord Wrote: [ -> ]Hello peeps hope for some help!

Got an Samsung g7 1440p. 240hz. When i Enter a lower res at 1600x1200 for cs i get 320hz and for 1770x990 360hz. Pasning ufo tests etc

Heres the Big problem. I love playing 4:3 stretched in cs. Buuuut here we go as soon as i go to amd driver enable gpu scaling to fill the screen it goes Down to 240hz… if i disable gpu scaling i Can run it at 360hz. But want it stretched. Is there a work around for this ???

GPU scaling is for scaling to the native resolution, which only has 240 Hz. You need to change the scaling in the monitor's menu.

I Will look for it. Just that i need it to stretch the screen. If i dont have scaling in amd driver its not stretching out the image then i get Black bars

Hello, after purchasing the Asus pg329q, it was possible to use 120Hz (which allowed the use of a 10-bit color depth). Like any decent person with a high level of trust in the manufacturer, a month after the release of the new firmware, the monitor was updated, there was no limit to surprise... 120Hz evaporated, leaving behind the sadness of 60Hz with a depth of 10bit or 144Hz and 165Hz in 8bit. There is no doubt that the chance of getting old firmware is critically small.
I really want to replace the existing 165Hz profile with 120Hz, but I'm worried that I'll screw it up. Maybe there is an owner of a device with old firmware who is ready to put a screenshot from the Custom Resolution Utility for 120Hz settings?

Hello,

I have the Acer XV273K monitor (4K, 120Hz(-144Hz with Dual DP), Ports: 2 x DisplayPort 1.4 & 2 x HDMI 2.0) (https://www.displayspecifications.com/de/model/407f14c5) and a RTX 3080 (Ports: 3 x DisplayPort 1.4a & 2 x HDMI 2.1).
I have had some issues with Black Screens and Alt-Tabbing for a while.
For example, I would Alt-Tab out of GTA V and the screen would go black for a few seconds as if the resolution or refresh rate were being changed. But nothing was changed and it annoyed me.
Then I stumbled upon this Reddit post (https://www.reddit.com/r/OLED_Gaming/com...lttabbing/) where a guy describes my problem and says it's because of DSC. After that, I got into a 4-hour rabbit hole of CRU, and now I know a lot more about it than I would like to.
My issue now:
In CRU if I add a DisplayID 1.3 extension block and add a Detailed Resolution of 3840x2160 with "CVT-RB standard" selected I can use 120Hz and even more with no problems. To avoid DSC, I need to use a refresh rate under 118.2Hz and use 8 bpc and RGB (as per calculator: https://linustechtips.com/topic/729232-g...mulas=show)
[attachment=1239][attachment=1236]
as the monitor only has DP 1.4 and the RTX 3080 only supports DP 1.4a. Altough another site says max. 116.8Hz. (https://tomverbeure.github.io/video_timings_calculator) This also works (although between ~117.8Hz and 119Hz I get some weird jittering of the whole screen, so I just use 116.700Hz).
[attachment=1244]
If I select "CVT-RB2 standard" I should be able to go as high as 120.4Hz,
(calculator: https://linustechtips.com/topic/729232-g...mulas=show)
but I can't.
If I use CVT-RB2, the screen goes crazy with artifacts and green colors and flickering as if he doesn't recognize the signal or something. This only happens with < ~60Hz and sometimes up to ~80Hz, and sometimes I can only go up to 30Hz. It's random?
[attachment=1242][attachment=1243]
I already tried two different 1.4 DP cables (PI5010-020 & BN39-01879N) and recalculated the values that would be needed for CVT-RB2 (https://tomverbeure.github.io/video_timings_calculator) but they were always correct.

I never use the Dual DP mode in the OSD of the monitor for 144Hz as it activates some input lag.
In OSD, the DP Format is set to 1.4, HDMI Black Level on Normal, FreeSync on On, HDR on Off, 4K-144Hz Mode on Off, Wide Mode on Aspect, Color Space on Standard.
Do some monitors just not support CVT-RB2? Or do I have some other settings wrong?