Custom Resolution Utility (CRU)

[ToastyX]

(11-13-2021 01:49 PM)d2freak Wrote:  One thing is on my mind though. This used to work. On the very same computer. This weird behaviour started after I used another program called Moonlight, which is a program for Android to mirror the PC screen to your phone for gaming. It hooks into GeForce Experience.

Why can this be related? Well, here is the thing: If you use a non-standard resoulution in that program (such as my phones res) it injects it somehow onto the computer and switches to it. This is supposed to be temporary and it should not be visible in any list (I asked the dev about this). Problem is, this resolution got "stuck" on my computer. I tried to remove it in CRU but it didn't show up there.

So... I used reset-all from CRU and it removed the weird resolution, as well as my working CRU settings. Ever since then, I've had this weird problem I described. Like from exactly that day. Do you think CRU and Moonlight could have interacted badly with eachother causing this buggy state?

Also, if I go into "list all modes" in windows, after applying the correct CRU settings, I still see 4k resolutions as well as that resolution from Moonlight (1440x900)...not sure if this is the problem too? I don't know how to delete stuff from that list.

NVIDIA does have a function to set a temporary resolution, which is what the NVIDIA control panel uses when testing custom resolutions, so Moonlight could have triggered a bug in the driver that's persisting in the driver's settings. Try reinstalling the NVIDIA driver after using DDU to completely uninstall the driver: https://www.wagnardsoft.com/display-driv...aller-ddu-