Custom Resolution Utility (CRU)

[willianwojcik]

(Today 03:26 PM)ToastyX Wrote:  

(Today 01:42 PM)willianwojcik Wrote:  Right, 556.12, the last one that is scaling perfectly with DLDSR

I do two things to make it work. I pull up the 3840x1600 resolution to the first place in the "Detailed resolutions (2 slots left)" tab. Necessary to appear as native on the NVIDIA panel, otherwise the 2560x1080 resolution will appear as native, scaling incorrectly in the DSR. If you don't do this simple 1 second step, it won't work.

In the "Extension Block", "TV Resolutions" tab, I delete all 4096x2160 resolutions

In the "HDMI Support" tab, I do the same

That's all, I click on "restart64" and everything works as it should

https://imgur.com/a/MFzoJTs

Export a file from CRU.

Okay, done

It created a bin file, correct?

How can I send it to you?

Thanks

[ToastyX]

(Today 07:02 PM)willianwojcik Wrote:  Okay, done

It created a bin file, correct?

How can I send it to you?

Thanks

Any format is fine. You can upload it as an attachment here.

[willianwojcik]

(Today 07:19 PM)ToastyX Wrote:  

(Today 07:02 PM)willianwojcik Wrote:  Okay, done

It created a bin file, correct?

How can I send it to you?

Thanks

Any format is fine. You can upload it as an attachment here.

Done!

Thanks

[ToastyX]

(Today 08:45 PM)willianwojcik Wrote:  Done!

Thanks

I don't see 3840x1600 @ 120 Hz anywhere. Only 60 Hz.

[willianwojcik]

(Today 09:54 PM)ToastyX Wrote:  

(Today 08:45 PM)willianwojcik Wrote:  Done!

Thanks

I don't see 3840x1600 @ 120 Hz anywhere. Only 60 Hz.

From the beginning, when I use the C2's 21:9 ultrawide, the native resolution that appears on the NVIDIA panel is 2560x1080, not scaling correctly with DLDSR

To display 3840x1600 as native, you need to select the 3840x1600 resolution first in the "Detailed resolutions (2 slots left)" tab. Just pull it up and leave it as the first one, instead of 2560x1080. Nothing more

Doing this in CRU after 556.12 driver, the 3840x1600 is stuck at 60Hz

When I contacted NVIDIA, they initially told me it was a bug in the driver, but so far no solution, no answers

Strange isn't it? I don't know what to do to fix it

I found some people with the same problem on Reddit, with no solution. They tried everything

Thanks