Custom Resolution Utility (CRU)

[Azex]

(04-05-2019 01:09 PM)ToastyX Wrote:  

(04-05-2019 09:22 AM)Azex Wrote:  Big fan! I have been using CRU for a long time and have overclocked my monitor from 60hz to 77hz successfully. Now i have some questions that need your help. My current res is 1920x1080 at 77hz (Pixel Clock: 179.22 Mhz), after 77.00 hz if i go further to 78hz my monitor which is a Samsung sa350 shows the not optimal mode pop up and it doesn't go away. so i add a new stretch res in CRU 1444x1080 at 80hz and the pixel clocks reaches only 155.16hz and then i restart my pc and go to monitor settings, and the 80hz doesn't show up in that only 77hz and 60hz exist. Why is that? so i figure that only the refresh rate's with the native res will register in display adapter properties and no other res will work in cru. So i was wondering is there any way to bypass that?

The monitor settings only show the refresh rate for the current resolution. You have to switch to 1444x1080 first, or use the "List All Modes" button. If you still don't see the refresh rate, then you have GPU scaling enabled. GPU scaling scales everything to the native resolution, so only refresh rates at the native resolution will be available. Also, Samsung monitors usually don't allow more than 77 Hz regardless of the resolution, so you will get the "Not Optimum Mode" message at 80 Hz.

(04-05-2019 09:22 AM)Azex Wrote:  And 2nd question- Should i keep my timing parameters as high as possible or as low as possible, since increasing the timing parameters increases the pixel clock value and its obvious that our monitors can read data from cable at a limited value. so increasing the value would result in it not being able to read it and cause lag or something.I mainly play games like fortnite, pubg so should i keep at default value or lower for max refresh rate and stable gameplay?

It doesn't matter much if you're not hitting pixel clock limits. Higher blanking/totals just waste bandwidth. Lower vertical blanking/totals can cause the video card to not clock down when idle.

(04-05-2019 09:22 AM)Azex Wrote:  3rd question - the range limits, i set Vrate: 72-77hz Hrate: 31-81 and Max Pixel Clock to 240Mhz and i figured out these values do have an affect on the game like when i put my Max Pixel clock to 300Mhz or higher the game stutters a lot or even when i put Vrate:76-77hz it still stutters af. Now i do something extra while playing i put the process priority to realtime through task manager and the game feels really smooth like i get constant 77hz but sometimes it crashes. but when i play the same game at normal priority the game feels like its running on 30hz so how do i fix this ??

The range limits would not affect performance like that. CRU does not even include the range limits by default unless you have a DisplayPort FreeSync monitor, in which case the vertical rate would control the FreeSync range.

I disabled gpu scaling and you were right samsung cant go beyond 77hz, is that a firmware limitation or hardware limitation? if it is firmware, can you code it to increase the refresh rate limits?