Custom Resolution Utility (CRU)
|
10-06-2017, 11:25 AM
(Last edited: 10-06-2017, 02:24 PM by Conor)
Post: #3212
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Hi
I have an issue with some software which is caused by the order in which the PC is booted up and the TV turned on. System Info: Windows 10 Pro running nVidia GT710 Random brand 1080p TV Connection to TV via HDMI. The PC is connected to the TV via HDMI, the PC is set to autostart on power on so in a morning when the mains gets switched on the PC fires up, boots Windows, runs the software. Basically the software requires the resolution of the display to be defined in an argument, i.e startapp.exe -h1920 -v1080 r60 The problem I have is that if the TV is not turned on, Windows is defaulting to say 1024x768 and the app crashes because the resolution of Windows is not the same as specified in the argument. Once the TV is turned on then restarting the PC or restarting the app once Windows has detected the TV and set the proper resolution resolves the issue but it isn't ideal as the PC is usually hidden away. If we were using nVidia Quadro cards then it wouldn't be an issue as I could use the nVidia control panel to generate an EDID data file from the TV info and tell the driver to load the EDID data from a file instead of polling HDMI but sadly we're running GT 710s. Is this something the CRU application can solve by say removing all but 1080p from the list of available resolutions so Windows only has one option or would the issue still exist? Annoyingly enough it has never been an issue on VGA or Display Port. Many thanks for any advice. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 85 Guest(s)