Match the reported symptom first
This guide covers a setting that appears enabled after restarting but does not deliver the expected performance benefit until reapplied. It does not diagnose a missing menu option, unsupported hardware or every low-FPS report. Record the GPU, driver and installed client build, then check whether the issue happens only after a restart. If performance is equally poor before and after, start with the broader settings guide.
Use a controlled before-and-after comparison
Editorial diagnostic: note your existing setting and test a stable scene after a fresh client launch. Reapply Frame Generation through the normal menu and compare the same scene. Keep resolution, upscaling choice, frame cap and graphics quality unchanged during this comparison. Record the result once, then repeat after another restart if you need to demonstrate the pattern. This procedure follows the reported symptom; it is not a guaranteed fix.
Why an FPS counter is only part of the result
Frame delivery, responsiveness and visual artifacts are separate experiences. A higher displayed count does not by itself demonstrate reduced input latency or better aim control. Use the same measurement method for each run and note whether the comparison includes menus or gameplay. Avoid combining results from different maps, server loads or capture settings into a claimed percentage improvement.
Restore a known state if the comparison is inconclusive
Return the setting to your original value and keep a record of what you changed. Do not stack launch flags, registry edits, modded DLLs and multiple driver changes into a single experiment. Those changes make it harder to tell which condition produced the result. If the setting is unavailable, verify the official game menu and supported hardware documentation rather than downloading an unofficial feature unlocker.
What to include in a useful report
State whether the menu displays Frame Generation as enabled on a fresh launch, whether reapplying it changes the result, and whether the behavior returns after the next restart. Include hardware and driver information plus a comparable capture if possible. The developer’s 1.6 target remains pending QA; recheck the release notes when a new patch is offered.
Frequently asked questions
Why does Frame Generation look enabled but not help?
That exact restart-related behavior is acknowledged by the developer. Reapplying the setting is part of the reported pattern; a 1.6 fix is still awaiting verification.
Is there a confirmed FPS gain for my GPU?
This guide has not benchmarked GPUs and makes no numerical FPS promise. Compare your own matched settings and scene.
Sources and verification
Sources are linked for independent checking. Dynamic figures are snapshots, not permanent values.