Custom Resolution Utility (CRU)

[ToastyX]

(10-29-2016 11:06 PM)SweetLow Wrote:  >Intel's graphics _driver_
>That's a _driver_-specific method
And what is the problem?

Lots of problems. It's not publicly documented. Nobody knows what the first number should be, so how can CRU know what number to write? What if there are two of the same monitor? Which belongs to which? The first number seems to be port-based, while the monitors are in the registry are not, so there's no way to connect them. There might be a driver-specific way to handle this, but the driver's API functions and SDK are not publicly available either. I also don't have a system with an Intel GPU, so how can I test this? What systems does this trick work on? How will this conflict when the new drivers support EDID overrides?

(10-29-2016 11:06 PM)SweetLow Wrote:  >usual way
Microsoft defined way, to be precise

At least this way, I know how it's supposed to work, and it works with both AMD and NVIDIA.

(10-29-2016 11:06 PM)SweetLow Wrote:  >but they are working on it
...starting from 2011 year. You can wait next 5 years, of course.

They only started working on this recently. They've already made the necessary changes. The changes haven't made their way into official releases yet, but it's coming.