Custom Resolution Utility (CRU)
|
12-15-2024, 12:50 AM
Post: #8651
|
|||
|
|||
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. |
|||
12-16-2024, 12:04 AM
Post: #8652
|
|||
|
|||
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. 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. |
|||
12-16-2024, 05:57 PM
Post: #8653
|
|||
|
|||
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?
|
|||
12-17-2024, 02:49 AM
Post: #8654
|
|||
|
|||
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. |
|||
12-17-2024, 10:12 PM
Post: #8655
|
|||
|
|||
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? |
|||
12-18-2024, 12:41 PM
Post: #8656
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
I'm having major issues with my new Odyssey G95SC (LS49CG950SUXEN).
Whenever I try to set it at more than 60Hz the screen looses its connection to my PC and I get an error screen. I've tried different HDMI 2.1 cables as well as different DP 1.4 cables on all of the ports on my GPU which is an PowerColor Radeon RX 7900XTX Hellhound 24GB. I'm currently testing CRU a bit but have no experience in the application. Could someone assist me and perhaps recommend me settings that I could try to get this sorted? The screenshot shows my current settings for the screen (default). |
|||
12-18-2024, 03:09 PM
Post: #8657
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
I need help I just got a 360hz and i can't get stretched resolution with 360hz it just puts the numbers in red and doesn't let me apply.
|
|||
12-18-2024, 03:37 PM
Post: #8658
|
|||
|
|||
RE: Custom Resolution Utility (CRU) | |||
12-18-2024, 03:37 PM
Post: #8659
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-18-2024 12:41 PM)Kapten Wrote: I'm having major issues with my new Odyssey G95SC (LS49CG950SUXEN).I don't know what you're expecting. You shouldn't use CRU to try to fix problems that shouldn't exist in the first place. What is the error screen you are getting? |
|||
12-18-2024, 03:37 PM
(Last edited: 12-18-2024, 03:46 PM by ToastyX)
Post: #8660
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-17-2024 10:12 PM)gamesager Wrote: 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 haven't seen 64-bit color before. That's new to me. That's something specific to the way Windows handles color internally and not something in the EDID, and NVIDIA's handling seems broken from what you've described. I don't know what conditions 64-bit would appear. This article seems to imply that 64-bit appears with 10 bpc color, and the old 32-bit option is now called 24-bit, so you shouldn't be seeing 32-bit at all: https://nvidia.custhelp.com/app/answers/...1-desktops |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: Fnspydaman, 146 Guest(s)