Custom Resolution Utility (CRU)

[ToastyX]

(06-03-2017 08:10 PM)Siso Wrote:  I'm having a problem with cru 1.3 on a dell u2913wm with gtx 1050 ti connected via displayport, the added resolution is not seen by the windows...any help will be appreciated it works ok with cru 1.2.6...

The only difference is CRU 1.3 should be able to read the extension block.
Export the working configuration from 1.2.6 and the non-working configuration from 1.3 and give me the files so I can see what's different.

[ToastyX]

(06-01-2017 11:29 PM)CRTFTW Wrote:  Toasty X, did you see the CRU shout out in a recent Digital Foundry video?

https://youtu.be/wSpHONwyBqg

That seems to be about adding lower resolutions with GPU scaling. I think it'd be better to use a 2560x1440 or 3440x1440 monitor with a higher refresh rate rather than scaling 3200x1800 to 3840x2160 @ 60 Hz. That way it'd still be better than 1080p except without the scaling, and the higher refresh rate would provide a better experience. Optionally throw in ULMB or G-SYNC/FreeSync for even smoother motion. G-SYNC/FreeSync monitors also have less lag than UHD TVs.

[lukilla]

(05-27-2017 02:53 AM)lukilla Wrote:  ...

So I can get up to 54 custom resolutions for my mame pc?... awesome!. I still wonder why there are such limits though.

I guess it doesn´t work like that, when I add a custom resolution with CRU then the CP custom resolutions get wiped out.

[CRTFTW]

(06-04-2017 07:57 PM)ToastyX Wrote:  That seems to be about adding lower resolutions with GPU scaling. I think it'd be better to use a 2560x1440 or 3440x1440 monitor with a higher refresh rate rather than scaling 3200x1800 to 3840x2160 @ 60 Hz. That way it'd still be better than 1080p except without the scaling, and the higher refresh rate would provide a better experience. Optionally throw in ULMB or G-SYNC/FreeSync for even smoother motion. G-SYNC/FreeSync monitors also have less lag than UHD TVs.

Yeah, I think it was mainly directed at people with their PC's hooked up to 4k TV's. But I just thought it was cool that your software was getting mentioned by Digital Foundry, who is part of Eurogamer and is probably the most popular publisher of Xbox/PS4/PC comparisons and similar content. They routinely are the ones to break major news like the design of the Switch and the specs for Xbox Scorpio.

[mynm]

Hi, I'm having problems with my CRU config since the windows 10 creators update. Using it I have screen micro freezes and mouse stop working when changing resolutions, openig start menu or some apps, stuttering in videos and sometimes in games. Does anybody see this?. I have a R9 380 with the last driver.

I will attach the config if it's needed to know the problem.

[Jacob Bugge]

ToastyX,

