Post Reply
Custom Resolution Utility (CRU)
12-13-2024, 04:13 AM (Last edited: 12-13-2024, 04:34 AM by DmitriyBlade)
Post: #8651
RE: Custom Resolution Utility (CRU)
Only after i select "3. enable settings for selected display model" in nvidia
i was able to overclock further than my monitor default 165hz to 182hz(if i change it to 166 it starts artifacting)
If i overclock via nvidia custom resolution, my max was 174hz(if i set 175hz ask do i want to save - yes, and it won't save)

i copied settings from 165hz profile, changed only refresh rate to 182hz, seems working fine so far

Question:
1)Does messing around with Front porct/Sync width/Back porch etc gives you any latency decrease?
(or i should only use refresh rate overclock)
2)My Display cable kinda old(from previous monitor), but quite lengthy, if i order a new one, can i improve my 182hz limit further?

ps seems good for 200$ china 3440x1440 34' IPS display


Attached File(s) Thumbnail(s)
       
Find all posts by this user
Quote this message in a reply
12-13-2024, 10:40 AM
Post: #8652
RE: Custom Resolution Utility (CRU)
I'm trying to edit a block that's not editable with cru (greyed out).
The only solution I see is exporting a .bin dump of the edid and editing that block with an external editor.
The problem is that the edid reported by the monitor is not fixed from what I can see.
When I change certain settings on the monitor, the reported edid changes. I dumped the edid between such setting changes and verified that the binary files are different.

Am I correct to assume that if I import an edited edid with cru, it will override everything the monitor reports, essentially nullifying the monitor's ability to switch configurations?
And if so, is there a workaround for changing the specific block only and not affecting anything else?
Find all posts by this user
Quote this message in a reply
12-13-2024, 02:25 PM
Post: #8653
RE: Custom Resolution Utility (CRU)
(12-13-2024 10:40 AM)stej Wrote:  Am I correct to assume that if I import an edited edid with cru, it will override everything the monitor reports, essentially nullifying the monitor's ability to switch configurations?
That would depend on what the graphics driver considers a unique monitor. Usually each EDID would be considered a different monitor, so you can override just one of the EDIDs.
Find all posts by this user
Quote this message in a reply
12-13-2024, 02:25 PM
Post: #8654
RE: Custom Resolution Utility (CRU)
(12-13-2024 04:13 AM)DmitriyBlade Wrote:  Question:
1)Does messing around with Front porct/Sync width/Back porch etc gives you any latency decrease?
(or i should only use refresh rate overclock)
2)My Display cable kinda old(from previous monitor), but quite lengthy, if i order a new one, can i improve my 182hz limit further?
1. Latency would depend on when the frame is rendered. If you're using G-SYNC, you don't need to change the timing parameters because the vertical blanking is automatically adjusted to wait until the next frame is ready.
2. Overclocking is usually limited by the monitor. Cable would only be an issue if you're getting signal dropouts.
Find all posts by this user
Quote this message in a reply
12-13-2024, 10:10 PM
Post: #8655
RE: Custom Resolution Utility (CRU)
(12-13-2024 02:25 PM)ToastyX Wrote:  
(12-13-2024 10:40 AM)stej Wrote:  Am I correct to assume that if I import an edited edid with cru, it will override everything the monitor reports, essentially nullifying the monitor's ability to switch configurations?
That would depend on what the graphics driver considers a unique monitor. Usually each EDID would be considered a different monitor, so you can override just one of the EDIDs.

I don't see additional monitors created in Enum\Display in the registry, so I guess not, it only updates the EDID.
Comparing the contents of the exported .bin files I see that the first part of the file, presumably the EDID base, remains constant. What changes is the extension blocks. Which explains why it's not detecting additional monitors I suppose.

So, from your reply it seems that my assumption was correct. How about workarounds? The block I want changed is always present in every reported configuration and its contents remain static.

Any ideas for overriding a couple bytes and letting everything else pass through?
Find all posts by this user
Quote this message in a reply
12-15-2024, 12:50 AM
Post: #8656
RE: Custom Resolution Utility (CRU)
(12-13-2024 10:10 PM)stej Wrote:  Any ideas for overriding a couple bytes and letting everything else pass through?
There isn't a way to override specific data blocks. I only know an NVIDIA-specific method (OverrideEdidFlags0) that can override specific byte offsets in the EDID, but that would only work if the offsets never change. I don't know any equivalent method for AMD or Intel.

