Monitor Tests Forum

(10-05-2023 12:20 PM)Dstendo Wrote: [ -> ]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)

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

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?

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?

CVT-RB2 is a newer standard that some monitors don't support, but it's not necessary. You can start with CVT-RB and then manually reduce the blanking/totals to reduce the pixel clock. Those calculators don't tell you the pixel clock limit, which is the most important point. DisplayPort 4-lane HBR3 is limited to 1080 MHz pixel clock at 8 bpc without DSC. Usually it's the reduced horizontal blanking of CVT-RB2 that monitors can't handle, so you can reduce the vertical blanking instead. 4000x2250 totals will get you exactly 120 Hz at 1080 MHz pixel clock. In fact, "Exact" timing already does this, but if you have issues close to the limit, you can try something lower like 4000x2225, which will also give you exactly 120 Hz but at 1068 MHz.

(10-05-2023 03:08 PM)ToastyX Wrote: [ -> ]

(10-05-2023 12:20 PM)Dstendo Wrote: [ -> ]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)

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

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?

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?

CVT-RB2 is a newer standard that some monitors don't support, but it's not necessary. You can start with CVT-RB and then manually reduce the blanking/totals to reduce the pixel clock. Those calculators don't tell you the pixel clock limit, which is the most important point. DisplayPort 4-lane HBR3 is limited to 1080 MHz pixel clock at 8 bpc without DSC. Usually it's the reduced horizontal blanking of CVT-RB2 that monitors can't handle, so you can reduce the vertical blanking instead. 4000x2250 totals will get you exactly 120 Hz at 1080 MHz pixel clock. In fact, "Exact" timing already does this, but if you have issues close to the limit, you can try something lower like 4000x2225, which will also give you exactly 120 Hz but at 1068 MHz.