I was kindly referred to this thread by John over here (post #3),

https://www.sevenforums.com/graphic-card...tor-s.html

and I have tried to work my way through your instructions for my Philips 109P CRT monitor, however without luck.

The available resolutions for it that I know of are 1920x1440/60Hz, 1600x1200/75Hz, and 1280x1024/85Hz; and they work on an XP PC.

I updated my onboard Intel HD Graphics 4400 to the 4th generation Intel Graphics Driver for Windows 7/8.1 [15.36] (it is called 10.18.14.4578 by Windows 7), so I should meet the requirements, I believe.

Before running the CRU.exe, I could already choose those three refresh rates under Screen Resolution (RightClick from Desktop) or in the Graphics Control Panel.

When starting the CRU.exe for the first time, the monitor was listed as active and with an asterisk.

And from the start the Detailed Resolutions box contained 1600x1200 but at 85Hz which I changed to 75Hz.

And from the start the Standard Resolutions included 1920x1440/60Hz, 1792x1344/60Hz, 1600x1200/75Hz, 1280x1024/85Hz, 1280x1024/60Hz, 1024x768/85Hz, 800x600/85Hz, 640x480/85Hz.

And from the start, the Established Resolutions included 640x480, 800x600, 1024x768, and 1280x1024, at different refresh rates up to 75Hz, with All ticked.

After running the CRU.exe, the monitor is listed as active and with an asterisk.

When I run the restart.exe, the screen goes blank a few times, the first time showing an even lower resolution than 1280x1024, and ends on 1280x1024 with a window called Restart 1.3, with the statement Graphics Driver Restarted and three buttons, Restart Again, Recovery Mode, and Exit.

I have tried multiple restarts and also recovery mode.

Whatever I have done, I still only get the resolutions from 1280x1024 down, exactly as before running the CRU.exe and restart.exe.

[ToastyX]

(06-07-2017 03:43 PM)Jacob Bugge Wrote:  I updated my onboard Intel HD Graphics 4400 to the 4th generation Intel Graphics Driver for Windows 7/8.1 [15.36] (it is called 10.18.14.4578 by Windows 7), so I should meet the requirements, I believe.

Before running the CRU.exe, I could already choose those three refresh rates under Screen Resolution (RightClick from Desktop) or in the Graphics Control Panel.

When starting the CRU.exe for the first time, the monitor was listed as active and with an asterisk.

There should not be an asterisk when you first run CRU. Run reset-all.exe and reboot to make sure.

(06-07-2017 03:43 PM)Jacob Bugge Wrote:  And from the start the Detailed Resolutions box contained 1600x1200 but at 85Hz which I changed to 75Hz.

And from the start the Standard Resolutions included 1920x1440/60Hz, 1792x1344/60Hz, 1600x1200/75Hz, 1280x1024/85Hz, 1280x1024/60Hz, 1024x768/85Hz, 800x600/85Hz, 640x480/85Hz.

If those resolutions exist from the start without any changes, then the monitor already defines those resolutions, so you're running into a graphics driver limitation. The driver might not be allowing pixel clocks greater than 165 MHz, which would limit you to 1600x1200 @ 60 Hz. CRU won't be able to get around that limitation.

You don't need to change the detailed resolution to 75 Hz since it already exists as a standard resolution, but you can try changing it to 60 Hz using the "CRT standard" timing option to see if it is indeed a pixel clock limitation.

(06-07-2017 03:43 PM)Jacob Bugge Wrote:  When I run the restart.exe, the screen goes blank a few times, and ends with a window called Restart 1.3, with the statement Graphics Driver Restarted and three buttons, Restart Again, Recovery Mode, and Exit.

With Intel, you might have to reboot instead of running restart.exe for changes to take effect. I haven't tested any Intel GPUs, so I don't know what limitations they have.

[ToastyX]

(06-07-2017 09:51 AM)mynm Wrote:  Hi, I'm having problems with my CRU config since the windows 10 creators update. Using it I have screen micro freezes and mouse stop working when changing resolutions, openig start menu or some apps, stuttering in videos and sometimes in games. Does anybody see this?. I have a R9 380 with the last driver.

I will attach the config if it's needed to know the problem.

That doesn't seem related to CRU. Try using DDU to completely uninstall the old driver before installing the latest one: https://www.wagnardsoft.com/display-driv...aller-ddu-

[ToastyX]

(06-04-2017 10:15 PM)lukilla Wrote:  I guess it doesn´t work like that, when I add a custom resolution with CRU then the CP custom resolutions get wiped out.

Try adding custom resolutions with CRU first before using the NVIDIA control panel. The driver might be interpreting EDID changes as different monitors.

[mynm]

(06-08-2017 07:00 PM)ToastyX Wrote:  

(06-07-2017 09:51 AM)mynm Wrote:  Hi, I'm having problems with my CRU config since the windows 10 creators update. Using it I have screen micro freezes and mouse stop working when changing resolutions, openig start menu or some apps, stuttering in videos and sometimes in games. Does anybody see this?. I have a R9 380 with the last driver.

I will attach the config if it's needed to know the problem.

That doesn't seem related to CRU. Try using DDU to completely uninstall the old driver before installing the latest one: https://www.wagnardsoft.com/display-driv...aller-ddu-

Thanks.

That's what I did, using DDU to completely uninstall the driver, and I didn't have any problem until setting the bin I'm used to use. Deleting the config I don't have the problem.

So I'm sure I get the problems with my config. And I didn't have the problems before the creators update.

This is my config: