Custom Resolution Utility (CRU)

[ToastyX]

(01-04-2025 01:15 AM)willianwojcik Wrote:  It seems to be the same problem, or am I mistaken?

No, he has no problem using 240 Hz without DSR, and his issue happens with older drivers as well. In your case, I have no idea why 120 Hz isn't available even after adding it manually. The only thing that comes to mind is maybe they did some sort of workaround for your TV because of the 2560x1080 issue, so CRU is not having the proper effect. Does anything change if you edit the device ID to anything else using the "Edit..." button at the top?

[ToastyX]

(01-04-2025 12:51 AM)Case Wrote:  Maybe you're running into DSC issues? A 1440p 240Hz monitor at 8 bit color depth may or may not require DSC at that resolution and refresh rate. And in most cases (though, weirdly enough, apparently not in all of them), nVidia disables several features in their drivers if the monitor is using DSC, DLDSR being one of them.

I have a 4k monitor that is using DSC at all times in game mode regardless of refresh rate, so no DLDSR for me, ever.

2560x1440 @ 240 Hz doesn't require DSC at 8 bpc, and it also doesn't exceed the pixel rate that would cause DSR to be disabled. If it were the DSC issue, then CRU would have no effect either.

[ToastyX]

(01-02-2025 06:51 PM)ozzuneoj Wrote:  Just confirmed, it happens with DSR and DLDSR on my system. I forgot all about that actually... I think I had the same issue with standard DSR when I was running a GTX 970.

Does your monitor define any resolutions higher than the native resolution by default such as 3840x2160? DSR might be using the highest resolution instead of the native resolution. In that case, deleting the higher resolutions should solve the problem.

[wheo9x]

(01-04-2025 05:25 AM)ToastyX Wrote:  

(01-04-2025 01:23 AM)wheo9x Wrote:  The method to get a custom stretch res on 240hz when you go to detailed resolutions at the bottom you can only use the options there? the highest it shows is 240hz not 360hz when im using a 360hz monitor, there is no 360hz option and when i try to edit it at the bottom the number goes to red and i can't apply it.

The first post explains why the number turns red. 1920x1080 @ 360 Hz should already be there in a DisplayID extension block.

Ah yes i see that now, but then how do you paste it into the top box under detailed resolutions? when i paste it into the detailed resolutions at the top like id normally do its in red, i tried deleting the top detailed resolutions and the middle box and just keeping the displayid and changing it to my specific resolution and i thought it worked at first but it changed it to gpu scaling and my fortnite game looked like this..

Is there any chance you could list exactly how you do it from start to finish please? or some type of youtube video or something?

[ToastyX]

(01-04-2025 09:56 PM)wheo9x Wrote:  Ah yes i see that now, but then how do you paste it into the top box under detailed resolutions? when i paste it into the detailed resolutions at the top like id normally do its in red, i tried deleting the top detailed resolutions and the middle box and just keeping the displayid and changing it to my specific resolution and i thought it worked at first but it changed it to gpu scaling and my fortnite game looked like this..

Is there any chance you could list exactly how you do it from start to finish please? or some type of youtube video or something?

How to do what exactly? I don't understand why every time someone says "stretched resolution" they are always so vague. I can't give exact instructions if you won't tell me exactly what you're trying to do. Why do you need to paste it into the top box? What exactly are you trying to do?

Saying "stretched resolution" doesn't tell me anything. I already told you, CRU doesn't deal with scaling. You set the resolution you want, and then the monitor scales the resolution if you're using display scaling, or the GPU scales it to the native resolution if you're using GPU scaling. If that doesn't answer your question, then you're not telling me the actual problem.

All CRU can do is control which resolutions are sent to the display and which resolution Windows considers to be the native resolution. Any resolution listed in CRU should be sent to the display if you're using display scaling. The first detailed resolution is considered the native resolution. If you want to change what Windows considers to be the native resolution, the refresh rate part doesn't matter, so if you can't set it to 360 Hz, then just set it to 60 Hz, and add 360 Hz separately in a DisplayID extension block.

[juanme555]

Toasty, do you think it could be possible for graphics cards manufacturers to bypass the 25mhz minimum pixel clock requirement? theoretically speaking i mean.

You mentioned that you were able to make 256x240 120hz on your GTX 1070 through hdmi , in theory, could nvidia intel or amd enable such low resolutions on the displayport out through drivers? or will displayport never be able to carry such a low pixel clock signal?

[ToastyX]

(01-04-2025 11:53 PM)juanme555 Wrote:  Toasty, do you think it could be possible for graphics cards manufacturers to bypass the 25mhz minimum pixel clock requirement? theoretically speaking i mean.

You mentioned that you were able to make 256x240 120hz on your GTX 1070 through hdmi , in theory, could nvidia intel or amd enable such low resolutions on the displayport out through drivers? or will displayport never be able to carry such a low pixel clock signal?

Theoretically it could be done, but it would be out of spec, and the adapter would have to support it as well. The problem is a low pixel clock might be considered an inactive signal. Usually low resolutions are implemented with double clocking and/or double scanning because of scan rate limitations. They could implement that as well, but there isn't a way to specify that in the EDID.

[willianwojcik]

(01-04-2025 05:50 AM)ToastyX Wrote:  

(01-04-2025 01:15 AM)willianwojcik Wrote:  It seems to be the same problem, or am I mistaken?

No, he has no problem using 240 Hz without DSR, and his issue happens with older drivers as well. In your case, I have no idea why 120 Hz isn't available even after adding it manually. The only thing that comes to mind is maybe they did some sort of workaround for your TV because of the 2560x1080 issue, so CRU is not having the proper effect. Does anything change if you edit the device ID to anything else using the "Edit..." button at the top?

Display Properties? I never touched anything

Curiously, removing the 4096x2160 resolution in CRU, not touching anything else, save and restart, the NVIDIA control panel lets set 120Hz normally at 2560x1080 (marked as native), 3840x1600 too, but DLDSR scales with the highest resolution left, 3840x2160, in 16:9

There should be something telling DLDSR that the correct resolution to scale is 3840x1600 in 21:9, but unfortunately there isn't. The only way is through CRU, but they managed to mess that up too, it seems to be intentional on the driver's part

On Dell 21:9 monitors, DLDSR works perfectly scaling with the native resolution. It seems like they want us to spend money on a monitor instead of using a TV, which is cheaper

[ToastyX]

(01-05-2025 01:54 PM)willianwojcik Wrote:  Display Properties? I never touched anything

So did you try changing the device ID and making 3840x1600 @ 60 Hz the first detailed resolution and adding 3840x1600 @ 120 Hz in a DisplayID extension block?

[Case]

(01-04-2025 05:50 AM)ToastyX Wrote:  2560x1440 @ 240 Hz doesn't require DSC at 8 bpc, and it also doesn't exceed the pixel rate that would cause DSR to be disabled. If it were the DSC issue, then CRU would have no effect either.

OK, I phrased that inaccurately. By writing "may or may not require DSC", what I really meant was "may or may not have DSC enabled", because, like I said, some monitors keep DSC enabled even when it's technically not needed for the given resolution and refresh.

Though I believe 1440p at 240Hz might at least in theory still require DSC on DisplayPort depending on the specific timings the monitor uses...or am I wrong?