There is your problem. Please read the articles carefully. Enabling V-Sync enables frametime compensation which shifts frames so that they are in alignment with the scanout if they arrive a bit faster than the minimum frametime. You are not supposed to have V-Sync off with G-Sync / FreeSync unless you want slightly lower input latency due to, what BlurBusters terms as "defeating the scanout". V-Sync on with a frame cap when using G-Sync / FreeSync ensures the lowest possible latency achievable without defeating the scanout by tearing a fresh new frame right into the scanout. Context is important. You want 1ms less input latency, fine, you need frames to tear so that they are shown as soon as possible. There's no other way. Exactly. That's just that one game. I never encountered an issue so far with any game where I use 162FPS cap @ 165Hz with G-Sync. Because they behave in the same manner ... there's no magic involved here. It's display technology that we understand. If only your methodology wasn't flawed, this would have been the conclusion that would have followed. As it stands, most, if not all of us, who discuss the optimal settings for G-Sync / FreeSync monitors can spot stutter, jitter, and tearing from a mile away. There's nothing ... it's a flawless experience when the game engine itself isn't stuttery - and the vast majority of game engines are generally not stuttery, with perhaps a blip or two when loading textures or other assets.