Screen tearing on fast movement

[TheGameV30]

Hello!
Continuing the conversation from the comments section of the G-Sync 101: Control Panel article.

My setup: i9-13900KF, RTX 4090, 64GB RAM, 144Hz LG 27GR93U-B

Notice screen tearing along bottom 1/3 of my screen when playing Destiny 2 & Rocket League (play these the most) when moving the screen quickly.

Current NVCP settings: Max FPS 141, G-Sync on for windowed & full screen mode, V-Sync On

Destiny 2 settings: V-Sync Off, in-game limiter off, Reflex On

Monitor currently set to Extended Adaptive-Sync, Response Time Fast & connected via DP1.4

Any help on how to fix the screen tearing would be greatly appreciated as I am very new to PC gaming & have no idea what I’m doing lol. Any other info that would help, let me know. Thanks!

[RealNC]

Enable the g-sync overlay indicator in the Nvidia control panel to make sure g-sync is actually active in the game (the "G-SYNC" should appear in the top-right corner of the screen in-game.)

If it's active, then try switching vsync from "on" to "fast" in NVCP. This fixes tearing with some monitors.

[TheGameV30]

Thanks! I turned on the overlay and it is showing as being active in Destiny 2, but on both On & Fast it would still seem to show screen tear in the lower 1/3. Leaving it at Fast DID seem to help in Rocket League though!

But now in Baldur’s Gate 3 I get what looks like horizontal static lines across the whole screen. Currently have BG3 settings set to whatever the Nvidia app optimized it to along with the same NVCP settings (141 FPS, Fast). All of this is why I had held off of PC gaming for the longest time as I just never know what to try to fix any of these issues.

Any continued help would be appreciated!

[jorimt]

Continuing the conversation from the comments section of the G-Sync 101: Control Panel article.

The only thing I can further suggest, assuming G-SYNC is showing as engaged in your problem scenarios, and you're still seeing tearing with framerates within the refresh rate, is to use the in-game V-SYNC option instead of the NVCP option; as already mentioned in the article, there are rare instances where NVCP V-SYNC will not work where the in-game V-SYNC does (and visa-versa).

[TheGameV30]

Sounds good! I will give this a try. Thank you!