Monitor Tests Forum

Hello Toastyx. I want to thank you for your insights which inspired me to solve all the problems I had.

The solution was obvious and I feel like a dumb-ass for not considering it earlier....which I did without even realising.

In the end I created a DisplayID extension block with a custom resolution of 2160p @ 96hz (custom timings) and saved it along with the original CEA-861 extension block. When I rebooted, my 120hz selection was replaced by the 96hz and I was able to choose 4:4:4 10 bit colour and full range.

To add a cherry on top, I went into TV resolution in the CEA-861 extension block and deselected 1920x1080 @ 60hz as Native format so now Madvr's native resolution shows as 3840x2160 rather than 1920x1080 had I not done that.

Cheers dude

I read a few pages in this thread, but did not find an answer. I hope I have not just missed it.

I got an Iiyama GB3466WQSU with its new firmware and I only got the menu flickering stuff when using G-Sync / Freesync on my GTX1070.
But in some game menus the flickering is so bad, that it really annoys me. It can easily be reproduced in the Pendulum demo by settings the FPS range between 25 and 144Hz.

So I decided to try CRU to change the freesync range from 48-144Hz to something like 68-144Hz.

I am using a Display Port cable, but nontheless I change the freesync range in CRU at the top "Edit" and in the "Extension blocks" as well.
After that I tried restart64.exe, restart.exe and I also restarted the whole PC.

When I test the settings in the Pendulum demo the Monitor OSD still shows frequencies lower than 68Hz and also the flickering is still there.

Anyone got an idea what I do wrong? Or maybe I simply misunderstood the usage of CRU

Hello, I am a new user and trying to get CRU to work. I have an 49LGNANO85UNA, which supports 120hz in 1440p and 1080p, and my objective is to get it recognized by Windows as such, and driven in 2560x1440@120Hz, so I can play racing games. The graphics card is an Nvidia RTX 3080. The monitor is connected via a Displayport to HDMI cable.

I was able to get the monitors to 2560x1440, but at a lower frequency (60Hz). It seems that the only resolutions that (in the default Windows/NVIDIA) configuration go up to 120Hz are those 1080p (e.g. 1920x1080). I have checked the TV specs, and several benchmarks and they do mention that the TV supports 120Hz in 1440p resolution, which is what I want to achieve. So, problem #1 is getting the TV to 2560x1440@120Hz.

After trying various iterations with CRU, without success. I decided to go as minimalistic as possible, to see if I could debug the problem. I used CRU to get to the following configuration:

• 2560x1440 @ 120Hz (483.40Mhz) listed as the *only* "Detailed Resolution"
• No "Standard Resolutions" (I deleted them all)
• In the CEA-861 Extension Block:
  • Deleted all "TV resolutions"
  • Within "HDMI Support" I deleted all the "HDMI resolutions"
  • In "4:2:0 resolutions" I deleted them all as well.
    

Needless to say, it did not work. After rebooting the computer, the monitor defaulted to 1024x768 with only 800x600 as an alternative resolution.

I then did the same setup as above, but tried it as "LCD - standard" (instead of the "LCD - native" I had used the first time). Same results.

Then, I tried to add 2560x1440/120Hz as a "standard resolution" but it is not listed in the drop-down menu. What is more, when you try "Custom Resolution" and enter the values 2560, 1440, and 120hz, the first two are in red and of course CRU does not let you create such a resolution.

Finally, I tried to create this resolution within the "HDMI Support" part of the "CEA-861" extension block, but in such a case it asks me for "code" for the resolution and I have no idea which code to use for 2560x1440/120Hz.

Apologies for the length of this email. Any/all advice is appreciated.

Thanks
Luis

(10-25-2020 06:02 PM)lblando Wrote: [ -> ]Hello, I am a new user and trying to get CRU to work. I have an 49LGNANO85UNA, which supports 120hz in 1440p and 1080p, and my objective is to get it recognized by Windows as such, and driven in 2560x1440@120Hz, so I can play racing games. The graphics card is an Nvidia RTX 3080. The monitor is connected via a Displayport to HDMI cable.

