Custom Resolution Utility (CRU)

[ToastyX]

(11-22-2021 05:33 AM)chef_pooh Wrote:  I've been trying to get my Apple Pro Display XDR to show its full 6k resolution over Thunderbolt 3 on my Windows desktop, and I'm looking for some help. My motherboard (ASRock x570 ITX TB3) has a TitanRidge TB3 controller with DP1.4, so there's enough bandwidth to support 6k...but, as reported by others ( https://forums.macrumors.com/threads/app...t-29114824 ), Windows doesn't seem to expose a 6k resolution when using TB3. On the other hand, I'm able to support 5k with 10 bits (or even 12, despite the monitor only being 10 bit), which is more bandwidth than 6k8bit -- so I'm convinced this is an EDID problem.

Can you describe how everything is connected? From what I've read, you need two DisplayPort cables from the NVIDIA GPU to the Titan Ridge controller, but I only see one DisplayPort input on the motherboard. The 6K resolutions don't fit within the max pixel clock for DisplayPort 1.3/1.4 HBR3 (1080 MHz pixel clock at 8 bpc), so either it requires two streams or display stream compression (DSC). Maybe the Titan Ridge controller is preventing DSC from working. Why not connect the monitor directly to the video card using the Moshi USB-C to DisplayPort cable?

I don't think anything is wrong with the EDID. The reason CRU doesn't list the monitor is because the reported EDID in the registry is supposed to be the first 128 bytes only, but apparently that changed with Windows 11, and your monitor is reporting 5 extension blocks, while older drivers only supported up to 3, so CRU saw too much data and failed to process the monitor. I will fix that in the next version. For now, try this: https://www.monitortests.com/CRU-EXT.zip