Configure the display’s refresh rate and GSync operation first, then use the synchronization and target controls supported by your installed Dynamic MFG path. Do not add a copied external-cap preset before confirming those basics.
For the separate synchronization trade-off, read how VSync affects Dynamic MFG input lag.
This is a verification workflow, not one universal checkbox combination. Game integration, display mode and software version can change which settings apply.
Verify the display connection and refresh rate
Confirm that the GPU output, cable, monitor input and resolution support the intended refresh rate. A monitor’s maximum advertised rate may depend on its input or display mode.
Set the desired rate in Windows and check the monitor’s on-screen status. A high-refresh panel configured at a lower rate changes the target the rest of the setup should pursue.
If the monitor has an Adaptive-Sync or VRR setting, enable it as its manual requires. Some monitor modes can disable VRR or alter available settings.
Do not assume every USB-C dock, adapter or hybrid laptop path exposes the same GSync capabilities as a direct supported GPU connection.
Enable GSync for the mode you actually use
Use the NVIDIA driver’s available GSync configuration for the connected display. Select the appropriate supported fullscreen or windowed coverage for how you run the game.
Confirm operation with the driver or monitor’s supported indicator. A saved setting is weaker evidence than a status indication during the actual game.
Keep the window mode consistent while testing. Moving between borderless and exclusive fullscreen can change the path and make comparisons harder to interpret.
If GSync options are absent, check the display connection, monitor support and platform routing before reinstalling software. A missing capability cannot always be restored with a checkbox.
Identify the active Dynamic integration
Check the game build, driver and any NVIDIA app override used to enable the requested generation mode. A generic DLSS setting does not prove that Dynamic MFG is active.
NVIDIA’s current Dynamic integration documentation describes target and VSync behaviour as well as its preferred Reflex-aware limiting path. Those details matter more than an old universal preset.
Support for Dynamic with synchronization and limiters changed after launch, but newer SDK support is not proof that every game has adopted it. Use the actual title’s supported setup.
If support remains unclear, compare a documented fixed generation mode rather than forcing several settings and assuming any visible output proves correctness.
Choose supported target and sync controls
Start with the native Dynamic target appropriate to the documented path. In a current VSync-enabled integration, target handling can differ from a manually entered Dynamic target.
Do not assume a custom FPS value will override every other presentation control. Check the observed result and the title’s documentation.
Avoid stacking in-game, driver and RTSS caps at the outset. Where a supported path already manages the ceiling, an additional cap may be redundant or act on the wrong stage.
Our frame target guide helps distinguish a useful sustainable target from a base-rate restriction that accidentally worsens response.
Check operation in real gameplay
Use a route with an easy area, a heavy area and a transition. Watch for tearing, regularity of motion and how aiming or steering responds.
Record rendered and output rates separately when available. A final output figure near the display rate does not by itself establish a strong underlying game cadence.
Check the supported VRR indicator while the game runs. A monitor refresh counter can help verify activity, but it is not a complete latency measurement.
Repeat the route after restoring the initial configuration. Keep any practical difference in target or sync behaviour in the notes instead of attributing all changes to GSync alone.
Troubleshoot one symptom at a time
For tearing, verify the active VRR and synchronization path rather than simply lowering random graphics settings. For delayed controls, inspect base performance and limiter interactions as separate possibilities.
For hitches only with an external cap, restore native pacing and repeat. The sister site’s RTSS pacing guide explains why the limiter and its monitoring overlay should be isolated.
For one affected title, preserve settings that work elsewhere. Record the exact build and reproduction before changing global profiles or reinstalling the driver.
If the monitor is outside its useful VRR range, behaviour can differ from the same setup within range. Check the display’s documented capabilities rather than promising one universal outcome.
Keep a known working profile
Once motion and response are acceptable, save a short record of the game, display mode, target, sync controls and versions. Retest after a relevant update if the behaviour changes.
My preference is the smallest supported configuration that works. Correct GSync operation plus a coherent Dynamic path is more useful than a long preset containing controls whose roles you cannot verify.