Custom Resolution Utility (CRU)

[imfakeyo]

Just made an account to let you know that the newest AMD beta driver (15.9.1) has broken the CRU. I'm on Windows 10 Pro 64bit. I can add new custom resolutions but they don't appear in windows or inside games. Trying to launch games with the custom resolution in the cfg makes it reset back to default. Rolling back the driver fixes the issue.

[Seketh]

Hi guys, I'm having a problem with 60hz over HDMI.

I use CRU with an HDMI-audio.dat custom extension block. I delete every resolution, and then add 70hz and 60hz on the Extension Block.

With just 70hz, everything is fine, the Nvidia Control Panel shows only "PC" resolutions.

When I add 60hz, it shows both "HDMI" and "PC" resolutions. 59hz is also present.

How can I fix this?

[ToastyX]

(10-10-2015 04:19 PM)Seketh Wrote:  Hi guys, I'm having a problem with 60hz over HDMI.

I use CRU with an HDMI-audio.dat custom extension block. I delete every resolution, and then add 70hz and 60hz on the Extension Block.

With just 70hz, everything is fine, the Nvidia Control Panel shows only "PC" resolutions.

When I add 60hz, it shows both "HDMI" and "PC" resolutions. 59hz is also present.

How can I fix this?

You need to add 60 Hz in the main window, not the extension block. 70 Hz can go in either place, but if you only have two resolutions, you can put both in the main window.

[ToastyX]

(10-10-2015 01:42 PM)imfakeyo Wrote:  Just made an account to let you know that the newest AMD beta driver (15.9.1) has broken the CRU. I'm on Windows 10 Pro 64bit. I can add new custom resolutions but they don't appear in windows or inside games. Trying to launch games with the custom resolution in the cfg makes it reset back to default. Rolling back the driver fixes the issue.

I'm not seeing any issues with 15.9.1. You didn't mention what resolutions you're trying to add. Are you taking into account pixel clock limits?

[ToastyX]

(10-08-2015 11:58 PM)falkentyne Wrote:  is it possible (or even feasible) to make a patch to bypass the displayport limits, or at least to extend the pixel clock range for 8 bits per channel color, or is this not possible?

It might be possible, but I haven't found a way to do it. The DisplayPort limits are not constants like the other limits, so it would be very difficult to figure out what code needs to be changed.

DVI, HDMI, and VGA are constant streams of data with the pixel clock determining the data rate, so I can just change the limits. DisplayPort is packet-based with fixed clock speeds, so I'm not sure how overclocking would work.

[falkentyne]

(10-10-2015 06:32 PM)ToastyX Wrote:  

(10-08-2015 11:58 PM)falkentyne Wrote:  is it possible (or even feasible) to make a patch to bypass the displayport limits, or at least to extend the pixel clock range for 8 bits per channel color, or is this not possible?

It might be possible, but I haven't found a way to do it. The DisplayPort limits are not constants like the other limits, so it would be very difficult to figure out what code needs to be changed.

DVI, HDMI, and VGA are constant streams of data with the pixel clock determining the data rate, so I can just change the limits. DisplayPort is packet-based with fixed clock speeds, so I'm not sure how overclocking would work.

I see. Thank you.

A bit unrelated, but I had been doing some overclocking. Got my XL2720Z to 2560x1440 at *115hz*. This was only possible with bizarre HT:

2560x1440
Porch 48/3
Sync 32/5
HT: 2641 (any lower and values turn red)
VT: 1497 (1496=black screen). Only VT 1497-1502 work.
Refresh rate: 115hz.
Pixel clock: 454.67 MHz
(displayport. 6 bpc).
Tried DVI once 120hz...monitor switched to VGA input right away).

1 more hz higher (116hz) and I start to get flickering pixels.
120hz has too much corruption yet there is no frameskipping at all...image is perfectly smooth, just flickering pixels

Do you think 115hz is stable/safe even though I don't see any "obvious" flickering? Maybe theres very random flickering, cant tell for sure. No frameskipping.

Any lower on the VT and I get a black screen/out of range message with no display.

