Custom Resolution Utility (CRU)
|
03-09-2023, 04:37 PM
Post: #7266
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(03-09-2023 12:13 PM)ToastyX Wrote:(03-09-2023 03:46 AM)Parallellines Wrote: I use HDMI, not DisplayPort, so setting the range there at the top wouldn't do anything. And yeah I suppose it's a driver bug indeed since everything worked normally with my 580.I need to know if including the range works or not, not just changing the range, which has no effect if it's not included. There's nothing special about your hex edit, so there's no reason why this shouldn't work with CRU. Including it still broke the resolutions. As I said, it happens with any edits whatsoever and I only used the Freesync range value as a quick example. I also took the opportunity to do another test: I reset everything and simply imported the default, untouched EDID using CRU. That still broke the resolutions somehow. And yes, the hex edit isn't special, but shouldn't CRU only touch the absolutely required bytes instead of messing with the rest of the file structure? These issues stem from those other edited bytes. On a related note, I forgot to mention that I had a weird issue with my 580. Whenever the monitor would wake from sleep the entire screen would be dim except for the mouse cursor and the fix was to change the resolution or press CTRL+SHIFT+WIN+B. Again, that only happened when I made edits with CRU and I just dealt with it for years and didn't think much about it. This doesn't happen anymore with the 5700XT. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 88 Guest(s)