Custom Resolution Utility (CRU)

[ToastyX]

(01-04-2018 02:45 PM)IanL Wrote:  I use CRU to match my ATI Graphics card to a LG 42" plasma TV over DVI. The 1920 x 1080 nominal resolution results in overscanning, and 1910x1060 has done the job.

I have just updated to Win 10 (Creators) and CRU 2.6 has no effect at all. The resolution appears for selection in the Win 10 Display Resolution selector, but it does nothing when selected.

I don't see how that's possible unless there's a problem with the graphics driver. What specific card do you have?

(01-04-2018 02:45 PM)IanL Wrote:  I updated CRU to 3.0, but it seems to crash something; the TV reports Invalid Signal. I recovered with Safe Mode and used CRU reset and a reboot of the PC to get the display back.

Is it possible that the latest Win 10 is storing resolution parameters in a different place?

There's nothing different about the way Windows 10 handles EDID overrides. The same settings should work the same way unless the graphics driver handles something differently with Windows 10. Simply changing the default 1920x1080 to 1910x1060 should behave the same with both CRU 1.2.6 and 1.3.1 on Windows 7-10.