Custom Resolution Utility (CRU)

[CRTFTW]

(02-04-2018 03:04 AM)ToastyX Wrote:  Those numbers don't make sense, so it can't be a pixel clock limit. I haven't seen this sort of behavior before. Maybe it's listening to the kHz range limit. Have you tried including the range limits and changing the ranges? I don't see what else could be limiting it.

I did the incremental 1Hz test on multiple resolutions, and resolutions would always start being ignored at the same pixel clock for the specific monitor. Maybe the drivers are basing the max pixel clock of something other than what is found in "display properties/range limits"

But I'll give the horizontal limit idea a try, since like pixel clock it is a thing that is increasing with resolution/refresh rate.

And I also wonder if this could be a side effect of the displaport MST/SST standard that is tripping up the drivers, since this adapter is meant to be used in that way. But like I said, AMD's Ubuntu drivers don't have this issue, so it's definitely an artificial, maybe unintentional limit.

I guess my last resort would be to reprogram that HDMI dummy to give me better results, but I need to figure out what I would need to put in the new EDID. Well, that and I don't know of any software updated in the last 10 years for overwriting EDID's. All I can find on the net is Powerstrip, and some DOS-based tool.