Custom Resolution Utility (CRU)
|
10-27-2020, 01:25 AM
(Last edited: 10-27-2020, 01:42 AM by MonopolyMan)
Post: #5237
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-27-2020 12:58 AM)ToastyX Wrote:I added the NV_Modes key with "2560x1080=1;" and now most of the resolutions are gone. There are still two left that I don't want: 1768x992 and 1176x664. Seems like there's an overscan setting somewhere.(10-26-2020 11:28 PM)MonopolyMan Wrote: Thanks! I got rid of the Nv_Modes key under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 and it sucessfully got rid of some of the resolutions, but I'm still seeing some resolutions I don't want. Any idea where these are coming from? I'm trying to do scan the registry for them, but so far I haven't had any luck.Delete the TV resolutions from the extension block. You don't need to define the same resolution in multiple places. If that doesn't work, you might need to create an NV_Modes with just "2560x1080=1;" in it. Edit: Despite the extra resolutions, Parsec now stays at 2560x1080! I'm still curious about these two remaining resolutions and where they come from, but my original goal has been achieved. Also, for future reference, do you know if AMD has a registry key similar to NV_Modes? |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 157 Guest(s)