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.
[
attachment=1449]
Version 26100.2033 of Windows 11 and Nvidia Drivers 565.90.
Anyone can help me to use CRU in my LGC3?
THE PROBLEM: I Cant set 3840x1600 120hz using CRU... just 60hz. Well i can set 120hz in nvidia, but C3 says: Hey You are in 2160p. In other words, the LGC3 does not recognize 3840x1600 @120hz, losing some functions of the TV's ultrawide game mode. In 60hz all things work fine.
I tried to use the "DDU" program but every time I reinstall the nvidia driver the resolution 3840x1600 ALWAYS appears in the resolutions list, so I can't change or create anything in CRU or i dont know how to do it. How do I delete native resolutions in the Nvidia driver?
If I try to edit a native resolution up there in CRU, I set 120hz and the text turns red as if I was doing something wrong. Can anyone help me? thx.
(10-23-2024 01:52 PM)BearBR Wrote: [ -> ]Anyone can help me to use CRU in my LGC3?
THE PROBLEM: I Cant set 3840x1600 120hz using CRU... just 60hz. Well i can set 120hz in nvidia, but C3 says: Hey You are in 2160p. In other words, the LGC3 does not recognize 3840x1600 @120hz, losing some functions of the TV's ultrawide game mode. In 60hz all things work fine.
I tried to use the "DDU" program but every time I reinstall the nvidia driver the resolution 3840x1600 ALWAYS appears in the resolutions list, so I can't change or create anything in CRU or i dont know how to do it. How do I delete native resolutions in the Nvidia driver?
If I try to edit a native resolution up there in CRU, I set 120hz and the text turns red as if I was doing something wrong. Can anyone help me? thx.
You can add 3840x1600 @ 120 Hz in a DisplayID extension block, and you can make 3840x1600 @ 60 Hz the first detailed resolution in the main window to make 3840x1600 the native resolution. If 3840x1600 still appears after using DDU, that means it's in the EDID somewhere.
(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?
(10-15-2024 07:56 AM)Merculian Wrote: [ -> ]hello, help with my problem, if you can (black screen with two monitors)
hello, i partially decided the problem
now i connected two monitors on dp cables, i can turn on, turn off windows (think, firmware helper), all okay, but the BIOS, Animation Boot on the 2nd monitor))
to launch windows right need switch on the power on two monitors (no dp signal, before BIOS)
If i change cables in ports, BIOS will be on the 1st monitor, in Windows the 1st become 2nd, but primary)), the 2nd will be 1st
from nvidia i got nothing
(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.
(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-26-2024 11:43 PM)Monkeyking Wrote: [ -> ] (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'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
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.
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.
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.
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