Custom Resolution Utility (CRU)

[ToastyX]

(10-26-2020 09:10 AM)slobo2712 Wrote:  Seems that this CPU/GPU cant do 4k60hz via HDMI anyway that might be a issue?

https://ark.intel.com/content/www/us/en/...0-ghz.html

Max resolution means nothing. It's the pixel clock that matters. You would need HDMI 2.0 for 3840x2160 @ 60 Hz without 4:2:0.

[slaindevil]

(10-25-2020 09:03 PM)ToastyX Wrote:  I don't know how it works with NVIDIA, but with AMD, just changing the low end of the FreeSync range should work. I don't think that monitor has issues on the low end of the range though. Try reducing the refresh rate to 140 Hz instead. You'll have to change the both detailed resolution and the range.

Thanks for you reply. I tried it with 140Hz, but this just led to very weird artifacts in the lower quarter of the screen.
I think I will return the monitor and try to get my hands on an IPS / G-Sync unit. But thank you.

[MonopolyMan]

I'm trying to remove all resolutions, with the exception of 2560x1080@120Hz on a fit-Headless (GS). The problem is not running at this resolution (it can run at this resolution out of the box), the problem is that Parsec for some reason resets the resolution to 1920x1080 every time I connect, despite 2560x1080 working just fine once I manually change it. Even with every resolution being removed from the EDID with CRU, Windows (and thus parsec) still detects 1920x1080 as a valid resolution. Are there any extra steps I can take to ensure 2560x1080 is the only resolution?

[ToastyX]

(10-26-2020 10:19 PM)MonopolyMan Wrote:  I'm trying to remove all resolutions, with the exception of 2560x1080@120Hz on a fit-Headless (GS). The problem is not running at this resolution (it can run at this resolution out of the box), the problem is that Parsec for some reason resets the resolution to 1920x1080 every time I connect, despite 2560x1080 working just fine once I manually change it. Even with every resolution being removed from the EDID with CRU, Windows (and thus parsec) still detects 1920x1080 as a valid resolution. Are there any extra steps I can take to ensure 2560x1080 is the only resolution?

The graphics driver automatically adds some common lower resolutions as scaled resolutions. For NVIDIA, search the registry for NV_Modes.

[MonopolyMan]

(10-26-2020 10:37 PM)ToastyX Wrote:  

(10-26-2020 10:19 PM)MonopolyMan Wrote:  I'm trying to remove all resolutions, with the exception of 2560x1080@120Hz on a fit-Headless (GS). The problem is not running at this resolution (it can run at this resolution out of the box), the problem is that Parsec for some reason resets the resolution to 1920x1080 every time I connect, despite 2560x1080 working just fine once I manually change it. Even with every resolution being removed from the EDID with CRU, Windows (and thus parsec) still detects 1920x1080 as a valid resolution. Are there any extra steps I can take to ensure 2560x1080 is the only resolution?

The graphics driver automatically adds some common lower resolutions as scaled resolutions. For NVIDIA, search the registry for NV_Modes.

Thanks! I got rid of the Nv_Modes key under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 and it sucessfully got rid of some of the resolutions, but I'm still seeing some resolutions I don't want. Any idea where these are coming from? I'm trying to do scan the registry for them, but so far I haven't had any luck.



Edit: There's a registry key NV_R&T that might have something to do with it. I'm going to look into this key a bit more, but if I can't find anything else I'll try deleting it and seeing what happens.

Edit2: I decided to just send it so I deleted NV_R&T. Unfortunately that didn't remove the resolutions. For now I have restored NV_R&T

[ToastyX]

(10-26-2020 11:28 PM)MonopolyMan Wrote:  Thanks! I got rid of the Nv_Modes key under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 and it sucessfully got rid of some of the resolutions, but I'm still seeing some resolutions I don't want. Any idea where these are coming from? I'm trying to do scan the registry for them, but so far I haven't had any luck.

Delete the TV resolutions from the extension block. You don't need to define the same resolution in multiple places. If that doesn't work, you might need to create an NV_Modes with just "2560x1080=1;" in it.