Thank you so much, this helped a lot. I now use 4000x2225 and it works perfectly.
I have another question regarding the pixel clock limit.
In CRU, it says in the Display Properties that the max. pixel clock of my monitor is 1070 MHz.
[attachment=1245]
Do I have to look out for this too?
If I go above 1070 MHz, am I overclocking my monitor?
Also, if I would use 4000x2168, would it look a lot different to my eye than 4000x2225?
I also found out that I can use this pixel clock calculator (https://www.monitortests.com/pixelclock....clock=1080) which is very helpful.
And is there any way that I can know if my PC is using DSC. Like a detection programm or something.

(10-05-2023 04:59 PM)Dstendo Wrote: [ -> ]Thank you so much, this helped a lot. I now use 4000x2225 and it works perfectly.
I have another question regarding the pixel clock limit.
In CRU, it says in the Display Properties that the max. pixel clock of my monitor is 1070 MHz.

Do I have to look out for this too?
If I go above 1070 MHz, am I overclocking my monitor?
Also, if I would use 4000x2168, would it look a lot different to my eye than 4000x2225?
I also found out that I can use this pixel clock calculator (https://www.monitortests.com/pixelclock....clock=1080) which is very helpful.
And is there any way that I can know if my PC is using DSC. Like a detection programm or something.

I've never seen the reported max pixel clock matter, so I wouldn't worry about it. DisplayPort is packet-based and runs at fixed clock speeds, so it's more a matter of whether the monitor can handle the resolution and refresh rate. The blanking mainly affects how long to wait between each line and frame, so it wouldn't visibly affect the image. The driver doesn't seem to report if DSC is active or not, but NVIDIA doesn't support scaling features such as DSR, DLDSR, and image scaling with DSC unless something changed recently, so that might be one clue.

So for the purpose of using dldsr in 16:9 on a 21:9 screen. I need to make 2560x1440 my default resolution that nvidia detects.

To do this , we'll all my resolutions were the 3440x1440 ones , so I simply changed them all to 2560x1440 and didn't touch anything else.

It appeared to work, however when selecting any hz besides 60 or 120 I get a black screen. My options are 60 100 120 144 175

For reference, I can use other hz such as my native 175 on 2560x1440 when choosing it in the nvcp when I don't make changes by removing the 3440x1440 ones with cru, or rather changing them to 2560x1440 ones would be more exact.

So something about 2560x1440 now being my native resolution caused this maybe?

I tried going back into cru and tried different timings such as exact reduced, yet sadly to no avail.

I'm extremely fresh to this all so excuse my ignorance. Could I please get some assistance? It would be very appreciated

For reference I'm trying to use a 175hz, which is my monitors native max. And considering g sync exists , I haven't the need to play at anything lesser. So as long as I can get that working that's plenty for me!

Aw3423dw. Newest GeForce driver, let me know if there's any other information I should provide.

Thanks in advance!

Edits for new information:

turns out any of my other resolutions in the nvcp , such as 1920x1080 , don't work at 175hz either.

Deleting every other displayId resolution besides the 175hz one didn't work

Deleting all extensionblock resolutions besides the 175hz one hasn't either.

Rebooting my pc hasn't worked.

When changing the display ID from 1.3 to 2.0 the 175hz option dissapears from nvcp (its the only resolution left as i deleted the rest, minus the default 60hz one ofc)

And when having both a display ID 1.3 and 2.0 175hz resolution, I do see the option to choose it again, yet I black screen.

(10-08-2023 11:01 PM)Troco72 Wrote: [ -> ]So for the purpose of using dldsr in 16:9 on a 21:9 screen. I need to make 2560x1440 my default resolution that nvidia detects.

To do this , we'll all my resolutions were the 3440x1440 ones , so I simply changed them all to 2560x1440 and didn't touch anything else.

It appeared to work, however when selecting any hz besides 60 or 120 I get a black screen. My options are 60 100 120 144 175

For reference, I can use other hz such as my native 175 on 2560x1440 when choosing it in the nvcp when I don't make changes by removing the 3440x1440 ones with cru, or rather changing them to 2560x1440 ones would be more exact.

So something about 2560x1440 now being my native resolution caused this maybe?

I tried going back into cru and tried different timings such as exact reduced, yet sadly to no avail.

I'm extremely fresh to this all so excuse my ignorance. Could I please get some assistance? It would be very appreciated

For reference I'm trying to use a 175hz, which is my monitors native max. And considering g sync exists , I haven't the need to play at anything lesser. So as long as I can get that working that's plenty for me!

Aw3423dw. Newest GeForce driver, let me know if there's any other information I should provide.

Thanks in advance!

Monitors with NVIDIA's G-SYNC hardware only support a limited combination of resolutions and refresh rates. The AW3423DW only seems to support 60 Hz and 120 Hz at 2560x1440. The graphics driver automatically adds some common resolutions as scaled resolutions. If 2560x1440 didn't exist in CRU by default, then it was being scaled to 3440x1440 by the GPU.

(10-08-2023 11:40 PM)ToastyX Wrote: [ -> ]

(10-08-2023 11:01 PM)Troco72 Wrote: [ -> ]So for the purpose of using dldsr in 16:9 on a 21:9 screen. I need to make 2560x1440 my default resolution that nvidia detects.

To do this , we'll all my resolutions were the 3440x1440 ones , so I simply changed them all to 2560x1440 and didn't touch anything else.

It appeared to work, however when selecting any hz besides 60 or 120 I get a black screen. My options are 60 100 120 144 175

For reference, I can use other hz such as my native 175 on 2560x1440 when choosing it in the nvcp when I don't make changes by removing the 3440x1440 ones with cru, or rather changing them to 2560x1440 ones would be more exact.

So something about 2560x1440 now being my native resolution caused this maybe?

I tried going back into cru and tried different timings such as exact reduced, yet sadly to no avail.

I'm extremely fresh to this all so excuse my ignorance. Could I please get some assistance? It would be very appreciated

For reference I'm trying to use a 175hz, which is my monitors native max. And considering g sync exists , I haven't the need to play at anything lesser. So as long as I can get that working that's plenty for me!

Aw3423dw. Newest GeForce driver, let me know if there's any other information I should provide.

Thanks in advance!

Monitors with NVIDIA's G-SYNC hardware only support a limited combination of resolutions and refresh rates. The AW3423DW only seems to support 60 Hz and 120 Hz at 2560x1440. The graphics driver automatically adds some common resolutions as scaled resolutions. If 2560x1440 didn't exist in CRU by default, then it was being scaled to 3440x1440 by the GPU.

I'm so confused as I'm currently using 2560x1440 at 175hz. And I've been using it. I also just set the native resolution to 2560x1440 in cru *withOUT* deleting the other 3440x1440 resolutions/changing them to 2560x1440.

And it works , I can use 2560x1440 at 175 hz. It's selected and applied right now currently with this cru setup, and when not using cru I obviously could select it too , but even when using it to change my native resolution I can choose 175hz.

However only when I remove the 3440x1440 resolutions or change them. Then I can't use said refresh rate.

Am I missing something? Why am I always able to use 2560x1440 at every single hz the monitor comes with UNTIL I do the specific cru action of getting rid of the 3440x1440 resolutions that are attached to said refresh rates?

Thank you for taking the time to respond

Also unfortunately having my native resolution at 2560 isn't enough, I guess nvidia chooses the silly route of basing dldsr off your max resolution not your native.

Would you know any way I could use your program to get around this?

(10-09-2023 12:05 AM)Troco72 Wrote: [ -> ]I'm so confused as I'm currently using 2560x1440 at 175hz. And I've been using it. I also just set the native resolution to 2560x1440 in cru *withOUT* deleting the other 3440x1440 resolutions/changing them to 2560x1440.

And it works , I can use 2560x1440 at 175 hz. It's selected and applied right now currently with this cru setup, and when not using cru I obviously could select it too , but even when using it to change my native resolution I can choose 175hz.

However only when I remove the 3440x1440 resolutions or change them. Then I can't use said refresh rate.

Am I missing something? Why am I always able to use 2560x1440 at every single hz the monitor comes with UNTIL I do the specific cru action of getting rid of the 3440x1440 resolutions that are attached to said refresh rates?

Thank you for taking the time to respond

Also unfortunately having my native resolution at 2560 isn't enough, I guess nvidia chooses the silly route of basing dldsr off your max resolution not your native.

Would you know any way I could use your program to get around this?

If you have GPU scaling enabled, then all lower resolutions are always scaled by the GPU to the native resolution regardless, so all refresh rates at the native resolution will be available at lower resolutions since the monitor is actually receiving the native resolution.

If you have GPU scaling disabled (display scaling), then any resolutions defined in the EDID as shown in CRU will be sent to the monitor, and any scaled resolutions automatically added by the graphics driver will be scaled by the GPU to the next highest resolution.

In either case, the native resolution is never scaled, so when you delete 3440x1440 to change the native resolution, 2560x1440 is then sent to the monitor instead of being scaled by the GPU, so it will only work at whatever refresh rates the monitor supports at 2560x1440, which happens to be 60 and 120 Hz. There's no way around this since it's a limitation of the monitor.

The Windows advanced display settings will show you the desktop resolution and the active signal resolution. If the desktop resolution is 2560x1440 but the active signal resolution is 3440x1440, then it's being scaled by the GPU. The monitor should also report what resolution and refresh rate it's receiving somewhere in the monitor's menu. It will report 3440x1440 if it's being scaled by the GPU.

(10-09-2023 01:09 AM)ToastyX Wrote: [ -> ]

(10-09-2023 12:05 AM)Troco72 Wrote: [ -> ]I'm so confused as I'm currently using 2560x1440 at 175hz. And I've been using it. I also just set the native resolution to 2560x1440 in cru *withOUT* deleting the other 3440x1440 resolutions/changing them to 2560x1440.

And it works , I can use 2560x1440 at 175 hz. It's selected and applied right now currently with this cru setup, and when not using cru I obviously could select it too , but even when using it to change my native resolution I can choose 175hz.

However only when I remove the 3440x1440 resolutions or change them. Then I can't use said refresh rate.

Am I missing something? Why am I always able to use 2560x1440 at every single hz the monitor comes with UNTIL I do the specific cru action of getting rid of the 3440x1440 resolutions that are attached to said refresh rates?

Thank you for taking the time to respond

Also unfortunately having my native resolution at 2560 isn't enough, I guess nvidia chooses the silly route of basing dldsr off your max resolution not your native.

Would you know any way I could use your program to get around this?

If you have GPU scaling enabled, then all lower resolutions are always scaled by the GPU to the native resolution regardless, so all refresh rates at the native resolution will be available at lower resolutions since the monitor is actually receiving the native resolution.

If you have GPU scaling disabled (display scaling), then any resolutions defined in the EDID as shown in CRU will be sent to the monitor, and any scaled resolutions automatically added by the graphics driver will be scaled by the GPU to the next highest resolution.

In either case, the native resolution is never scaled, so when you delete 3440x1440 to change the native resolution, 2560x1440 is then sent to the monitor instead of being scaled by the GPU, so it will only work at whatever refresh rates the monitor supports at 2560x1440, which happens to be 60 and 120 Hz. There's no way around this since it's a limitation of the monitor.

The Windows advanced display settings will show you the desktop resolution and the active signal resolution. If the desktop resolution is 2560x1440 but the active signal resolution is 3440x1440, then it's being scaled by the GPU. The monitor should also report what resolution and refresh rate it's receiving somewhere in the monitor's menu. It will report 3440x1440 if it's being scaled by the GPU.

That's such a shame. Thanks for taking thentime to fill me in have a good one!

Can you tell me how I can reach the maximum frequency of my monitor? I was able to increase the frequency of my BOE08BE PnP 120Hz monitor to 132.40 Hz using the mode: Exact reduced

Hi, I recently got me a QN800B Samsung for double use as TV, but mostly as monitor (95% of the time). I use it with a 1050ti Nvidia videocard.

It is 'only' 65" big so when watching 8K it is the same as staring to a 32" 4K monitor up close (yeah, pretty stupid). So was looking for a way to change the resolution to 5K 5120x2880 or 6K 6400x3600. But no matter what I've tried, I can do anything from 3840x2160 downwards, but can't find out how or if it is possible at all to show resolutions between 4K and 8K.

Are there safe ways to get there? (blew up my PSU and MOBO died recently after black screen followed by hard shutdown, after messing with resolution settings).

(btw, my advice: stay away from 8K for the time being, as the technology and ecosystem is not ready yet, the things you have to perform to make the screen show 8k content are just ridiculous, messing with 'game mode', 'extra signal', '4:2:0 YCRB' and other trickery)