Custom Resolution Utility (CRU)
|
12-13-2024, 10:10 PM
Post: #8650
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(12-13-2024 02:25 PM)ToastyX Wrote:(12-13-2024 10:40 AM)stej Wrote: Am I correct to assume that if I import an edited edid with cru, it will override everything the monitor reports, essentially nullifying the monitor's ability to switch configurations?That would depend on what the graphics driver considers a unique monitor. Usually each EDID would be considered a different monitor, so you can override just one of the EDIDs. I don't see additional monitors created in Enum\Display in the registry, so I guess not, it only updates the EDID. Comparing the contents of the exported .bin files I see that the first part of the file, presumably the EDID base, remains constant. What changes is the extension blocks. Which explains why it's not detecting additional monitors I suppose. So, from your reply it seems that my assumption was correct. How about workarounds? The block I want changed is always present in every reported configuration and its contents remain static. Any ideas for overriding a couple bytes and letting everything else pass through? |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 81 Guest(s)