How Data Is Changing the Way Players and Fans Watch Esports
Esports viewing has changed a lot. Fans no longer watch only for big kills, clutch rounds, final scores, or highlight…
I have G-Sync working on my 165 Hz monitor, confirmed with your test. Guides disagree on whether V-Sync should be on or off. I sometimes see a tear line near the top in fast games. What's the right setup?
A widely used setup is G-Sync on, V-Sync on in the NVIDIA control panel, V-Sync off in games, and a frame rate cap a few frames below the refresh rate. The cap keeps you inside the variable refresh range; driver V-Sync catches occasional frame time spikes that would otherwise tear.
The disagreement comes from mixing up two different V-Sync behaviours. With variable refresh active, the setup most people settle on is:
G-Sync or FreeSync on, confirmed working.
A frame rate cap a few frames below your refresh rate, for example around 160 on a 165 Hz monitor, set in the driver or in the game. This keeps the frame rate inside the variable refresh range, so the monitor follows every frame and plain V-Sync never takes over with its extra lag.
V-Sync on in the graphics driver's control panel, and off in the game. Even with a cap, individual frames occasionally arrive slightly early. Without V-Sync, those moments can produce a tear, often near the top or bottom of the screen, which matches what you see. Driver V-Sync, while you stay inside the variable refresh range, smooths those moments without adding the large lag that classic V-Sync does above the refresh rate.
Some competitive players prefer V-Sync off entirely and accept occasional tearing for the absolute lowest lag. Both are valid; the capped setup is the best balance for most.
Run our G-Sync and FreeSync test and your games afterwards to confirm smooth, tear-free motion.
Tested on: Applies to G-Sync and FreeSync setups on Windows 11 with NVIDIA and AMD graphics. Settings locations vary by driver version.
Checked by Lucas Rocha on . How we verify answers
Embedded Systems And Firmware Programmer at Gamepad Tester
Alistair is an embedded systems programmer. He writes custom firmware for third-party PC gamepads and builds input-parsing test rigs on microcontrollers such as the Arduino and Raspberry Pi Pico, which means he can see what a controller is sending at the wire level rather than guessing from what the operating system reports. That is usually the fastest way to settle whether a fault is in the pad, the driver or the browser. On Gamepad Tester he answers the firmware and driver questions, including the ones where an update has broken a working controller.
Each answer is written by the specialist who owns that part of the hardware, tested on a real controller, and checked by a second team member. How we verify answers
Answers are free general guidance from the Gamepad Tester Team and the community. Opening a controller or replacing a thumbstick module can void your warranty, so check the maker's support or warranty first. Battery and soldering work carries a real risk of damage or injury.
Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.
Esports viewing has changed a lot. Fans no longer watch only for big kills, clutch rounds, final scores, or highlight…
If you have ever watched a video that looked choppy, played a game that felt sluggish, or noticed that scrolling on…
Content creators, marketers, and businesses are finding creating images and videos more and more effortless via AI. As…
The newest replies from players and the Gamepad Tester Team.