Custom Resolution Utility (CRU)

[endao2]

(04-14-2023 06:01 PM)ToastyX Wrote:  [quote='endao2' pid='14634' dateline='1681370277']
If I may ask a different question. I have the GPU memory locked at max freq (2000Mhz in my case) and also dealing with some input lag (some gpu drivers way worse than others) and I am thinking to use another mode to see if GPU memory will go down

I found that some people fixed this using a different timing. Is there a risk running pixel clock at 346 vs the max reported(330 in my case)? I attached what it looks like if i chose that timing. Am I understanding correctly that the monitor is being instructed by the OS on how to operate by altering the registry? Or its a gpu driver change as well?


Also would this have an impact of how fast the image is being displayed right? Could this add / remove some perceived input lag? I'm troubleshooting Rocket League and its a very fast paced game

If this would fix the gpu memory issue with no impact in games it would be nice

(04-14-2023 06:01 PM)ToastyX Wrote:  If you're using DisplayPort, then 346 MHz is fine. Technically more blanking means it spends less time visibly refreshing and more time between refreshes, but the difference is miniscule and not worth worrying about. CRU creates EDID overrides in the registry, which is basically a description of what the monitor supports. It's not really altering anything in the registry since there's no override by default. The GPU driver will use the override if it exists. Otherwise it uses the monitor's EDID.

Thank you this is very informative and I can actually use this to maybe design some more tests.

And yes the default and custom resolution settings are identical at 120 Hz

Have no idea why the image looks better now