Custom Resolution Utility (CRU)

[LTC]

(11-28-2014 12:21 PM)ToastyX Wrote:  

(11-28-2014 06:20 AM)LTC Wrote:  Most importantly, the overrides provided by CRU along with checking the "use EDID" checkbox make the driver offer the correct modes, just not at once and also not safely as it needs to be restarted, sometimes just a couple times, sometimes several, before it starts behaving appropriately.

This constitutes driver bug 2: it has the EDID to work the modes from (through the override), it is being told to use it, yet it won't do so without being restarted, more than once indeed, which may lead it to become unstable and crash. Driver bug 1 is having arbitrary refresh rates unavailable when it has been told NOT to use the EDID, which is a behavior different than, as an example, the Intel drivers on my laptop.

Steps needed to use these modes on my laptop: 1 Tell it I want to use these custom modes. 2 Confirm that I know what I'm doing bla bla bla. 3 There's no step 3, the modes are available to applications and in "list all modes" on Windows advanced display settings.

I have tried restarting it with the box checked, unchecked, it doesn't matter. The modes only work after a few tries!

So have you tried the adlutil method that I mentioned?

Not as of yet, since an AMD customer service representative has contacted me and asked that I try the 14.11.2 beta drivers, which I already did and still found the same issue as before. Now I'm waiting for them to get back to me. I'll give them a chance and try and wait for an official solution to this problem for now.

Let's see how this goes...