Custom Resolution Utility (CRU)

[kurtdh]

(08-07-2024 01:56 PM)ToastyX Wrote:  

(08-07-2024 04:36 AM)kurtdh Wrote:  Ok, I plugged in HDMI 2.1 to the FO32U2P. I set the monitor to 12 bit 240hz 4k. I opened up CRU. I navigated to FO32U2P (active). I clicked import, selected FO32U2P-no-DSC.dat. I clicked OK to exit the program. I clicked restart64. I then ran edid-test followed by edid-dump. Files are attached. Please let me know what your findings are.

Did it have any effect? I'm finding that Windows recognizes the EDID override is there, but NVIDIA's driver seems to ignore it.

(08-07-2024 04:36 AM)kurtdh Wrote:  Secondly: I've been speaking with one of the admins of blurbusters. He owns a XG27AQDMG 240hz 1440p oled monitor. He claims the override in CRU works just fine for him at 1440p 240Hz 10-bit on DisplayPort 1.4. This means he's using DSC, but CRU works just fine for him (that's what he says.) I thought CRU didn't work with DSC, so why is it working for him?

I looked more into it and NVIDIA says this: "NVIDIA DSR, NVIDIA DLDSR and NVIDIA Image Scaling are supported when DSC mode is enabled, if the pixel rate needed to drive the display mode does not exceed the GPU's single head limit. If GPU uses two or more internal heads to drive the display, NVIDIA DSR, NVIDIA DLDSR and NVIDIA Image Scaling are not supported."

That doesn't explain why they need to disable EDID overrides, but it seems tied to this. They don't say what the single head limit is, so I don't know the exact logic that NVIDIA is using to disable EDID overrides and DSR/DLDSR. All I know is everyone with this problem has a monitor with DSC, but apparently it has more to do with the bandwidth required for the highest resolution and refresh rate. Regardless of the cause, the limitation is definitely on NVIDIA's end and not the monitor or CRU.

Did it have any affect on what exactly? After I imported FO32U2P-no-DSC.dat and then used restart64, it didn't change any of my settings. My monitor remained at 240hz 4k 12 bit, and games ran normally. After that, I tried going into CRU and editing the 4k 240hz resolution located in "DisplayID 1.3: 1 data block" in Extension blocks. I changed it to 200hz and used restart64, and it didn't change my monitors resolution to 200hz, so I still can't use CRU, if that's what you're asking.

[ToastyX]

(08-07-2024 05:12 PM)kurtdh Wrote:  Did it have any affect on what exactly? After I imported FO32U2P-no-DSC.dat and then used restart64, it didn't change any of my settings. My monitor remained at 240hz 4k 12 bit, and games ran normally. After that, I tried going into CRU and editing the 4k 240hz resolution located in "DisplayID 1.3: 1 data block" in Extension blocks. I changed it to 200hz and used restart64, and it didn't change my monitors resolution to 200hz, so I still can't use CRU, if that's what you're asking.

That's what I wanted to know. Thanks.

[jeffeh12133]

hey Toasty, i have another useless question lol

I want to add a vesa DMT timing for 1920x1080 @ 60hz, but it seems like vesa DMT is only used for 4:3/5:4 resolutions like 1366x768 (or other weird PC resolutions), how do i go about specifically adding a vesa DMT timing for 1920x1080 @ 60hz?

[ToastyX]

(08-08-2024 08:38 AM)jeffeh12133 Wrote:  hey Toasty, i have another useless question lol

I want to add a vesa DMT timing for 1920x1080 @ 60hz, but it seems like vesa DMT is only used for 4:3/5:4 resolutions like 1366x768 (or other weird PC resolutions), how do i go about specifically adding a vesa DMT timing for 1920x1080 @ 60hz?

VESA DMT timing for 1920x1080 @ 60 Hz is the same as CTA, so "Automatic PC" and "Automatic HDTV" both do that already.

[Kas_37]

Hello!
I have an issue with DLDSR is missing on my tv - Samsung S95C, probably because it uses DSC.
Changes made by CRU does not any affect, driver just ignores them. So is it really no way to workaround/fix this behavior? How to force DSR to work? Any hope?

[ToastyX]

(08-09-2024 04:38 PM)Kas_37 Wrote:  Hello!
I have an issue with DLDSR is missing on my tv - Samsung S95C, probably because it uses DSC.
Changes made by CRU does not any affect, driver just ignores them. So is it really no way to workaround/fix this behavior? How to force DSR to work? Any hope?

You should bug NVIDIA about that. They're the only ones that can fix it.

[Kas_37]

(08-11-2024 03:28 AM)ToastyX Wrote:  

(08-09-2024 04:38 PM)Kas_37 Wrote:  Hello!
I have an issue with DLDSR is missing on my tv - Samsung S95C, probably because it uses DSC.
Changes made by CRU does not any affect, driver just ignores them. So is it really no way to workaround/fix this behavior? How to force DSR to work? Any hope?

You should bug NVIDIA about that. They're the only ones that can fix it.

I tried. There is no much hope nvidia will fix it. We need a hacker-hero ?

[ArtMov]

there is a problem, on dp my bootlogo is stretched like 4:3, on hdmi it is displayed correctly. Toasty, please tell me what can be done? There is no problem on the other monitor...

[ToastyX]

(08-11-2024 11:07 AM)ArtMov Wrote:  there is a problem, on dp my bootlogo is stretched like 4:3, on hdmi it is displayed correctly. Toasty, please tell me what can be done? There is no problem on the other monitor...

If the boot resolution is in the EDID, then the resolution should be sent to the display, and it's up to the display to control scaling. If the boot resolution is not in the EDID, then the GPU will scale the resolution to a higher resolution, and there is no way to control GPU scaling during the boot process. The resolution used for scaling may vary depending on the GPU.

[Jen]

Hello, so Im using an all in one desktop with a gtx 1650 and uhd630, it has no mux switch and all the video ports are connected to the Intel gpu, and I was wondering if integer scaling would be usable on an external monitor. I heard that the display must be connected directly to the nvidia gpu for this option to appear in NVCP, and some other sources claim that it would work with hybrid graphics perhaps only with an external monitor.

Also in case anyone is wondering the cpu is a 10th gen comet lake which unfortunately does not support retro scaling I think it was called.