Your configuration doesn't appear to limit your video gaming framerates. I use a smart FHD television with a nVidia 1050Ti with an i5 CPU (generation 7 or so) which tops out @ a maximum of 60Hz.

Vsynch is the Gog-recommended and effective fix for the problem I have experienced where my protagonist gets stuck in Star Wars games, like KotOR (uneven ground is the worst, like inside a cave). I think I might have needed it for The Witcher, too.

edit: markup syntax error

People using VSync, have you tried using the newer and better alternatives instead? AMD Enhanced Sync and NVIDIA Fast Sync.

Found another good video: Input Lag and Frame Rate Limiters

AMD Enhanced Sync - Nope. I usually use NVidia stuff.

Fast Sync - Yep, it's good...as long as it works. It's good for certain games b/t the birth of V-Sync and G-Sync. It's basically a mix of V-Sync and No Sync - you get the benefits of No V-Sync (no input lag), as it's also be selective of what frames to keep and also what one to toss; especially tossing frames that are worthless (i.e. blank).

G-Sync - This is the ideal method to me. I use this for most games; especially modern and newer title. No input lag, no screen tearing, and often no stuttering. Absolutely awesome, if you also put it with high framerates and have a monitor supporting that - i.e. 90fps, 120fps, 144fps, 240hz, etc etc.

About 1:30 into the video on the Enchanced Sync Technology, he lied about vsync. I'm gonna keep watching, and type as I watch, and i'm gonna predict that this "new technology" is merely reinventing vsync. I noticed the animation he used is also true of vsync, but his description was not, and it's clear that what he said is what's happening with vsync options in particular that's causing the "input lag." He said that they queue several frames in advance, rather than only outputting the most recently finished front buffer. This queueing is not inherent or necessary for vsync, however it is indeed precisely where it seems the lag is coming from with newer computers.

5:55: I fucking called it. The sad thing is, this is precisely how my vsync driver works for my toy OS, and... lemme see the copyright on the code... "2013-03-28 23:10:51.000000000 -0400" was my last update. Hell this strategy is probably older than windows. You know what it's called? We normally call this vsync. The only difference is that with my vsync driver, the game or whatever waits for the vsync, so it doesn't actually run faster. And when it doesn't run fast enough it allows tears, which is what old vesa drivers did, anyway.

Basically, what they're talking about is they've apparently created some industry standard at some point to redefined vsync, so games that vsync would progressively have longer and longer wait times so they could sell this new technology. Either that, or I'm a damned pioneer and failed to patent my fancy idea of the "faster double buffer" by not queueing frames once they're drawn.

Then again, other users in this thread have verified this behavior on their computers, so apparently they intentionally broke vsync this time to market "new technology" which was merely vsync.

EDIT: This post needs my driver at this point. That's not the whole thing, but that's the vsync part. The weaknesses and a huge mistake i made should be fairly obvious, but also actual testing of this driver on real hardware showed no "input lag."