Blur Busters Forums

I’m hoping to get some insight into an issue I’ve been having with my G-Sync laptop. I've been using this machine for a while, but a few months ago, I started noticing some strange graphical artifacts.

The problem is that these artifacts appear under very specific, yet seemingly disconnected, scenarios. I have been trying to find a pattern or any coherence between them, but I haven't had much luck so far.

Here are the scenarios I've identified:

• LSFG: When using Lossless Scaling Frame Generation with G-Sync enabled for the game, plus G-Sync compatibility enabled in the application settings, I get these specific artifacts. However, if I disable G-Sync specifically for that game, the issue goes away.
• Unity Engine Games: I see similar artifacts in games like PEAK and GTFO whenever the game stutters badly. GTFO is a particularly good example to reproduce this, as it suffers from some poor frame pacing issues.

I’ve also noticed a very particular behavior depending on the display's refresh rate: The artifacts appear when the frame rate is inside the G-Sync range, but only before LFC (Low Framerate Compensation) kicks in. Once the frame rate drops low enough for LFC to engage, the artifacts disappear.

At first, I was worried this might be a physical hardware issue, but at some points I discovered that I can capture the artifacts in screenshots and video recordings. Hence, I’m fairly certain it isn't a hardware issue, and instead I suspect this is a software problem.

Has anyone experienced this before? Any insight would be appreciated.

Here is a recording and a couple screenshots of the artifacts I've described:

reference

artifacts

After further evaluation, I found that what I show in my recordings is a separate issue from what I'm perceiving in the display, though they have a correlation around the driver versions where both started to occur. I'll do further testing to narrow down the exact version. Hopefully I can figure out where to report this to NVIDIA, as I've found other posts on Reddit reporting similar findings.

Found the issue first appeared in driver version 531.41, with all subsequent versions still being affected.
I reported it to NVIDIA through the feedback form and copied some of the details into a thread on their forums.
https://www.nvidia.com/en-us/geforce/fo ... ecordings/