VRR (Variable Refresh Rate)
ℹ️ Reference
VRR (G-Sync / G-Sync Compatible, AMD FreeSync, VESA Adaptive-Sync, HDMI 2.1 VRR) – a technology that synchronizes the monitor's refresh rate with the game's frame rate. It is designed to eliminate the negative effects of V-Sync and provide a smooth, tear-free image with the lowest latency within its operating range. However, it is no cure for a game's stuttering problems.
Why is VRR not a replacement for V-Sync? This video explains
V-Sync (Vertical Sync Pulse / Vertical Synchronization) – a setting in the driver (NVCP / NVAPP) or the game itself. Put simply, V-Sync makes the system wait until the monitor has completely finished drawing the current frame. It is required for VRR to work correctly, since it eliminates tearing entirely by compensating for frametime variance.
NVCP / NVAPP – the NVIDIA Control Panel or the newer NVIDIA app.
Low Latency Mode – an NVIDIA driver setting, also known as LLM. When set to Ultra, it is also called ULLM/NULL (Nvidia Ultra Low Latency mode), referring to a zero-frame queue.
🟢 VRR on Nvidia
- Enable VRR (G-Sync / G-Sync Compatible, AMD FreeSync, VESA Adaptive-Sync, HDMI 2.1 VRR) on the monitor itself through its OSD menu.
-
Enabling VRR in the driver:
- If you use NVIDIA app (NVAPP): Go to System -> G-SYNC and Surround -> enable G-SYNC for FULLSCREEN MODE ONLY. Below, under Display Properties check “G-SYNC support: Enable G-SYNC settings...”.
- If you use the classic Control Panel (NVCP): Go to Set up G-SYNC -> enable G-SYNC and select FULLSCREEN MODE ONLY. Below, select the monitor and check Enable settings for the selected display model.
- In games WITH Reflex support: V-Sync ON (in-game) + Reflex ON. (If everything works correctly, the maximum FPS should be slightly below the monitor's refresh rate.)
- In games WITHOUT Reflex support: V-Sync ON (in-game / force it in NVCP/NVAPP if the game's implementation is poor) + Low Latency Mode: Ultra* (in the driver) OR inject Reflex through RTSS/Special K and cap FPS with a “fast” limiter using the formula
Refresh - (Refresh x Refresh / 3600) = FPS Cap**.
🔴 VRR on AMD
- Enable VRR (G-Sync / G-Sync Compatible, AMD FreeSync, VESA Adaptive-Sync, HDMI 2.1 VRR) on the monitor itself through its OSD menu.
- In the driver settings -> Display -> enable VRR/FreeSync (the name depends on the connection type/monitor technology).
- In games WITH AMD Anti-Lag 2 support: V-Sync ON (in-game) + AMD Anti-Lag 2 ON (in-game) + a fast FPS limiter using the formula
Refresh - (Refresh x Refresh / 3600) = FPS Cap**. - In games WITHOUT AMD Anti-Lag 2 support: V-Sync ON (in-game/Adrenalin) + AMD Anti-Lag ON (in the driver)* + a fast FPS limiter using the formula
Refresh - (Refresh x Refresh / 3600) = FPS Cap**.
⭐ Clarifications and Important Details
- * If you notice an unusual FPS drop or other signs of instability with Low Latency Mode: Ultra / Anti-Lag enabled, change it to Default. Ultra mode may also have poor compatibility with some DX12 games.
- ** This is not the exact formula for Reflex's dynamic limit with VRR + V-Sync, BUT it provides headroom to stay within the VRR range and removes jitter from any type of limiter. You do not have to use this exact cap, but the key is not to go above it.
⚠️ Important:
- Never change V-Sync, Low Latency Mode, or the FPS limiter in the GLOBAL driver profile (NVCP/NVAPP). Configure them individually for each game if needed.
- Also enable and tune the monitor's Overdrive setting (pixel response acceleration). Usually, Medium (a middle option in the list) is the best preset.
- Do not use the Discord overlay; it breaks VRR. Always check other overlays as well.
- The driver's G-SYNC indicator breaks VRR.
- Never enable Dynamic Refresh Rate in Windows Advanced display settings.
🔵 Optional: Disable Windows VRR
If you experience unusual VRR problems, try disabling this system setting, as it can cause them.
Path: System -> Display -> Graphics -> Advanced graphics settings -> Variable refresh rate — Off.
On Windows 11, this will not affect VRR operation in most games. However, disabling this setting prevents VRR from working when a windowed overlay or another window appears over the game, or when the game is out of focus. Disabling it is not recommended unless you have problems.
🚫 Without VRR
If your monitor has a poor VRR range of 48–75 Hz, you probably should not use VRR at all. Test it yourself.
Additional Information
1. Requirements for Correct VRR and V-Sync Operation
Correct VRR operation requires Independent Flip (I recommend reading more), V-Sync (SyncInterval=1/AllowTearing off) to compensate for frametime variation, and an FPS cap below the refresh rate to stay within the VRR range and avoid engaging ordinary V-Sync. It is also worth mentioning that VRR does not change the monitor's refresh rate: an incoming frame is scanned out at maximum speed. All VRR implementations are based on dynamic VBLANK.
There is no “incorrect” V-Sync implementation at the DXGI level, but game engines can add their own behavior, which can be GOOD (for example, disabling V-Sync during loading because of engine-specific behavior, or disabling the built-in limiter) or BAD (for example, using half-refresh-rate V-Sync).
VRR is compatible only with SyncInterval = 1; values 2–4 (half-refresh-rate V-Sync) are incompatible. Forcing V-Sync through the driver overrides the flag with SyncInterval=1, limiting configuration flexibility and potentially engaging VRR in applications it was not intended for.
In modern games (DX11+ / with Reflex), in-game V-Sync usually works correctly, and you do not need to change the driver settings. The game is better off knowing that V-Sync is in use: In-game V-Sync > NVAPP V-Sync
The driver's V-Sync setting controls only vertical synchronization itself, whereas many in-game “V-Sync” toggles control much more than frame synchronization. They can control everything from the in-game FPS limiter to the amount of resources loaded per frame (which affects loading times), and anything else the developers considered reasonable to tie to that particular setting.
2. Frame Rate Limiting (If the Game Has No Native Reflex)
In-game frame rate limiters CAN have lower latency, mainly because they can wait immediately before the simulation/input stage.
If the game's limiter is poor or absent, use “fast” limiters such as RTSS Async/Back Edge Sync/Reflex mode or Special K Low Latency.
The driver limiter (NVCP/NVAPP) has significant drawbacks: it is less predictable, depends on the placement of the NvAPI_D3D_Sleep call in Reflex games, and cannot be changed on the fly.
3. VRR Flicker on VA/OLED Monitors
Some flickering can be considered normal on these panel types; it depends on the specific monitor and occurs with large frametime variations.
Make sure G-SYNC is enabled for fullscreen mode only (rather than fullscreen and windowed modes), use the correct VRR settings above, and also try disabling Windows VRR.
4. DLSS FG and VRR + V-Sync
Nvidia Frame Generation is fully compatible with VRR + V-Sync. Support was added in driver version 526.98: “Introduces DLSS Frame Generation support for VSync when G-SYNC is enabled”.
However, many developers block in-game V-Sync when FG is enabled, so you need to enable it manually in the driver settings (NVCP or NVAPP).
Dynamic MFG is compatible with V-Sync starting with Streamline 2.14.1 (DLSSG DLL versions 310.9.0/310.9.1).
You can also try using Smooth Motion with V-Sync.
5. Reflex in Games and Low Latency Mode
The CPU, GPU, and display are three asynchronous parts of the frame queue. Most game latency arises because the CPU works ahead of the GPU.
Reflex is therefore designed to synchronize the CPU and GPU: it tells the CPU to prepare a new frame just before the GPU finishes rendering the current one. This means Reflex prevents one frame from queuing when the GPU cannot keep up with the CPU (a GPU bottleneck), significantly reducing latency. Everyone should enable it.
Reflex was also designed in part to force an FPS cap when VRR is active. When enabled together with VRR + V-Sync, Reflex should automatically cap FPS approximately according to the formula Refresh - (Refresh x Refresh / 3600) = FPS Cap. This provides a tear-free image and latency on a par with uncapped FPS.
Low Latency Mode: Ultra does exactly the same thing, but less efficiently; it was designed for older games where Nvidia Reflex was not yet available. It is also convenient because it does not conflict with Reflex when both are enabled, eliminating the possibility of user error.
6. What Reflex + Boost Actually Does
+Boost disables GPU frequency scaling (similar to “Prefer maximum performance” in 3D settings) and optionally applies aggressive optimization using latency markers via bUseMarkersToOptimize. The additional bUseMarkersToOptimize optimization reduces latency even more effectively, but requires competent implementation by the developer.
Unfortunately, many game developers do not know about this feature or encounter problems with it, and all their Boost mode does is prevent GPU frequency scaling (which is actually rarely useful for reducing latency). If you notice reduced FPS/stability, it is most likely a case of bUseMarkersToOptimize being used with a poor engine.
7. Specifically for CS2 Players
The Counter-Strike 2 community often discusses the claim that NVIDIA Reflex works incorrectly and should be disabled using the -noreflex parameter. This is only half true.
Reflex's implementation in CS2 is indeed imperfect and cannot always eliminate the entire one-frame delay, but it still gives better results than playing without it or using ULLM.
It is also important to understand that Reflex has no (or minimal) effect on frame pacing, so enabling it does not cause stutters. NVIDIA considers a 4% FPS drop with Low Latency On and a 7% drop with Low Latency + Boost normal.
8. Monitors with a G-Sync Module
Monitors with a G-Sync module also have Variable Overdrive, and LFC runs directly in the module.
9. Why Not Fullscreen and Windowed G-SYNC?
This mode was designed for the Windows 7–8 era, when windowed games mostly went through DWM. On modern Windows it is unnecessary, because a windowed game is INDEPENDENT and is always considered fullscreen when it is in Independent Flip (I recommend reading more). This mode changes DWM's own rendering rate and engages VRR in any application, which ALWAYS causes problems (Video about Windowed G-Sync)
This English translation was produced primarily using AI.