Threaded Mode | Linear Mode

Duke_PH · 07-12-2015, 07:08 PM

I think you are right with Nvidia not accepting 4@60 as native. I made a custom EDID override with AWEditor to set 4k60 as default and it still kept 30 as native. Anyway I decided to make 1080p@60 default and see if i can use nvidias DSR to downscale 1440p to 1080 instead. Because DSR only renders at a multiple of the native then downscales it. And I have have no plan of playing at 8k downscaled to 4k, lol. Anyway it worked. I've ready some forums of people trying to use DSR in reverse and have seen people saying its impossible. So at least something good came out of this.

http://www.analogway.com/en/products/sof...editor/#dl
It's very good. Give it a try if you haven't already.

On a side note. I tried using the edid of a benQ at some point and when i opened nvidia control panel the pc thought my monitor was a real benq and even displayed the output as dvi. Now my theory is maybe this 4k@30native restriction is only for hdmi. And if we can fool the computer into thinking its displayport or dvi then setting 4k@60 as native may be possible. I tried doing this on my own with AWEditor but nvidia still reported HDMI. And I'm just not knowledgable enough to take the BenQ Edid and manually put in my tv's proper timings. Any ideas? PS, pass on the ability to usae DSR in reverse to anyone that needs it on other threads. Thanks

(07-12-2015 11:40 AM)ToastyX Wrote:
(07-12-2015 06:11 AM)Duke_PH Wrote: So I imported the dat file into CRU. Immediatly I noticed it change my custom res's to 4k@30, 1440p@60, and 1080@60. So I thought okay, whatever, as long as there is a block that tells my pc that 4k@60 is native. Saved it, restarted. Didn't work. So I loaded the bin file you gave me into MonInfo which translates it in to "English". The EDID you gave me has 4k@30 as native still. I'm sorry to say i didn't work. I wish I was knowledgeable enough to write a custom block myself. Any ideas?
MonInfo does not read the file correctly. It only reads the first half. To read the whole thing, you would need to import the file into CRU and export a .bin file instead of a .dat file. Even then, MonInfo does not understand the new data blocks. They are simply listed as "Reserved video related data" with the raw bytes.

The first detailed resolution is considered the native resolution, but 4:2:0 resolutions are defined in the "Extended (14)" data block in the extension block. The "Extended (13)" data block is the "video format preference" data block that's supposed to define additional native resolutions, but if NVIDIA's driver doesn't use that information, then I don't see a way to mark a 4:2:0 resolution as native.

You can try changing the first detailed resolution to 3840x2160 @ 60 Hz. That will get rid of 30 Hz at least. The problem is if NVIDIA's driver ignores that, then it might scale to 2560x1440 instead.

Those are the only two ways I know to define 3840x2160 @ 60 Hz as a native resolution. If NVIDIA doesn't support either method, then there's no way to do this. This is a driver limitation that NVIDIA would need to fix.