Custom Resolution Utility (CRU)
|
11-28-2014, 06:20 AM
Post: #1123
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-28-2014 05:18 AM)ToastyX Wrote:(11-28-2014 04:40 AM)LTC Wrote: It's a VGA monitor. Not DVI-D, not HDMI, old school VGA. And ever since Vista it's no longer plug-and-play, I've to muck around to get its proper modes, not just whatever generic low-res low-RR CRT modes Windows has. Back when I first got Vista, that was accomplished by installing the monitors drivers, which I didn't really need to before. It's gotten more complex over the years. I had the same problem with a Viewsonic G220fb, which I no longer own, it was plug and play on XP, stopped being so on Vista. I've never needed to do the "remove the twelfth pin-mod", and I have multiple high-quality cables as well as a few dvi-to-vga adapters, from past cards and also store bought. Way back then I remember reading from other people with the same issues on Vista, so I just got on with life. This monitor runs just fine with my laptop Intel graphics on Windows 7, it also ran fine with all cards I had(all NVIDIA) since I bought it.I know it's VGA. The "Use EDID" option is only available with VGA. CRU needs that option to be enabled. Yes it does. But only on Vista and later, including this new PC with 8.1 Pro. Back when I had XP both this one and the Viewsonic were properly recognized. For the moment, let's assume the EDID is missing for whatever reason, even though I never messed with it and it used to be recognized, it really doesn't matter as even when told not to "use the EDID or driver defaults" Catalyst still presents a limited set of choices in terms of both resolution and refresh rate, no matter how high I set the "Maximum resolution" and "Maximum refresh rate" drop box selectors that are made available when "use EDID" is unchecked below the EDID checkbox in the "Monitor attributes" section. Not only are some refresh rates italicized, and thus unselectable, as the set of which modes are available and which are not doesn't make any sense, with modes with very high pixel clock available while others with relatively low pixel clocks are not. Most importantly, the overrides provided by CRU along with checking the "use EDID" checkbox make the driver offer the correct modes, just not at once and also not safely as it needs to be restarted, sometimes just a couple times, sometimes several, before it starts behaving appropriately. This constitutes driver bug 2: it has the EDID to work the modes from (through the override), it is being told to use it, yet it won't do so without being restarted, more than once indeed, which may lead it to become unstable and crash. Driver bug 1 is having arbitrary refresh rates unavailable when it has been told NOT to use the EDID, which is a behavior different than, as an example, the Intel drivers on my laptop. Steps needed to use these modes on my laptop: 1 Tell it I want to use these custom modes. 2 Confirm that I know what I'm doing bla bla bla. 3 There's no step 3, the modes are available to applications and in "list all modes" on Windows advanced display settings. I have tried restarting it with the box checked, unchecked, it doesn't matter. The modes only work after a few tries! Is it clear what I'm saying now? How come something that is so simple with a laptop IGP drivers can be so hard with a dedicated graphics card driver? |
|||
« Next Oldest | Next Newest »
|