Custom Resolution Utility (CRU)

[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]

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

[ToastyX]

(Yesterday 10:02 PM)Case Wrote:  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?

2560x1440 @ 240 Hz shouldn't need DSC with CVT-RB standard at 8 bpc, but 10 bpc would require it. DSC doesn't necessarily disable DSR. I think the max pixel clock for DSR is around 1350 MHz for 3000-series GPUs, so anything below that can still have DSR even with DSC enabled. DSR is all or nothing. NVIDIA completely disables DSR and EDID overrides if any resolution exceeds the max pixel clock, so CRU would have no effect in that case.

[ant23k]

I'm having trouble with CRU and need help, on my extension blocks it never shows my highest resolution (360hz) but instead shows 240hz, it does show up under "display ID, 1.3" but whenever I try to paste it into detailed resolutions it doesn't allow 360hz. The highest it lets me go is 260hz, could anybody help me solve this issue?

---

(01-04-2025 11:43 PM)ToastyX Wrote:  

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

Im having this same issue, i've been trying to set my native resolution to 1720 x 1080 @ 360hz however, from what i've seen in many youtube videos the process to do that is to paste the extension block (in this case 1920x1080 @360hz) into the detailed resolution and then change it into our preferred resolution. Maybe these steps are incorrect but it's what I've been taught in videos and I've done it multiple times on my old 144hz monitor and never had an issue. Now the issue is when you paste the 360hz into the detailed resolution, the refresh rate goes red. Tried to explain to the best of my ability as i don't know more than what youtube videos have told me.

[ToastyX]

(Today 08:20 PM)ant23k Wrote:  Im having this same issue, i've been trying to set my native resolution to 1720 x 1080 @ 360hz however, from what i've seen in many youtube videos the process to do that is to paste the extension block (in this case 1920x1080 @360hz) into the detailed resolution and then change it into our preferred resolution. Maybe these steps are incorrect but it's what I've been taught in videos and I've done it multiple times on my old 144hz monitor and never had an issue. Now the issue is when you paste the 360hz into the detailed resolution, the refresh rate goes red. Tried to explain to the best of my ability as i don't know more than what youtube videos have told me.

Stop following those videos. Many video don't explain anything and add unnecessary steps. Those videos cause me a lot of headache because people don't tell me what they're doing and then ask weird questions with no context. The first post explains why the refresh rate turns red, and the post you quoted tells you what to do.