Since the lowest valid VT for this is 1449 (black screen/out of range), I'm assuming this VT range that works (1497-1502) only works because this is (im guessing) reserved internally for Lightboost mode for reducing strobe crosstalk (even though 1138, 1143 and 1149 tell the monitor to enter 3d mode). There's no other explanation as to why this VT range works, and everything from 1400-1495 gives an out of range error (from testing VT's at 1920x1080). Note VT 1370-1400 show an image but the OSD says "out of range" anyway and most VT's have frameskipping in this range. (the scaler resolution shows 1792x1344 in that VT range :/)

[falkentyne]

Failed in my attempt to overclock to UHD

3840x2160@30hz actually works all the time but is horribly laggy (automatic timings); unusable except for taking screenshots. No way I can play even Path of Exile with lag that bad. but boy does it look nice if I'm not moving...

3840x2160@60hz exceeds DP 1.1 specs...tried over DVI, screen shuts off

3840x2160@50hz...Over DVI...screen appears for like half a second then shuts off, turns on, turns off, etc.

3840x2160@50hz over displayport...works when it wants to.
Had it working a few times...most beautiful thing ever. 4x Supersampling on a 1920x1080 monitor. Had to turn off blur reduction or the backlight turns off. But..then try again and it just switches to VGA input. No out of range error or anything...One time it worked but the screen looked like a 1:1 shrunk image of a lower resolution I really wish I could find a setting that worked reliably...

Wanted to try to see how Path of Exile looks but if I can't even get it to stick 100% on the desktop, no point...

3200x1800 wont work at all no matter what I do.

I guess my stable limit then is 2560x1440@115hz with HT 2641 and VT 1497...

[falkentyne]

Well, ToastyX,
Looks like the Mstar scaler VT sorcery tricks still work.

Remember I told you that "sometimes" 3840x2160@50hz displays a correct screen?
Well seeing how the same VT tricks to reduce strobe crosstalk work (e.g. VT 1497-1502 at 1920x1080, which send a 1440 signal to the scaler (if the factory service menu reading of 1280x1440 is to be believed),

I decided to use the CRU default VT for 3840x2160 (which is 2220 VT) for 3200x1800@60hz (and the pixel clock fits within DP ranges).

The default VT for 3200x1800 in CRU is 1852. This just shows out of range (black screen+out of range error) no matter what VT I use in this range. Tested quite a few.
So I jacked the VT Way up to 2220.

And sure enough......

3200x1800@60!
Didn't seem to be frameskipping at all.
However blur reduction did not work, even double strobed. Backlight shut off as soon I tried enabling blur reduction.

Seems to be the limit now. 3840x2160@30hz works but is too laggy to be useful....

Yes ToastyX I know what you're thinking.
You're thinking "why don't I just use AMD VSR and use 3200x1800x60? without all of this trouble? (and then I can still use blur reduction)....
Yeah I could do that, but that's no fun and...

Main problem is VSR doesn't seem to work very well with custom resolutions and if I have a VT tweak active for 1920x1080@100hz, 2560x1440@100hz doesn't appear with VSR...only 2560x1440@60hz appears in the CCC...

I know this is probably useless since I'm on a 1080p screen but still...

[marsupilami]

Hi guys, could I ask something?

I'm gonna buy monitor soon and I want to see the feeling of 21:9 Ultrawide first.
So I tried Custom Resolution Utility on my 1080p monitor (old Samsung B2230).
On 'detailed resolutions', I add 1792x768 @ 60Hz with Scaling mode 'Use centered timings' on Catalyst Control Center.
It's Catalyst 15.201 and I have Fury X on Windows 10 64bit.

It works perfectly in Windows. 1:1 pixel mapping, centered and all around black bar.
But everytime I tried HOR+ games (old game like Skyrim, NFS Hot Pursuit 2010 and new game like Project CARS) in fullscreen, the 1792x768 resolution always stretched (not 1:1 pixel mapping) to entire screen area, no black bar.
It ONLY works if I had the games on Windowed mode.

Age of Empires II HD works perfectly on fullscreen but that's because it's a pixel based games.

I also tried 1920x810 (should be only have top and bottom blackbar) but the result are the same.
'Enable GPU up scaling' on CCC doesn't affect anything whether it's checked or not.

What I'm trying to achieve is to buy large 16:9 monitor such as BenQ BL3200PT and convert it into 2560x1080 Ultrawide occasionally. For that I don't want it to be stretched.

Any idea why? Is it depends on the monitor or is it issue from the games or it's wrong setting on Catalyst Control Center?

[ToastyX]

(10-12-2015 02:33 PM)marsupilami Wrote:  Hi guys, could I ask something?

I'm gonna buy monitor soon and I want to see the feeling of 21:9 Ultrawide first.
So I tried Custom Resolution Utility on my 1080p monitor (old Samsung B2230).
On 'detailed resolutions', I add 1792x768 @ 60Hz with Scaling mode 'Use centered timings' on Catalyst Control Center.
It's Catalyst 15.201 and I have Fury X on Windows 10 64bit.

It works perfectly in Windows. 1:1 pixel mapping, centered and all around black bar.
But everytime I tried HOR+ games (old game like Skyrim, NFS Hot Pursuit 2010 and new game like Project CARS) in fullscreen, the 1792x768 resolution always stretched (not 1:1 pixel mapping) to entire screen area, no black bar.
It ONLY works if I had the games on Windowed mode.

Age of Empires II HD works perfectly on fullscreen but that's because it's a pixel based games.

I also tried 1920x810 (should be only have top and bottom blackbar) but the result are the same.
'Enable GPU up scaling' on CCC doesn't affect anything whether it's checked or not.

What I'm trying to achieve is to buy large 16:9 monitor such as BenQ BL3200PT and convert it into 2560x1080 Ultrawide occasionally. For that I don't want it to be stretched.

Any idea why? Is it depends on the monitor or is it issue from the games or it's wrong setting on Catalyst Control Center?

That's supposed to work. I don't understand how scaling could work correctly in Windows but not in games. If the GPU scaling option is not working correctly, then that's a driver bug that I can't do anything about. I don't know what's going on with the Windows 10 drivers. Some people are having the opposite problem where resolutions are centered instead of stretched. Supposedly scaling works correctly with older drivers, but then Windows 10 will automatically try to update the driver even if you disable automatic driver updates. Windows 10 is becoming a hassle to use. If the monitor has scaling options, disable GPU scaling to send the resolution to the monitor instead. The Samsung should have an image size option, but I don't know if it can scale resolutions like 1792x768 or 1920x810.