Monitor Tests Forum

I have a quick ish 360Hz question - My G-Sync range is 1-360 obviously as it's the AW2521H

But as we know, CRU can't get the info it needs from NV's reporting because they're being difficult with the way they display information.

With it saying 1-255 as the VRR range, am I not able to change this to 65-255 and have that apply for the real VRR range of 1-360? (aka it would be 65-360?)

Although it's a native g-sync module and does all framerates at any range - there's an awkward unexplainable benefit to this 60fps vsync'd game I'm playing when a g sync module monitor has the VRR range minimum placed at 55-65 for a 240hz, rather than sub 20 for the minimum.

(12-27-2020 03:50 PM)ToastyX Wrote: [ -> ]

(12-27-2020 03:34 PM)jarkid Wrote: [ -> ]1. The flickering is like this: https://youtu.be/rfGM_hV6UlE?t=49
shortly and occasionally in game or effect other programs outside. It's really annoying.

You said the whole screen flickers. That video only shows flickering in BlueStacks, which would be a problem with the software. I don't see how blanking could affect software like that.

Hi,ToastyX,

Last time I changed a monitor, it's the same.

Right now, I just bought a new nVidia card - GTX 1660 ... and the problem has been resolved...

So the root cause is the AMD Video card(RX570) + 75Hz monitor + the Android simulator don't co-exist well...

Although I can use CRU to resolve the problem, I still want to find the root cause, that's why I bought a new card to test it...

(12-28-2020 03:29 PM)jarkid Wrote: [ -> ]So the root cause is the AMD Video card(RX570) + 75Hz monitor + the Android simulator don't co-exist well...

Yes, but that doesn't affect the whole screen, so I don't understand why blanking would make any difference. Either it's a driver bug or a bug in BlueStacks.

(12-28-2020 08:06 AM)diakou Wrote: [ -> ]With it saying 1-255 as the VRR range, am I not able to change this to 65-255 and have that apply for the real VRR range of 1-360? (aka it would be 65-360?)

Native G-Sync monitors don't use the EDID to control the range, so you can't change the range unless they changed something with newer monitors.

(12-27-2020 11:03 PM)chillly Wrote: [ -> ]I'm thinking it's not a matter of support but more of a matter of getting Windows to send DD instead of PCM, which may not be a EDID issue. I'm at 4k but I can send 4k@60 through my receiver and games sends 7.1 PCM fine if I configure that 'monitor' as 7.1 speakers (which it has the option to). But I know my TV can't send 7.1 PCM back through ARC, so need it to encode it. And I'm running freesync to the TV. When I'm playing a movie or something from like Kodi that starts with a DD signal, it will passthrough ok.

I don't know what's required for DD/AC-3 to work. I don't have anything that uses formats other than basic LPCM audio.

Hey there, so I'm having an issue setting a custom refresh rate with my native resolution. I have a 3440x1440 144Hz monitor that I wish to cap at 143Hz. It's an obscure issue but the TLDR is that my monitor occasionally skips every other frame down to 72hz at 144hz when the input is changed but does not have the same behavior at 145hz or 143hz. The issue is I can't set 10-bit color in the Nvidia control panel with a non-native refresh rate. Obviously, CRU fixes this issue but nonetheless, it will not accept any refresh rate above 122hz. I've attached a screenshot showing the issue with setting it to 144hz at 3440x1440 which is the monitor's native resolution and refresh rate. If anyone has any ideas it would be greatly appreciated. Thanks!

I'm having trouble getting CRU resolutions to show up.

Using a `qnix.inf` file from another thread, I was able to set my Qnix QX2710 to 87 hz without artifacts using the Nvidia control panel.

I was inspired to use CRU to push the refresh rate even higher, many people have luck with my same monitor going up to 120hz.

Unfortunately, all detailed resolutions with custom refresh rates I add do not show up in windows 10 control panel or nvidia control panel, no matter if I reboot or do restart64. In the windows dialog the options are 59 and 60 always, and in nvidia there is always only 60.

