Custom Resolution Utility (CRU)
|
10-26-2024, 11:07 AM
Post: #8561
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-24-2024 05:24 PM)ToastyX Wrote:(10-22-2024 12:02 PM)Audioboxer Wrote: Hi guys just signing up to say I've noticed Windows now reporting 400 instead of 1000 like it was previously. Been using CRU since I got my G8 and it's been fine changing peak brightness, but doesn't seem to be working now.Well either NVIDIA's driver is ignoring the change or there's something else overriding it. What happens if you delete the HDR10+ data block? Have you tried the Windows HDR Calibration app? Windows calibration app responds fine with the scaling on white going up to 993 nits before image completely disappears. I don't tend to save a profile with it though, just check nothing is being cut off incorrectly. I know if you save a profile it can make peak brightness display correctly under Advance display, but CRU always skipped that step being needed. I'll try deleting the HDR10+ data block. |
|||
10-26-2024, 11:43 PM
Post: #8562
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-29-2023 05:32 AM)ToastyX Wrote:(11-29-2023 02:50 AM)b0utamine Wrote: I will go ahead and report it. How would you suggest I word it so it's clear and actionable on their end?There are two issues. The first is the EDID reported to Windows is modified compared to the EDID reported by the display, which is why CRU can't match the EDID to get the extension blocks. The second is the driver seems to ignore EDID overrides for displays affected by the first issue even if the override is complete with all extension blocks. These issues only happen with certain displays on RTX 3000/4000-series GPUs. I'd like to forward this to nvidia but the engineers seem more favorable to developers concerns directly. Have you thought creating a thread on the nvidia developer forum ? they might listen to you since you master the subject, seems like they redirect every consumer to the consumer forum where it's a bit deafened. damn one connect box |
|||
10-27-2024, 12:19 AM
Post: #8563
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-26-2024 11:43 PM)Monkeyking Wrote:They actually fixed the first issue, and the second issue turns out to be the driver disabling EDID overrides if the pixel rate requires more than one head. They also disable custom resolutions and DSR/DLDSR in that case, but I don't know why EDID overrides need to be disabled. That mainly affects monitors with display stream compression (DSC). The problem is I don't have the hardware to reproduce these issues, so I can't provide any information they might need, and without having the hardware myself, it took me a long time to figure out the issue was related to the pixel rate.(11-29-2023 05:32 AM)ToastyX Wrote: There are two issues. The first is the EDID reported to Windows is modified compared to the EDID reported by the display, which is why CRU can't match the EDID to get the extension blocks. The second is the driver seems to ignore EDID overrides for displays affected by the first issue even if the override is complete with all extension blocks. These issues only happen with certain displays on RTX 3000/4000-series GPUs. I'm gathering a list of bugs to report myself soon, but I don't know how to reproduce some of them, and I don't know which ones are fixed. It's very hard to get anyone to fix problems if they aren't easy to reproduce. There's a particularly nasty NVIDIA driver bug that causes Windows to hang on boot, but I don't know what conditions trigger it. I only recently figured out it's more likely to happen with multiple monitors connected, but it doesn't always happen even on systems that have had it happen before, so there's some other piece of the puzzle missing. There's another issue where the control panel is sometimes missing the display section, and I don't know what conditions trigger that. That's why it'd be more helpful for people having the issues to report them. |
|||
10-27-2024, 04:02 PM
(Last edited: 11-18-2024, 03:52 AM by ikonomov)
Post: #8564
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Additionally, I've noticed that if the pixel rate requires more than one head the Integer scaling option in NVCP becomes unavailable.
I've been using my 4K monitor configured to use 158Hz with the settings reported here with DSC disabled and HDMI 2.1 connection. I've found no issues except every once in a while (could be as rare as 2 or 3 times a day) I would get a blank screen, basically the same behavior that happens when the cable isn't capable of supporting the bandwidth. I was at first using Zeskit X-Tech 6.5' then I switched to Zeskit Maya 6.5' with the assumption that the second cable might provide a cleaner signal given its advertised construction and popularity. The problem persisted, so I tried just resetting all EDID overrides and using the monitor's default 144Hz max refresh rate when DSC is disabled. I think at 144Hz the frequency at which it happens improved, but the issue was still not gone. This problem has been plaguing me for about a month now and while trying to find some logic for this black screen behavior and specifically how it happens, it got me thinking that it seems to happen with some pattern, either when I'm not doing anything like reading something on the screen, or immediately after an idle state when I move the mouse. I decided to try switching Windows' power plan to High Performance, which disables "PCI Express Link State Power Management". It'll take a while to know for sure, but so far so good. It's interesting that with DSC enabled it doesn't seem to happen, maybe having the GPU constantly encoding the signal prevents the PCIE power management from entering the idle state. Edit: Unfortunately disabling PCI Express Link State Power Management did not solve the blank screen problem. Unless it has something to do with the HDMI 2.1 cable that I use, it seems that the only solution is to use the DP 1.4 port with DSC. I tried both Zeskit Maya 6.5' and Zeskit X-Tech 6.5', both of which are HDMI 2.1 ultra high speed certified and tested with fairly good reputation. |
|||
10-27-2024, 07:47 PM
(Last edited: 10-27-2024, 07:48 PM by mahanddeem)
Post: #8565
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Hi
How can I remove the 3840x2160 resolution from my Aorus 1440p OLED monitor using cru? Native resolution is 2560x1440 but has 4k mode for consoles (with HDMI). It's listed in PC section in NVCP. Thanks |
|||
10-28-2024, 02:51 AM
Post: #8566
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-27-2024 07:47 PM)mahanddeem Wrote: HiUse this guide: https://www.monitortests.com/blog/guide-...4096x2160/ |
|||
10-28-2024, 02:59 PM
Post: #8567
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-28-2024 02:51 AM)ToastyX Wrote:(10-27-2024 07:47 PM)mahanddeem Wrote: HiUse this guide: https://www.monitortests.com/blog/guide-...4096x2160/ Thanks. I will give it a good read |
|||
10-28-2024, 06:09 PM
(Last edited: 10-28-2024, 06:11 PM by ffd)
Post: #8568
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Can you help?
I have a: Monitor: AOC Q27G2E 27" 2K Windows 11 24H2 (Atlas applied) Graphic card: Nvidia GTX 550 TI MSI with Mini HDMI 1. The first problem is that I can set a maximum of 2560x1440 96HZ, above 96HZ the picture starts to chop and after about 100 or more it becomes black. What is the limitation? Is this graphic because it uses a MINI Hdmi port or is the cable old-bad? The monitor doesn't support DVI input, so I can't test via DVI if the same thing happens. The monitor has HDMI 2x and 1 Display Port, but the graphics card does not have a display port, so the only option for me is a Mini HDMI to standard HDMI cable. 2. Another problem is that through the CRU I can only set 1920x1080 resolution and 96 hz and it will be visible there Display Settings/Advanced Display/Display Adaptor Propertires/List All Modes and the maximum resolution that I can set through the CRU and it will be visible is 1920x1080 and 96hz and it works. In the same way, I create 2k resolution, 60hz or 96hz and do everything the same, but it does not appear. I changed the drivers but to no avail. Used Quadro drivers first and then regular 500 series 391.xx drivers, but they don't help with 2K. But through Nvidia Control Panel I can make 2k and 96hz and it works. What's the problem? I sent several different tutorials for CRU and read here by topic, I adjusted it in every possible way, deleted all the resolutions that CRU lists in all three fields and made one, but again they won't display the 2K resolution I make, I tried every possible timing but it didn't help. This 2560x1440 95hz created from Nvidia Control Panel.. I create everything, it is there in the CRU, but windows will not load it anywhere, and the Nvidia Control Panel does not load it either. |
|||
10-28-2024, 08:28 PM
Post: #8569
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-28-2024 08:09 PM)Lemonade Wrote: Hello everyone,You can't add 2880x1800 as a standard resolution. It has to be a detailed resolution. Try using the vertical total calculator to make the same pixel clock as 120 Hz: https://www.monitortests.com/blog/vertic...alculator/ |
|||
10-28-2024, 08:28 PM
Post: #8570
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-28-2024 06:09 PM)ffd Wrote: Can you help?Your GPU is too old. It doesn't support HDMI 2.0. You're lucky it can even do 2560x1440 @ 96 Hz. That's far beyond what HDMI could do at the time. HDMI 1.3/1.4 allows up to 340 MHz pixel clock, but many cards at the time had lower limits. NVIDIA's driver allows overclocking the HDMI port through the NVIDIA control panel but not through EDID overrides that CRU uses, so whatever limit you're hitting with CRU is the pixel clock limit of the card. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 96 Guest(s)