Custom Resolution Utility (CRU)

[dotcomma]

(11-05-2024 03:53 PM)ToastyX Wrote:  

(11-04-2024 01:51 PM)dotcomma Wrote:  Hello,
I'm trying to set custom max refresh rate on my monitor to be lower than native, but it does not accept it and shows that display resolution is not supported, any idea/tip what can I try please?

My monitor is Samsung OLED G8 with native resolution 3440x1440 at max refresh rate 175 Hz, VRR range is 48-175 (Gsync compatible).
Other than 175Hz, monitor also natively supports 60hz, 100hz and 120Hz resolutions.
I have Nvidia 4080 GPU and using DP connection with DSC, EDID override is accepted and luckily works for me on current Nvidia drivers.

What I tried is to edit Detailed Resolution in DP extension block and change the original 175Hz resolution to 150Hz, but keep the original pixel clock. Unfortunately it does not work, is it possible that VRR monitor is locked to some fixed Max refresh rates? If I try 100 or 120 Hz then it works, but only these. I would expect that if its VRR range is 48-175 it would accept native resolution with any refresh rate withing that range, especially if pixel clock is the same.

The reason for doing this is VRR flicker mitigation where fps limiters don't work.

What happens with normal timings, not with the same pixel clock? What about 144 Hz?

Nope, it does not work even with normal timings or 144Hz.

[vol.2]

Quick question. When you wrote about the Alternative Method for Intel GPUs, does the .exe file you export and run effect the monitor itself, or just the PC-side EDID information?

"If you have an older Intel GPU, use the "Export..." button and choose "EXE file" for the file type to export a self-contained EDID override installer. Then run the .exe file and choose "Install EDID" to install the EDID override on all matching displays."

Basically, I'm asking if you meant "for all matching displays," or you actually meant "on all matching displays."

I'm sure this is obvious to most people, but perhaps I don't fully understand how the software works yet. AFAIK, I haven't ever overwritten the EDID information on the monitor itself before.

TIA

[ToastyX]

(11-07-2024 02:34 PM)vol.2 Wrote:  Quick question. When you wrote about the Alternative Method for Intel GPUs, does the .exe file you export and run effect the monitor itself, or just the PC-side EDID information?

"If you have an older Intel GPU, use the "Export..." button and choose "EXE file" for the file type to export a self-contained EDID override installer. Then run the .exe file and choose "Install EDID" to install the EDID override on all matching displays."

Basically, I'm asking if you meant "for all matching displays," or you actually meant "on all matching displays."

I'm sure this is obvious to most people, but perhaps I don't fully understand how the software works yet. AFAIK, I haven't ever overwritten the EDID information on the monitor itself before.

TIA

CRU doesn't do anything that affects the monitor itself. The alternative method is just an Intel-specific method that's also saved in the registry. It's done separately because I don't have a way to match a specific monitor to a particular output using the Intel-specific method, so it just applies the EDID override to all outputs.

[ToastyX]

(11-05-2024 07:27 PM)dotcomma Wrote:  Nope, it does not work even with normal timings or 144Hz.

It's possible the monitor only accepts specific refresh rates. What about with HDMI?

[dotcomma]

(11-07-2024 03:34 PM)ToastyX Wrote:  

(11-05-2024 07:27 PM)dotcomma Wrote:  Nope, it does not work even with normal timings or 144Hz.

It's possible the monitor only accepts specific refresh rates. What about with HDMI?

It has HDMI 2.1, but since it is not possible to raise min VRR range above 48Hz I'm not using it, as I need more than 100Hz min range. Or do you know about some workaround for these HDMI 2.1 limits? Min range cannot go above 48Hz and max range cannot go below 100 if I'm not mistaken.

[ToastyX]

(11-08-2024 06:04 AM)dotcomma Wrote:  It has HDMI 2.1, but since it is not possible to raise min VRR range above 48Hz I'm not using it, as I need more than 100Hz min range. Or do you know about some workaround for these HDMI 2.1 limits? Min range cannot go above 48Hz and max range cannot go below 100 if I'm not mistaken.

That's true for HDMI 2.1 VRR. Maybe it would be better to disable VRR if flicker is a problem.

[Audioboxer]

(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?

   

Sorry for delay getting back to you, if I delete this it just comes back again on a restart.

For now I think I'll just have to use the Windows calibration app and save a profile, as for some reason the behaviour around CRU has changed and using a custom value is being ignored.

Some games like Alan Wake 2 will pull peak brightness from whatever System - Display - Advanced display states.

With some digging online, especially in topics about my monitor, there may be some Nvidia driver issues going on https://www.reddit.com/r/ultrawidemaster...are_button

[funkerwolf]

(10-15-2024 05:48 AM)ToastyX Wrote:  

(10-15-2024 04:49 AM)funkerwolf Wrote:  

(10-14-2024 10:49 PM)ToastyX Wrote:  

(10-11-2024 08:29 PM)funkerwolf Wrote:  

(09-27-2024 12:07 AM)ToastyX Wrote:  Show me what you have. Run this and post the test.txt here: https://www.monitortests.com/EDID-test.zip

That was the old URL. I have an updated version here: https://www.monitortests.com/edid-test.zip

You didn't set the max TMDS clock in the HDMI data block like I said to do. You said it was all in place.

good night, I decided to double-check and unfortunately, 75Hz mode now works only through displayport, but not through hdmi as it should be, I really don't want to use this stillborn standard, as only one problem it causes - banal when you turn off the monitor, it disappears from the system and in the same anydesk just on the output black square Malevich. on the old drivers all ok, what for sabotage of current technologies I do not understand. but it's like the driver ignores the custom modes now.
And the most not clear to me still, if displayport is supposedly a more modern standard, then why it does not have half of the settings that are available through hdmi?        

[Audioboxer]

ToastyX, here is what could be a noobish question for you.

I've just switched from DP to HDMI on my Samsung G8 because I finally picked up a HDMI 2.1 cable. I also wanted to see if I could reproduce the current behaviour I have where editing the monitor max luminance didn't seem to be changing in Windows system settings anymore.

New issue though, if I edit this

   

It actually bricks me getting into Windows. As soon as login screen should appear the monitor just goes black/no signal and begins its 60 second timeout timer.

Spent the last few hours tearing my hair out thinking the HDMI cable was faulty/reinstalling drivers after cleaning in safe mode and finally figured out it was simply any time I edited max luminance it would brick the monitor from displaying anything once Windows loaded (after a restart from editing).

Maybe this is me not understanding editing under HDMI is different from DP, or is it something else???

Cheers

[ToastyX]

(11-10-2024 06:02 PM)Audioboxer Wrote:  It actually bricks me getting into Windows. As soon as login screen should appear the monitor just goes black/no signal and begins its 60 second timeout timer.

Is the computer frozen (does caps lock respond)? Do you have any other monitors connected?