When using the qnix.inf driver the display appeared in windows as QX2710. I also tried reverting to the microsoft 2006 driver and now it says "generic pnp monitor". Neither display driver seems to allow my custom resolutions to appear.

I also tried deleting my custom resolution from nvidia control panel, running reset-all, and even enabling the DSR in nvidia control panel (which disables custom resolutions).

It's connected via a active displayport adapter called dell bizlink (dvi dual link). Maybe this is the problem? But 87hz worked using Nvidia Control panel.

This monitor is quite popular, and I've seen ToastyX post with some detail about them (maybe they have one?) Just looking for guidance where I should be troubleshooting (display driver, nvidia driver, CRU settings, etc).

(12-30-2020 06:14 AM)jcarrz1 Wrote: [ -> ]When using the qnix.inf driver the display appeared in windows as QX2710. I also tried reverting to the microsoft 2006 driver and now it says "generic pnp monitor". Neither display driver seems to allow my custom resolutions to appear.

I fixed it by adding a displayId extension. Don't think anything else mattered.

New question, "LCD Reduced" is working for 90hz (higher than I achieved with nvidia control panel). The colors are perfect, no artifacts. However, on this new CRU preset (and the 87 I'd come up with in nvidia control panel) the rightmost column of pixels is either pink or white all the way down the right side of my monitor. I think it's just 1 pixel column, maybe 2, very thin.

Is this a common artifact? Does it mean i'm pushing the display too hard? everything else about the image is great.

Thanks!

(12-30-2020 06:46 PM)jcarrz1 Wrote: [ -> ]I fixed it by adding a displayId extension. Don't think anything else mattered.

New question, "LCD Reduced" is working for 90hz (higher than I achieved with nvidia control panel). The colors are perfect, no artifacts. However, on this new CRU preset (and the 87 I'd come up with in nvidia control panel) the rightmost column of pixels is either pink or white all the way down the right side of my monitor. I think it's just 1 pixel column, maybe 2, very thin.

Is this a common artifact? Does it mean i'm pushing the display too hard? everything else about the image is great.

That's not a common artifact for that monitor, and that monitor can easily handle more than 90 Hz. You might be hitting the limits of the adapter. The adapter might not be converting the signal correctly.

I'm curious about the limits you're hitting. Normally that kind of adapter is limited to 357 MHz pixel clock with 8 bpc color and 476 MHz with 6 bpc, so I'm not sure where 87 Hz comes from. Whatever the case, the limit is probably related to the pixel clock and how much the adapter can handle.

"LCD reduced" also matches "LCD standard" at 2560x1440 @ 90 Hz, so I'm wondering how you got more with CRU than the NVIDIA control panel. The same timing parameters should work the same with both. The NVIDIA control panel matches "LCD native" by default, or the same as clicking "Add..." and changing only the refresh rate. "LCD standard" actually increases the vertical blanking with the refresh rate, so that should get you less.

I also don't understand why adding a DisplayID extension block would make a difference. Was there a "Default extension block" by default? That monitor incorrectly reports having an extension block when it doesn't, but CRU has automatic workarounds for that if it can read the extension block and see there's no data.

(12-30-2020 05:19 AM)Skok Wrote: [ -> ]Hey there, so I'm having an issue setting a custom refresh rate with my native resolution. I have a 3440x1440 144Hz monitor that I wish to cap at 143Hz. It's an obscure issue but the TLDR is that my monitor occasionally skips every other frame down to 72hz at 144hz when the input is changed but does not have the same behavior at 145hz or 143hz. The issue is I can't set 10-bit color in the Nvidia control panel with a non-native refresh rate. Obviously, CRU fixes this issue but nonetheless, it will not accept any refresh rate above 122hz. I've attached a screenshot showing the issue with setting it to 144hz at 3440x1440 which is the monitor's native resolution and refresh rate. If anyone has any ideas it would be greatly appreciated. Thanks!

Please read the first post.