Custom Resolution Utility (CRU)
|
06-20-2022, 09:02 AM
(Last edited: 06-20-2022, 09:03 AM by pneumatic)
Post: #6687
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Hello,
Is there a trick to getting both n/1 and n/1.001 modes exposed through Windows display settings dialog? eg. On my Nvidia system, I can create with CRU the following modes: [23.976hz, 24.000hz, 59.940hz, 60.000hz, 119.88hz, 120.00hz] and these will appear in Windows display settings as [23hz, 24hz, 59hz, 60hz, 119hz, 120hz]. However on my AMD GPU system, I only get [24hz, 60hz, 120hz] appearing in Windows display settings. The trick to getting all modes exposed on the Nvidia system was to add them to a new DisplayID 1.3 block in CRU and delete the corresponding n/1 modes from the CTA block's "TV resolutions" sections. However this trick doesn't work on my AMD system. The only way I can get both n/1 and n/1.001 modes exposed is by creating the missing n/1.001 ones in Radeon Settings custom resolution utility. However that utility sucks and is full of bugs (which I can work around, but it's still janky and I much prefer to use CRU). I tried auditing the registry with tool RegScanner to see what registry keys were being modified when clicking Apply in Radeon Settings custom resolution, but I couldn't glean anything coherent. My current hypothesis is that perhaps it's up to the GPU driver whether it adds modes from the EDID to the list of modes exposed through Windows display settings. I'm guessing there is some WinAPI function that does that which Nvidia is calling but AMD isn't. On the other hand, this article says that both n/1 and n/1.001 modes should be exposed, so I don't really know what's going on. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 88 Guest(s)