Custom Resolution Utility (CRU)
|
11-20-2015, 08:53 AM
(Last edited: 11-20-2015, 09:31 AM by Spec-Chum)
Post: #1778
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-20-2015 02:35 AM)ToastyX Wrote:(11-19-2015 08:42 PM)Spec-Chum Wrote: My new monitor (Acer XR341CK) can do 85hz, but every time I change anything with CRU it disables FreeSync, as in it disappears completely from CCC.I don't have a FreeSync monitor, so I don't know what's required for FreeSync to work. The only document I found from AMD says the EDID must indicate that it is a "continuous frequency display" and report the range of refresh rates that the display supports, which is what CRU does when you include the range limits descriptor. The FreeSync "hack" is just modifying the range limits descriptor with an EDID override like CRU does, so I don't understand why it's not working. Yeah, it's showing in the Detailed Resolution list, it says: "Range Limits: 30-85Hz, 160-160 kHz, 600Mhz". Adding the 85Hz does work in that I can select 85Hz using CCC but it disables FreeSync completely, you can't even select it. Here's the original EDID bin file: http://1drv.ms/1l90UJ1 OK, just having a quick play. Even doing nothing but adding the default range into the details description breaks FreeSync. It's almost like CRU isn't creating the correct type of EDID. Just importing the original .dat file into CRU and not touching it also disables FreeSync lol What's going on? |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 79 Guest(s)