Custom Resolution Utility (CRU)

[Jmatt110]

Quote:That's weird because only NVIDIA custom resolutions are supposed to be listed as custom. CRU resolutions should appear under "PC" unless they changed something recently. Try an older driver like 446.14.

If I edit the default 60Hz resolution in CRU to 90Hz, it shows up in NVCP as a 'PC' resolution. Changing it to 144Hz, or creating a new 144Hz entry always puts it under "Custom resolution".

[Anderkor]

Hello! I had trouble when doing export/import in app - was doing to figure out how to override edid on intel with build-in display. So I'm trying set correct display size (width, height) as my display hasn't, to get proper interaction in multimonitor setup - can You please explain or in any other way show how to do it (mean override edid for intel gpu)?

[ToastyX]

(11-12-2020 05:51 PM)Anderkor Wrote:  Hello! I had trouble when doing export/import in app - was doing to figure out how to override edid on intel with build-in display. So I'm trying set correct display size (width, height) as my display hasn't, to get proper interaction in multimonitor setup - can You please explain or in any other way show how to do it (mean override edid for intel gpu)?

I don't know what you're trying to do. What is wrong with the display size? What is wrong with the multi-monitor setup? Built-in displays usually don't support non-native resolutions, so other resolutions won't display correctly anyway without GPU scaling, which would only work for lower resolutions.

[Anderkor]

(11-13-2020 01:10 AM)ToastyX Wrote:  I don't know what you're trying to do. What is wrong with the display size? What is wrong with the multi-monitor setup? Built-in displays usually don't support non-native resolutions, so other resolutions won't display correctly anyway without GPU scaling, which would only work for lower resolutions.

Sorry for wasting Your time - I had wrong use of edid_override in windows. I've figured out how CRU manages my custom resolution and now I'm able to write my changes. Thank You for attention and great software!

[ahmetomer]

hello

i am using HD5450(i sold my rx580 i am saving up for 6800). I did the ati patcher and 2560x1440p is now uncloked.

but cant i make a 100hz 1440p resolution?

i cant add anything over 1080p in the CRU

is there a way to import settings? if yes how?

thanks

my display is chg70 27

i have hdmi 2.0 and DVI to HDMI cable

[ToastyX]

(11-13-2020 05:44 PM)ahmetomer Wrote:  hello

i am using HD5450(i sold my rx580 i am saving up for 6800). I did the ati patcher and 2560x1440p is now uncloked.

but cant i make a 100hz 1440p resolution?

i cant add anything over 1080p in the CRU

is there a way to import settings? if yes how?

thanks

my display is chg70 27

i have hdmi 2.0 and DVI to HDMI cable

There's no way you're going to get 2560x1440 @ 100 Hz over HDMI with the HD 5450. It doesn't have HDMI 2.0. What settings do you want to import? You can export the settings to a file and import the file.

[AchillesBoi]

Hey ToastyX, I have an issue with CRU. My monitor is an Acer ET322QU (1440p 48-75hz). After using CRU, if I turn my monitor off then on again everything will look dim/faded even if I don't overclock anything. I know it's not my monitor acting strange because the cursor is still white and bright, my monitor's OSD still shows up bright, it is only the rest of the OS that looks dim. If I reset the display driver using restart64 or by pressing Win + Shift + Ctrl + B it will fix the issue, but will present itself again if I turn the monitor off and on.

I am using an RX 480 with the latest drivers (20.11.1), and I'm running the latest version of Windows 10 (October 2020 update). I should note that my monitor does not support HDR and I am not messing with HDR settings on CRU.

Another thing I noticed this bug is causing is that when I turn my monitor off/on the resolution switches to 1024x768 then back to native 1440p. It sucks because sometimes I'll have some windows open and when my monitor turns off/on all my windows are resized to a tiny square and it's frustrating to have to resize everything everytime. I used a remote desktop app to prove this, because when I turn off the monitor and then access my desktop using the remote app I can see how small everything is and I can go to the display settings and it tells me it's at a low resolution.

