A frame counter can rise sharply after enabling frame generation while the controls still feel different from a game rendering every displayed frame conventionally. That is not necessarily a broken counter. Generated frames and the game’s underlying rendered frames represent different parts of the presentation process.
NVIDIA’s DLSS overview, for example, distinguishes frame generation from super resolution and other rendering features. Frame generation creates additional frames; it should not be interpreted as proof that every part of the game’s simulation and input processing now runs at the displayed frame rate. Implementations and supported hardware vary.
Make a comparison you can actually feel
- Choose a repeatable scene in the same game, with the same resolution and graphics settings.
- Observe performance with frame generation disabled. Note uneven movement or stutters before changing anything.
- Enable the supported feature, keeping other settings as consistent as the game allows.
- Compare camera motion, moving objects, interface edges and the response to deliberate control inputs.
Record the relevant latency-reduction setting as well. If the game changes several options automatically, write those changes down; otherwise you may attribute the whole difference to one switch. Compare the same route or action rather than a quiet menu against a busy combat scene.
A higher displayed rate can make movement look smoother, but that does not make every visual artifact or underlying hitch disappear. Equally, a screenshot cannot show the full experience of motion. Review the feature while playing, and use the game’s or manufacturer’s documentation to understand what its counter includes.
Keep the setting that suits the particular game and your priorities. A slower-paced title and a game built around rapid precise inputs may lead you to different choices. There is no need to treat the largest displayed number as the only successful outcome; clarity, consistency and comfortable control are useful results too.