Mistfall Hunter DLSS, FSR, TSR, and frame generation test.
Use this page when Mistfall Hunter shows high average FPS but still feels uneven after changing DLSS, FSR, TSR, native resolution, frame generation, or NVIDIA Smooth Motion. The goal is not to chase the largest number; the goal is to find the mode with the best frame pacing in the same route.
The safe test order
- Restart the game so the first route is consistent.
- Use the same short route with one camera turn, one traversal transition, and one combat or effect-heavy moment.
- Turn ray tracing off if it is enabled.
- Turn frame generation, NVIDIA Smooth Motion, or similar interpolation off while diagnosing.
- Pick fullscreen or borderless and keep it fixed for the upscaler test.
- Cap FPS to a stable value such as 60 or 120 for diagnosis.
- Run native, DLSS, FSR, and TSR one at a time in the same route.
- Write down motion feel, camera-turn smoothness, first traversal hitch, and combat spikes.
Upscaler result matrix
| Mode | What to watch | Decision |
|---|---|---|
| Native | Baseline motion feel and input consistency. | Use this to judge whether upscalers improve pacing or only the FPS number. |
| DLSS | Average FPS, camera turns, traversal hitches, UI clarity. | Keep it only if motion feels smoother than native in the same route. |
| FSR | Same route, same cap, same fullscreen mode. | Use when it gives steadier motion or fewer spikes than other modes. |
| TSR | Traversal into new areas and combat-effect spikes. | Consider it if DLSS raises FPS but does not fix stutter feel. |
| Frame generation | Motion smoothness after the base preset is already stable. | Test last. Do not use it to hide a bad base frame-time graph. |
Why frame generation should be tested last
Frame generation can make motion look smoother after a stable base is found, but it can also hide pacing spikes while you are diagnosing. If camera turns, traversal, or combat still feel uneven, disable it and fix the base path first.
Symptom-based reads
| Symptom | Likely test | What it means |
|---|---|---|
| High FPS but camera turns feel rough | Cap FPS and compare native vs one upscaler. | Average FPS improved, but frame pacing may still be unstable. |
| Stutter when entering a new area | Repeat the same route twice after a restart. | Shader, cache, or streaming behavior may be involved. |
| Frame generation looks smooth but input feels odd | Disable generation and test the base preset. | The generated result may be masking a weak base frame rate. |
| Only one upscaler stutters badly | Keep fullscreen, cap, and route fixed while comparing modes. | The mode interaction may matter more than general graphics quality. |
Copyable community reply
If someone asks what to test, use a short version instead of posting a wall of settings:
Need a longer test record? Use the Mistfall Hunter performance checklist and copy the result after one route.
Source context
This page was created for the community pattern around high FPS but uneven motion, especially comments about upscaler changes, frame generation, fullscreen mode, VSync, ray tracing, and repeated-route stutter. Treat this as launch-prep guidance until the live build, drivers, and patches settle.
FAQ
Should I use DLSS, FSR, TSR, or native?
Use the mode that feels most stable in the same route. A higher average FPS number is not enough if camera turns or traversal still hitch.
Should I turn frame generation on?
Only after finding a stable base preset. Turn it off while diagnosing, then test it as one separate variable.
Does this replace the stuttering fix page?
No. This page focuses on upscalers and frame generation. Use the stuttering fix checklist for the full display, VSync, cache, overlay, laptop, and long-session path.
Is this final launch advice?
No. It is pre-launch diagnostic guidance. Update the result after the final build and driver behavior are verified.