Custom Resolution Utility (CRU)
|
01-24-2024, 02:36 AM
Post: #7931
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(01-19-2024 12:39 PM)ArtMov Wrote: Question to dev, perhaps you are aware of whether there are ways to enable microsoft caso (software mux switch) in intel graphics 6-10 gen? This is purely a software lock, they are forcing us to switch to new hardware. I saw on some forum that someone added keys to the registry in the graphics path (0000) and caso seemed to work, I lost this resource. Toasty please pay attention, I’ve been digging into this question for half a year now. This is a huge boost for laptops, and you, as a display guru, probably know something...If the value is in the graphics driver key, then it's probably something specific to Intel's driver, and I'm not familiar with what registry values they use to control this. |
|||
01-24-2024, 06:52 AM
Post: #7932
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(01-24-2024 02:36 AM)ToastyX Wrote:(01-23-2024 01:44 PM)DragonRulerX Wrote: HiDSC should only be active for resolutions that require it, so if you set the other two monitors to 3840x2160 @ 60 Hz, then DSC shouldn't be active on those monitors. I did try that before posting here, but it didn't work. The GP27U is very strange when you look at its history and current feature set. It really doesn't like to play nice with multiple monitors. Unfortunately, I haven't been able to contact the vendor so any specific questions I have such as the one I'm posing here can only be answered by what is in the manual - which isn't very comprehensive. A really interesting and strange behavior is how the inactive monitor loses its settings randomly sometimes too. I can make edits in the NVIDIA Control Panel to a given monitor, change the set of 2 currently active monitors to a different pair and make changes there, followed by returning to the original pair and find my settings reverted back to factory on the monitor that was deactivated during the transition over to the other set of 2 monitors. Ex: (A->A*, B, !C), (!A, B, C->C*), (A, B, !C) instead of (A*, B, !C) The experience with the monitor has actually been very frustrating regarding configuration. I'll keep it for awhile longer while I wait for a new purchase of other undecided brand monitors to arrive so I still want to try to find a fix to this to post somewhere for posterity, but I have actually found monitors that explicitly declare in their manuals DisplayPort "version" / DSC On/Off controls so I'm intending to purchase a set of them after I get the response from one last vendor who didn't list these controls in their manual to make my final decision. |
|||
01-24-2024, 11:00 AM
Post: #7933
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(01-24-2024 06:52 AM)DragonRulerX Wrote: I did try that before posting here, but it didn't work. The GP27U is very strange when you look at its history and current feature set. It really doesn't like to play nice with multiple monitors. Unfortunately, I haven't been able to contact the vendor so any specific questions I have such as the one I'm posing here can only be answered by what is in the manual - which isn't very comprehensive.Those are NVIDIA driver issues. The monitor can't control what happens when other monitors are present. NVIDIA also has issues with EDID overrides on certain monitors with their newer GPUs. If CRU can read the extension block list (doesn't say "Default extension block"), then you can try deleting all the higher refresh rates to prevent DSC from activating. If not, you can try using DisplayPort to HDMI 2.0 active adapters for the two monitors, since those don't support DSC and will be limited to 3840x2160 @ 60 Hz. |
|||
01-27-2024, 11:09 PM
(Last edited: 01-27-2024, 11:11 PM by someone)
Post: #7934
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(01-23-2024 05:51 PM)alessandro Wrote: Hi dev! Amazing that you're still supporting this! You can only increase the maximum height to 864 but you need to create/modify a registry value called Display1_DownScalingSupported in the gpu's path (HKLM/System/CurrentControlSet/Control/Class/{4d36e968-e325-11ce-bfc1-08002be10318}/0000). You have to set it to 1 and restart the graphics driver. Because you can't use CRU for downscaling, 1366x864 is the maximum possible resolution you can use. According to Reddit, you can only decrease the titlebar size via the registry. |
|||
01-28-2024, 05:45 PM
Post: #7935
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
I'm trying to remove the dolby vision block on the alienware aw3225qf using cru. Driver version is 551.23. I'm able to delete it but dolby vision still activates on the monitor. Any idea why? In driver version 546.17, the dolby vision block is not there and it does not activate on the monitor, so shouldn't this method of deleting the block with cru produce the same results?
|
|||
01-30-2024, 04:58 PM
Post: #7936
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Hello, I have set my C9 to 790 nits via CRU/Windows HDR calibration tool and everything works fine. Though now I just got an 8K AVR and going through that instead of directly to the C9 and I cannot seem to calibrate the AVR's nits via CRU. The default values are stuck on 1499 nits and everything is brighter in games but also heavily crushing blacks. And when I go through the Windows HDR calibration tool, I only hit up to 530 nits which is well below what the C9 can do. Any suggestions/ideas? I have tried setting the CRU values for the AVR but nothing changes - also did a restart afterwards.
Side question, I have only used one value of 127 for both Max Luminance and Max Frame-Avg, is that not correct? Should I be using the VESA test app to find the correct Max Frame-Avg? Thanks, first post! |
|||
01-31-2024, 06:45 PM
Post: #7937
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Anybody? ^^
|
|||
02-02-2024, 03:05 PM
Post: #7938
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
So what would be the industry recognized term for what CRU calls "standard resolutions" in the EDID? I'm trying to use the right term for when I submit a bug report to AMD that mine aren't working correctly
Basically, my 6800 XT is having an issue where it uses reduced timings for "standard resolutions", which looks wrong on my CRT. In the past, on other GPUs, standard resolutions would utilize GTF or CVT standard, as far as I could tell, because they looked correct. I actually had this issue on my 5700xt but AMD fixed it at some point. But I guess the problem remained on the 6000 series. |
|||
02-03-2024, 02:13 PM
Post: #7939
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(02-02-2024 03:05 PM)CRTFTW Wrote: So what would be the industry recognized term for what CRU calls "standard resolutions" in the EDID? I'm trying to use the right term for when I submit a bug report to AMD that mine aren't working correctlyIt's the standard timing block in the EDID. I don't think AMD is expecting anyone to use CRT monitors since they don't have analog outputs anymore. The new CVT standard removed CRT timings completely. |
|||
02-03-2024, 02:13 PM
Post: #7940
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(01-30-2024 04:58 PM)SyphonFilter Wrote: Hello, I have set my C9 to 790 nits via CRU/Windows HDR calibration tool and everything works fine. Though now I just got an 8K AVR and going through that instead of directly to the C9 and I cannot seem to calibrate the AVR's nits via CRU. The default values are stuck on 1499 nits and everything is brighter in games but also heavily crushing blacks. And when I go through the Windows HDR calibration tool, I only hit up to 530 nits which is well below what the C9 can do. Any suggestions/ideas? I have tried setting the CRU values for the AVR but nothing changes - also did a restart afterwards.What GPU? What driver version? If NVIDIA, make sure there are at least 2 bytes left for data blocks in the CTA-861 extension block. Max luminance and max frame average luminance can be the same. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 143 Guest(s)