Frame generation can add processing and presentation delay compared with the same rendering setup without it. Latency-reduction features such as NVIDIA Reflex can offset other delays, so the measured result depends on the comparison. A high generated-frame total does not provide the input response of the same number of newly simulated and rendered game frames.
Separate what looks smooth from what responds quickly
Visual smoothness describes how frequently and evenly the display updates. Input latency describes how long an action takes to appear. Interpolated frames can make motion look smoother without adding a fresh game simulation and input sample for every displayed frame.
That difference is why a game can report a large FPS total yet feel slower than a native game at the same displayed rate. Neither observation is contradictory. Evaluate the feature according to the activity: a scenic single-player experience and a fast competitive aiming task can place different value on smoothness and response.
Understand where latency reduction fits
NVIDIA Reflex reduces system latency by coordinating CPU and GPU work and limiting unnecessary queueing in supported games. It addresses delays in the broader pipeline; it does not transform generated frames into independent input-driven simulation frames.
When comparing results, keep Reflex state consistent where the game permits it. Frame generation plus Reflex may compare favourably with a poorly queued baseline that has Reflex off. That does not prove frame generation itself has negative cost. It shows why the complete settings and pipeline matter when interpreting a before-and-after latency claim.
For the documented reference, see NVIDIA’s explanation of system latency and Reflex.
Start with a healthy base rendering rate
A weak base frame rate limits how often the game can process and render new information. Generating additional views between those frames can improve presentation, but it cannot fully repair unresponsive simulation or severe stutter. First choose settings that provide acceptable control without interpolation.
Use upscaling or reduce expensive visual settings if that improves base performance. Avoid a universal minimum FPS rule: the acceptable threshold depends on the game and player. The practical test is whether the underlying game already feels responsive enough before you ask frame generation to make the motion smoother.
Compare the same scene with controlled settings
Keep resolution, reconstruction mode and other graphics options fixed. Compare frame generation off and on in a repeatable scene, and note any automatically changed latency setting. Use an appropriate latency measurement tool if available, while recognizing that FPS alone is not such a measurement.
For a practical feel test, repeat a familiar aiming or camera movement and watch for changes in response and consistency. Do not compare unrelated scenes or judge entirely from a video recording. A recording can show visual artifacts, but it cannot reproduce the viewer’s own physical input-to-display experience.
Check frame caps, display behaviour and artifacts
Refresh limits, synchronization, frame caps and the game’s presentation path can affect the result. Follow the title and driver’s supported configuration rather than copying a single global recipe. Keep the display refresh rate and variable-refresh arrangement documented when comparing.
Inspect fast camera movement, interface elements and object edges. Interpolation artifacts can make motion feel less clean even if measured latency is acceptable. Conversely, a visually stable result can still have an input response you dislike. Treat those as separate observations so you can change the relevant setting rather than chasing one all-purpose fix.
Choose according to the activity and your tolerance
For fast competitive play, prioritize a high stable base rendering rate and low latency. For slower or visually demanding games, the extra smoothness may be a worthwhile trade. There is no requirement to keep the feature enabled simply because your hardware supports it.
Save the configuration that feels best under your actual conditions. If a game update changes pacing or model behaviour, repeat the comparison. The useful conclusion is that frame generation has a different relationship to responsiveness than ordinary higher rendered FPS, and its value should be assessed with both motion quality and input delay in view.
Frequently asked questions
Can 120 generated FPS feel like 60 rendered FPS?
It can retain response characteristics tied to a much lower base rate, with additional pipeline effects. Displayed FPS alone does not determine input latency.
Does Reflex remove every frame-generation delay?
No. It reduces latency elsewhere in the supported pipeline, but does not make generated frames equivalent to new input-driven game updates.
Should I disable frame generation for competitive games?
Prioritize measured response and a stable base rate. Test the supported configuration; your preferred trade-off can differ from a slower single-player game.