Custom Resolution Utility (CRU)

[ToastyX]

(Today 12:01 AM)jeffeh12133 Wrote:  Found a weird issue. When using CRU to add CVT-RB 1920x1080 143.981hz, upon reboot, my windows regedit shows VideoStandard as "255"

When deleting this CRU res and adding the same detailed res with nvidia custom resolution (CVT-RB 1920x1080 143.981hz in nvidia CP instead), i go into regedit:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Con​figuration\ACR0742TH5AA0038521_34_07E4_11^CC793B8FD95ECAE1C053C2FC37090D8E\00\00​

and it shows VideoStandard 3.

i looked up what VideoStandard means. https://learn.microsoft.com/en-us/window...l_standard

3 = D3DKMDT_VSS_VESA_CVT
255 = D3DKMDT_VSS_OTHER

to replicate, you might have to change your res to something lower, then back to the cvt-rb one in order to see the VideoStandard change between 255 and 3. CRU CVT-RB = VideoStandard 255, nvidia CVT-RGB = VideoStandard 3 (seems proper)

so despite adding a 143.981hz CVT-RB resolution in CRU, the regedit in windows always only shows 255 as the VideoStandard whereas adding CVT-RB via nvidia CP as a custom resolution shows the proper VideoStandard being 3 which means D3DKMDT_VSS_VESA_CVT according to above microsoft link.

That shouldn't matter. I wouldn't expect VideoStandard to be accurate. Detailed resolutions don't have a way to specify what standard it is. The timing options in CRU are just calculators to help fill in the values. The driver probably reports all detailed resolutions as D3DKMDT_VSS_OTHER because otherwise it would have to calculate and compare all the timing standards for every resolution, which would be pointless work. NVIDIA control panel custom resolutions are a vendor-specific implementation, so if you choose CVT-RB, it knows what you chose.

[jeffeh12133]

(Today 01:18 AM)ToastyX Wrote:  

(Today 12:01 AM)jeffeh12133 Wrote:  Found a weird issue. When using CRU to add CVT-RB 1920x1080 143.981hz, upon reboot, my windows regedit shows VideoStandard as "255"

When deleting this CRU res and adding the same detailed res with nvidia custom resolution (CVT-RB 1920x1080 143.981hz in nvidia CP instead), i go into regedit:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Con​figuration\ACR0742TH5AA0038521_34_07E4_11^CC793B8FD95ECAE1C053C2FC37090D8E\00\00​

and it shows VideoStandard 3.

i looked up what VideoStandard means. https://learn.microsoft.com/en-us/window...l_standard

3 = D3DKMDT_VSS_VESA_CVT
255 = D3DKMDT_VSS_OTHER

to replicate, you might have to change your res to something lower, then back to the cvt-rb one in order to see the VideoStandard change between 255 and 3. CRU CVT-RB = VideoStandard 255, nvidia CVT-RGB = VideoStandard 3 (seems proper)

so despite adding a 143.981hz CVT-RB resolution in CRU, the regedit in windows always only shows 255 as the VideoStandard whereas adding CVT-RB via nvidia CP as a custom resolution shows the proper VideoStandard being 3 which means D3DKMDT_VSS_VESA_CVT according to above microsoft link.

That shouldn't matter. I wouldn't expect VideoStandard to be accurate. Detailed resolutions don't have a way to specify what standard it is. The timing options in CRU are just calculators to help fill in the values. The driver probably reports all detailed resolutions as D3DKMDT_VSS_OTHER because otherwise it would have to calculate and compare all the timing standards for every resolution, which would be pointless work. NVIDIA control panel custom resolutions are a vendor-specific implementation, so if you choose CVT-RB, it knows what you chose.

gotcha

i have displayport connected to an EDID 1.4 monitor. by default, the base EDID lists 1920x1080 60hz cta-861 timing as the preferred/native timing. i currently have it edited to use 1920x1080 143.981hz as the first base EDID detailed timing. is this ok to do or should i leave it at the cta-861 1920x1080 60hz and just include the 144hz as a displayID extension block

also about displayID extension blocks, my monitor probably doesnt support it but displayID 1.3 extension block works properly and identified any detailed res i create in there. is it ok to use displayID extension block despite this or does the monitor specifically have to support it for it to work properly? and do you recommend putting the cvt-rb 1920x1080 144hz timing in displayID or under base EDID first detailed timing?

i notice differences between both