OverrideEdidFlags0 is a binary value that you have to add to this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\#### (usually 0000)

I don't have the details of the OverrideEdidFlags0 registry value, but I typically see:
(## ## ## ##) 00 00 FF FF 04 00 00 00 (offset) (length) (data)

The first four bytes are 0-based offsets 8-11 (9th-12th bytes) in the EDID that identifies the manufacturer and product ID.
Find all posts by this user
Quote this message in a reply
12-16-2024, 12:04 AM
Post: #8657
RE: Custom Resolution Utility (CRU)
(12-15-2024 12:50 AM)ToastyX Wrote:  
(12-13-2024 10:10 PM)stej Wrote:  Any ideas for overriding a couple bytes and letting everything else pass through?
There isn't a way to override specific data blocks. I only know an NVIDIA-specific method (OverrideEdidFlags0) that can override specific byte offsets in the EDID, but that would only work if the offsets never change. I don't know any equivalent method for AMD or Intel.

OverrideEdidFlags0 is a binary value that you have to add to this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\#### (usually 0000)

I don't have the details of the OverrideEdidFlags0 registry value, but I typically see:
(## ## ## ##) 00 00 FF FF 04 00 00 00 (offset) (length) (data)

The first four bytes are 0-based offsets 8-11 (9th-12th bytes) in the EDID that identifies the manufacturer and product ID.

This looked promising. I gave it a go and it worked initially.
Unfortunately though, the data block is not fixed in place.
The offset keeps moving when settings change on the monitor.

I got a feeling there might be additional ways to specify the target block, but without full documentation of this override function it's gonna be a pisstake figuring it out.

Thanks for your help either way. If I find any more info I'll be sure to post it.
Find all posts by this user
Quote this message in a reply
12-16-2024, 05:57 PM
Post: #8658
RE: Custom Resolution Utility (CRU)
I'm trying to limit my Samsung Odyssey G60SD (2560x1440, 360hz) monitor to 240Hz using Custom Resolution Utility (CRU) to avoid enabling DSC. I've turned off the DSC options in HDMI 2.x support, and added DisplayID 1.3/2.0 Detailed Resolutions set at 240hz, but the the 360hz refresh rate is still available as an option so DSC is on. How can I successfully cap my monitor at 240Hz without enabling DSC using CRU?
Find all posts by this user
Quote this message in a reply
12-17-2024, 02:49 AM
Post: #8659
RE: Custom Resolution Utility (CRU)
(12-16-2024 05:57 PM)canopylions Wrote:  I'm trying to limit my Samsung Odyssey G60SD (2560x1440, 360hz) monitor to 240Hz using Custom Resolution Utility (CRU) to avoid enabling DSC. I've turned off the DSC options in HDMI 2.x support, and added DisplayID 1.3/2.0 Detailed Resolutions set at 240hz, but the the 360hz refresh rate is still available as an option so DSC is on. How can I successfully cap my monitor at 240Hz without enabling DSC using CRU?
You didn't say what GPU. If it's an NVIDIA GPU, it's not possible to disable DSC with CRU because the driver ignores EDID overrides in this case.
Find all posts by this user
Quote this message in a reply
12-17-2024, 10:12 PM
Post: #8660
RE: Custom Resolution Utility (CRU)
I have the asus pg27aqdm and they have their actual monitor timings listed in the user manual online and by default nvidia doesnt use them.
I have tried setting in on cru and that works ok, but also tried with nvidias custom resolutions.
When I set it on nvidias, and then switch to gpu scaling and back to displayscaling, itll actually show a duplicate of my resolution in the custom window, but in the "PC" section instead of the custom section and will be listed as a 32 bit instead of 64 bit resolution.
When I select this resolution instead everything looks and feels WAY better. Im not sure how to explain it, but almost like gsync works significantly better, motion looks better and input feels better.

But every time I reset my pc, I have to redo the steps. Is there any way to use CRU to make that resolution permanently set as one of those 32 bit pc profiles? Or would someone know how to create those 32 bit profiles?
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: 65 Guest(s)