Custom Resolution Utility (CRU)

[ToastyX]

(07-01-2023 03:10 AM)Game-R Wrote:  I'm trying to get my Dell Latitude 7640 laptop with Intel Iris Xe Graphics to, through a Thunderbolt dock, display on a pair of external HP 20" LP2065 monitors at their native 1600x1200 resolution.
For some reason, Windows is only allowing me to go up to either a 1280x1024 or 1280x960 resolution max.

Looking at the output of CRU.exe, it seems to show that the native resolution in the Detailed & Standard resolutions lists and nothing else I can do with it.


I've already ensured the latest Windows, Dell & Intel updates and drivers are installed yet this problem persists. My older Dell XPS 13 9360 with a Intel UHD 620 Graphics is able to run this exact similar setup with all monitors running at their native resolution.

What is going on here? Is there something I can do with CRU to force this resolution into the Windows Settings options?

That sounds like a bandwidth limitation, possibly a driver bug since there should be enough bandwidth for both monitors. You'll have to ask Intel support why their driver is limiting the bandwidth to the dock.

[ToastyX]

(06-27-2023 07:22 AM)LordGurciullo Wrote:  Hey again thanks for always responding. Quick question. Do you know if it is HDMI 2.1a that is giving me a way better color gradient with my LG oled 27inch. People with 40 series video cards with HDMI 2.1a are all saying this and 30 series users with just regular HDMI 2.1 are not. Do you know which part of that is whats giving it that much better image? I'm just curious if you might shed light on it if you know. Thanks for responding about the interview. If you ever change your mind I think it could be fun. You are a legend

I don't think the HDMI version would affect gradients. HDMI 2.1a adds source based tone mapping for HDR, but I'm not sure that has anything to do with it. Maybe the RTX 4000-series GPUs add dithering. YCbCr compresses the 0-255 range into 16-235, so gradients would need dithering to be smooth. 10/12 bpc would make that less noticeable, but the conversion still happens. In theory, full range RGB would give better gradients without dithering if the TV supports full range.

[ToastyX]

(06-27-2023 06:13 AM)Kru1cif3r Wrote:  Im not sure either i used to have the 144hz option too but its missing as well. Isnt it weird that even after adding the detailed resolution from cru the 165 hz option is missing?

CRU can't bypass bandwidth limitations in the hardware or driver. If it worked with Windows 10, then it's a driver bug on Intel's end.

[ToastyX]

(06-26-2023 09:24 PM)BigChungus0001 Wrote:  As I was messing around with my XL2430 timings, I tested the absolute lowest values for the timings so I could squeeze the highest refresh rate, but I encountered some weird behaviors in the way.

First, I copied Falkentyne blanking timings from somewhere else to use in my monitor and my previous W2363D settings for the porchs and sync widths.
Front porch 24 | 3
Sync Width 32 | 5
Back porch 8 | 6
Blanking 58 | 10

I couldn't reduce the blanking timings further, so I think Falkentyne found the lowest possible values, therefore I changed the porchs and sync widths and found stability in these values.
Front porch 18 | 1
Sync Width 32 | 2
Back porch 8 | 6
Blanking 58 | 10

Then, I left the computer to do something else and when I came back, the computer wouldn't wake up, making me force power off. Because of that, I changed the porch value (I don't really know what was the culprit though).

Front porch 18 | 2
Sync Width 32 | 2
Back porch 8 | 6
Blanking 58 | 10

This never happened again, however sometimes the DCC/CI wouldn't work. When this happened, softMCCS reported "Not supported (missing DPtx services)".

1. Could timing parameters influence the wake up of Windows?
2. Is the DCC/CI behavior related to the timing parameters?

Thank you in advance, ToastyX.

If Windows wouldn't wake up with certain timing parameters, that's probably on the GPU's end. Different GPUs have different minimum values that they can handle. The DDC/CI issue could be a monitor limitation with low blanking values.

[syncsftw]

how do i get streched with 360 hrtz?

[Snow_Chain]

Finally, CRU is work with 7900XTX with the latest driver 23.7.1

[Noxyy]

hello guys

first I wanted to congratulate you, it helps many people to have a better monitor performance without having to spend a lot, I'm a big fan of your work

I recently discovered the app and have been using it to create 1600x1024 resolution at 75hz

I use the Automatic PC timing but all the others work perfectly with the exception of the CVT-RB and CVT-RB 2 which cause a few random flickers on the screen every 40 minutes or so.

As my resolution works with all timings but some change the polarity, the KHz or MHz I wonder if there is an "ideal" timing option to use. One that is more secure or stable or that is better for my case. If there is a timing option that is considered the most "correct"

[Mars]

(07-06-2023 12:18 AM)ToastyX Wrote:  You shouldn't have to add 1080p if the display supports it. It should work out of the box, so something is wrong. If the display doesn't have a valid EDID (listed as "Generic Non-PnP Monitor" with no resolutions), CRU will have no effect on Windows 11. If the display uses HDMI, you can use this to get a proper 1080p EDID: https://www.amazon.com/dp/B08RCMFLMK/?tag=mtests-20#ad

Thank you Toasty, you are right. I found the culprit, it was the HDMI to DP adapter I was using, I guess it was just underpowered or something. All working as intended now. Greets!

[Jija25]

Hi, toasty
I have little question, I use msi laptop on rtx 3050ti, 16 ram, i5-11400h, 17,3 inches 1920x1080 native resolution.
And I want create custom resolution like 1440x1080 or 1080x1080.
So, I very scared try create custom resolution, I think I get black screen.
How do u think, can I will get black screen or not?
Sry for my bad English, I live in Russia
Thank you, so much

[Nanaki]

Hello everyone,
I have a problem that I can't figure out, and I'm hoping to find a solution right here, via the CRU utility and your precious advice.

I've got a 1440p screen (2560x1440) and the DSR / DLDSR is giving me resolutions that have nothing to do with 4K, instead of 1.78xDL (3413x1920) and 2.25x DL (3840x2160), for example, the DSR - factors is giving me resolutions of 1.78x DL (5120x2880) and 2.25x DL (5760x3240)?

I have the impression that the nvidia DSR thinks I have a native 4K (3840x2160) screen, whereas I have a native 1440p (screen, so I can't take advantage of the DSR/DLDSR options on my games.

Is this due to a problem with the EDID of the screen, which is incorrectly configured from the factory?

using the CRU software here is what is mentioned in the attached image, do you see anything that does not correspond?

thank you very much!


[/img]