Posted July 14, 2021
I've had this issue for as long as I can remember, possibly since Dec. 2019 when I first began using Galaxy 2.0. It's the primary reason that I've not used it in day-to-day gaming. It happens long after I've launched Galaxy 2.0, at least 10 minutes to over an hour afterwards, and it reoccurs during the same session. Ahh.. that makes me wonder if it's related to my unorthodox dual display setup. My main display is a 4K HDR TV connected via HDMI, and in Windows' settings I have its scaling set to 200%. I have HDR disabled where and when it's possible to, but it does sometimes enable itself when launching certain apps. My secondary display is a 1080P non-HDR PC monitor connected via DVI, and its Windows scaling is set to 100%. My guess is that the 200% scaling is causing an issue, but that's just a hunch based on the fact that it can sometimes cause other weird issues.
My setup is otherwise straightforward: Windows is kept updated automatically, I don't have any third-party security software, and I often use Nvidia GeForce Experience's overlay/game capture a.k.a. ShadowPlay.
My setup is otherwise straightforward: Windows is kept updated automatically, I don't have any third-party security software, and I often use Nvidia GeForce Experience's overlay/game capture a.k.a. ShadowPlay.