Custom Resolution Utility (CRU)
|
07-19-2013, 01:14 PM
Post: #179
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(07-17-2013 05:52 PM)Mangix Wrote: My question is, where does the EDID specify that the monitor supports higher than 165MHz clock rates? The TV is connected to HDMI which supports up to 330MHz I believe. The driver currently thinks that my monitor is connected through DVI.NVIDIA's driver doesn't use any limit information. It only uses the information in the extension block to differentiate between DVI and HDMI. The problem is you're using a DVI/HDMI adapter on a dual-link DVI port, so when you disable the extension block, it treats the connection like DVI and tries to send a dual-link signal over a single-link connection, so the TV only gets half the picture. The patch is supposed to get around that. I don't know why that isn't working for you. The simplest solution is to use the HDMI port on your video card. Otherwise, you will have to craft an extension block that makes the driver think it's HDMI. I'm not sure what information it uses to determine that. (07-17-2013 04:23 AM)billsjo Wrote: Will CRU support switchable graphics anytime soon? I would gladly donate is there is any hope for this to work in the future. I have AMD/Intel HD 4k atm, and I just cant get 1080p100 to work, but it did work with my Nvidia/Intel HD 4k configuration through hdmi -> dvi-adapter and then DVI-D duallink into my Acer GD245HQ.It's not likely to happen in the near future. Intel's driver doesn't support the EDID override mechanism used by CRU to add custom resolutions, and Intel's SDK is not publicly available, so I don't have access to an Intel-specific method either. Even if I did, the program would need to work differently to be able to support an Intel-specific method, and there might be driver limitations that need to be patched, especially for what you're trying to do. I also don't have an Intel system to test this on. (07-15-2013 02:49 AM)Elysium Wrote: Same exact issue is happening to me with my LG L227WTG LCD display and AMD HD 7870 video card on Win 7 x64.I don't know why that's happening to some people because I've never seen it happen. It seems to be an AMD-specific driver issue, but I don't know how to trigger it, so I don't know how to work around it. What does the device manager show for the monitor when that happens? (07-12-2013 03:29 AM)tlaroze Wrote: Also I don't if this makes any difference but if I add 1680x1050 as the 2nd detailed resolution should it load the first at startup then I should be able to change it to 1680x1050 in Catalyst Control Panel? I tried adding 1680x1050 as the 2nd detailed resolution and the next time as the 3rd standard resolution and every time I still get the black screen at startup.There's no guarantee it will start at any particular resolution. Usually Windows will start with the last used resolution if available, or the native resolution if none was set. The highest resolution should be listed as the first detailed resolution to make it the native resolution. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 78 Guest(s)