You need HDMI 2.0 to use such a resolution. It's better to connect using HDMI directly. If you use a DisplayPort-HDMI adapter, it must support HDMI 2.0.

(10-25-2020 12:36 PM)slaindevil Wrote: [ -> ]I read a few pages in this thread, but did not find an answer. I hope I have not just missed it.

I got an Iiyama GB3466WQSU with its new firmware and I only got the menu flickering stuff when using G-Sync / Freesync on my GTX1070.
But in some game menus the flickering is so bad, that it really annoys me. It can easily be reproduced in the Pendulum demo by settings the FPS range between 25 and 144Hz.

So I decided to try CRU to change the freesync range from 48-144Hz to something like 68-144Hz.

I am using a Display Port cable, but nontheless I change the freesync range in CRU at the top "Edit" and in the "Extension blocks" as well.
After that I tried restart64.exe, restart.exe and I also restarted the whole PC.

When I test the settings in the Pendulum demo the Monitor OSD still shows frequencies lower than 68Hz and also the flickering is still there.

Anyone got an idea what I do wrong? Or maybe I simply misunderstood the usage of CRU

I don't know how it works with NVIDIA, but with AMD, just changing the low end of the FreeSync range should work. I don't think that monitor has issues on the low end of the range though. Try reducing the refresh rate to 140 Hz instead. You'll have to change the both detailed resolution and the range.

(10-24-2020 08:34 PM)ToastyX Wrote: [ -> ]

(10-24-2020 03:20 PM)slobo2712 Wrote: [ -> ]Ok,so there is no way..except to buy graphic card.Btw which is better 4k60hz or 1080p120hz?

Better for what?

Seems that this CPU/GPU cant do 4k60hz via HDMI anyway that might be a issue?

https://ark.intel.com/content/www/us/en/...0-ghz.html

(10-26-2020 09:10 AM)slobo2712 Wrote: [ -> ]Seems that this CPU/GPU cant do 4k60hz via HDMI anyway that might be a issue?

https://ark.intel.com/content/www/us/en/...0-ghz.html

Max resolution means nothing. It's the pixel clock that matters. You would need HDMI 2.0 for 3840x2160 @ 60 Hz without 4:2:0.

(10-25-2020 09:03 PM)ToastyX Wrote: [ -> ]I don't know how it works with NVIDIA, but with AMD, just changing the low end of the FreeSync range should work. I don't think that monitor has issues on the low end of the range though. Try reducing the refresh rate to 140 Hz instead. You'll have to change the both detailed resolution and the range.

Thanks for you reply. I tried it with 140Hz, but this just led to very weird artifacts in the lower quarter of the screen.
I think I will return the monitor and try to get my hands on an IPS / G-Sync unit. But thank you.

I'm trying to remove all resolutions, with the exception of 2560x1080@120Hz on a fit-Headless (GS). The problem is not running at this resolution (it can run at this resolution out of the box), the problem is that Parsec for some reason resets the resolution to 1920x1080 every time I connect, despite 2560x1080 working just fine once I manually change it. Even with every resolution being removed from the EDID with CRU, Windows (and thus parsec) still detects 1920x1080 as a valid resolution. Are there any extra steps I can take to ensure 2560x1080 is the only resolution?

(10-26-2020 10:19 PM)MonopolyMan Wrote: [ -> ]I'm trying to remove all resolutions, with the exception of 2560x1080@120Hz on a fit-Headless (GS). The problem is not running at this resolution (it can run at this resolution out of the box), the problem is that Parsec for some reason resets the resolution to 1920x1080 every time I connect, despite 2560x1080 working just fine once I manually change it. Even with every resolution being removed from the EDID with CRU, Windows (and thus parsec) still detects 1920x1080 as a valid resolution. Are there any extra steps I can take to ensure 2560x1080 is the only resolution?

The graphics driver automatically adds some common lower resolutions as scaled resolutions. For NVIDIA, search the registry for NV_Modes.