If I use reset-all.exe it fixes the problem entirely but I lose my overclock. I hope you can help us out because I found a good OC that is helpful for less input lag and would love to use it without having to work around this nasty bug (although it probably has something to do with AMD's drivers).

[ToastyX]

(11-14-2020 12:24 PM)AchillesBoi Wrote:  Hey ToastyX, I have an issue with CRU. My monitor is an Acer ET322QU (1440p 48-75hz). After using CRU, if I turn my monitor off then on again everything will look dim/faded even if I don't overclock anything. I know it's not my monitor acting strange because the cursor is still white and bright, my monitor's OSD still shows up bright, it is only the rest of the OS that looks dim. If I reset the display driver using restart64 or by pressing Win + Shift + Ctrl + B it will fix the issue, but will present itself again if I turn the monitor off and on.

I am using an RX 480 with the latest drivers (20.11.1), and I'm running the latest version of Windows 10 (October 2020 update). I should note that my monitor does not support HDR and I am not messing with HDR settings on CRU.

Another thing I noticed this bug is causing is that when I turn my monitor off/on the resolution switches to 1024x768 then back to native 1440p. It sucks because sometimes I'll have some windows open and when my monitor turns off/on all my windows are resized to a tiny square and it's frustrating to have to resize everything everytime. I used a remote desktop app to prove this, because when I turn off the monitor and then access my desktop using the remote app I can see how small everything is and I can go to the display settings and it tells me it's at a low resolution.

If I use reset-all.exe it fixes the problem entirely but I lose my overclock. I hope you can help us out because I found a good OC that is helpful for less input lag and would love to use it without having to work around this nasty bug (although it probably has something to do with AMD's drivers).

It's an AMD driver bug, so I don't know what to do about it. Are you using HDMI or DisplayPort? Does it happen with one or both? The issue with windows moving around is normal for DisplayPort because DisplayPort doesn't keep a connection when you turn the monitor off, but it shouldn't happen with HDMI.

[AchillesBoi]

(11-14-2020 02:20 PM)ToastyX Wrote:  

(11-14-2020 12:24 PM)AchillesBoi Wrote:  Hey ToastyX, I have an issue with CRU. My monitor is an Acer ET322QU (1440p 48-75hz). After using CRU, if I turn my monitor off then on again everything will look dim/faded even if I don't overclock anything. I know it's not my monitor acting strange because the cursor is still white and bright, my monitor's OSD still shows up bright, it is only the rest of the OS that looks dim. If I reset the display driver using restart64 or by pressing Win + Shift + Ctrl + B it will fix the issue, but will present itself again if I turn the monitor off and on.

I am using an RX 480 with the latest drivers (20.11.1), and I'm running the latest version of Windows 10 (October 2020 update). I should note that my monitor does not support HDR and I am not messing with HDR settings on CRU.

Another thing I noticed this bug is causing is that when I turn my monitor off/on the resolution switches to 1024x768 then back to native 1440p. It sucks because sometimes I'll have some windows open and when my monitor turns off/on all my windows are resized to a tiny square and it's frustrating to have to resize everything everytime. I used a remote desktop app to prove this, because when I turn off the monitor and then access my desktop using the remote app I can see how small everything is and I can go to the display settings and it tells me it's at a low resolution.

If I use reset-all.exe it fixes the problem entirely but I lose my overclock. I hope you can help us out because I found a good OC that is helpful for less input lag and would love to use it without having to work around this nasty bug (although it probably has something to do with AMD's drivers).

It's an AMD driver bug, so I don't know what to do about it. Are you using HDMI or DisplayPort? Does it happen with one or both? The issue with windows moving around is normal for DisplayPort because DisplayPort doesn't keep a connection when you turn the monitor off, but it shouldn't happen with HDMI.

I am using DisplayPort, and even though it loses connection when I turn the monitor off the resolution stays the same if I use default settings. The moment I use CRU the resolution will go all the way down when I turn the monitor off, so I am absolutely sure CRU is doing something here.

I have not tried with HDMI, but I hear DisplayPort is much better so I intend to use that. I have tried deleting all data from CRU: Established resolutions, Standard resolutions, Extension blocks, and all Detailed resolutions except for my OC, just to see if one of them is the culprit. Turns out it still suffers the bug regardless of what I put in CRU. If I touch anything in the slightest, even if I don't overclock anything, it will "activate" the bug.

Maybe CRU is missing an important Extension block that it's not adding by default?

[ToastyX]

(11-14-2020 09:40 PM)AchillesBoi Wrote:  I am using DisplayPort, and even though it loses connection when I turn the monitor off the resolution stays the same if I use default settings. The moment I use CRU the resolution will go all the way down when I turn the monitor off, so I am absolutely sure CRU is doing something here.

I have not tried with HDMI, but I hear DisplayPort is much better so I intend to use that. I have tried deleting all data from CRU: Established resolutions, Standard resolutions, Extension blocks, and all Detailed resolutions except for my OC, just to see if one of them is the culprit. Turns out it still suffers the bug regardless of what I put in CRU. If I touch anything in the slightest, even if I don't overclock anything, it will "activate" the bug.

Maybe CRU is missing an important Extension block that it's not adding by default?

The dimming is a driver bug for sure. Running restart64.exe or pressing Win+Shift+Ctrl+B proves this. I think the bug is related to higher color depths with FreeSync. Can you export a file after running reset-all.exe and restarting so I can take a look?

The windows resizing is a Windows+DisplayPort limitation. When the monitor is turned off with DisplayPort, it disconnects, so Windows moves all the windows to a virtual monitor. I don't know how it decides what resolution to use for the virtual monitor, but it's not something CRU can control. This is a common problem even for people not using CRU. I've seen people post various solutions, but they don't seem to work for all cases. Here's one example: https://answers.microsoft.com/en-us/wind...157334bb2f

CRU includes all extension blocks even if it doesn't know what it is. Unsupported extension blocks are listed as "Other extension block (##)". If CRU can't read an extension block, it will be listed as "Default extension block". CEA-861 and DisplayID are the only ones commonly used, and CRU supports both. CRU also preserves data blocks that haven't been edited.