[MonopolyMan]

(10-27-2020 12:58 AM)ToastyX Wrote:  

(10-26-2020 11:28 PM)MonopolyMan Wrote:  Thanks! I got rid of the Nv_Modes key under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 and it sucessfully got rid of some of the resolutions, but I'm still seeing some resolutions I don't want. Any idea where these are coming from? I'm trying to do scan the registry for them, but so far I haven't had any luck.

Delete the TV resolutions from the extension block. You don't need to define the same resolution in multiple places. If that doesn't work, you might need to create an NV_Modes with just "2560x1080=1;" in it.

I added the NV_Modes key with "2560x1080=1;" and now most of the resolutions are gone. There are still two left that I don't want: 1768x992 and 1176x664. Seems like there's an overscan setting somewhere.

Edit: Despite the extra resolutions, Parsec now stays at 2560x1080! I'm still curious about these two remaining resolutions and where they come from, but my original goal has been achieved.

Also, for future reference, do you know if AMD has a registry key similar to NV_Modes?

[ToastyX]

(10-27-2020 01:25 AM)MonopolyMan Wrote:  I added the NV_Modes key with "2560x1080=1;" and now most of the resolutions are gone. There are still two left that I don't want: 1768x992 and 1176x664. Seems like there's an overscan setting somewhere.

Edit: Despite the extra resolutions, Parsec now stays at 2560x1080! I'm still curious about these two remaining resolutions and where they come from, but my original goal has been achieved.

Also, for future reference, do you know if AMD has a registry key similar to NV_Modes?

Make sure there are no resolutions in the extension block, including detailed resolutions, or it might create underscanned modes. Other than that, I don't know where it's getting those resolutions.

AMD's list is hard-coded in the driver.

[sgern]

I just got an MSI GF75-10SCXR-003 with a 1920x1080, 144HZ screen. This is a bit unfortunate, as even though it's technically better than the 120HZ it's advertised as having, 144HZ doesn't divide neatly with both 24 (anime, movies) and 30 (live-action TV, games) the way 120HZ does.

I tried to use CRU to create a 1920x1080, 120HZ refresh rate setting, but it doesn't seem to do anything at all. I create the setting, run the reset file, and both Windows display settings and Intel Graphics Command Center still only show 60HZ and 144.028HZ. Intel Graphics Command Center also doesn't seem to have an option for custom resolutions.

Is there some way to fix this so I can get rid of any judder I'd experience at 144HZ?

EDIT: I guess I just needed to restart the laptop. Now the 120HZ display mode is showing up. I have a couple more questions though. Is this "true" 120HZ, or is it doing a bunch of frame skipping or something else screwy? Also, what are the exact values that games run at? I'm pretty sure "24FPS" shows are judder-free at multiples of 23.976 and "30FPS" at multiples of 29.97, but do games run at exact multiples of 30FPS, or is there some decimal stuff there as well? And why does the value seem to always be off ever so slightly from what I type in (119.88HZ vs 119.881HZ, 120HZ vs 120.002HZ)?

[ToastyX]

(10-28-2020 12:40 AM)sgern Wrote:  EDIT: I guess I just needed to restart the laptop. Now the 120HZ display mode is showing up. I have a couple more questions though. Is this "true" 120HZ, or is it doing a bunch of frame skipping or something else screwy? Also, what are the exact values that games run at? I'm pretty sure "24FPS" shows are judder-free at multiples of 23.976 and "30FPS" at multiples of 29.97, but do games run at exact multiples of 30FPS, or is there some decimal stuff there as well?

Laptops usually don't skip frames. You can verify using this test with a camera: https://testufo.com/frameskipping

Games with uncapped frame rates are not bound to specific rates and run as fast as the system can handle. Games with frame rate caps run up to whatever rate the game is designed for, often 60 FPS. The only way to have perfect smoothness in games is to synchronize with the monitor using VSync or FreeSync/G-SYNC.