Quick answer

On a system near the official minimum target, begin with Hardware Lumen off and use TSR or supported DLSS to trade internal resolution for performance. Test Frame Generation only after the base frame rate is stable; it can add latency when the underlying rate is too low.

Start with the official hardware target

| Target | CPU and memory | GPU | Official 1080p baseline | |---|---|---|---| | Minimum | i5-10600K or Ryzen 5 3600X, 16 GB | RTX 2060 Super or RX 6600 XT | 60 FPS target with TSR 71% or DLSS Ultra Performance | | Recommended | i5-12600K or Ryzen 5 7600X, 16 GB | RTX 3060 Ti or RX 6900 XT | 60 FPS target with TSR 100% High or DLSS Balanced |

The store lists Windows 10 64-bit for minimum, Windows 11 64-bit for recommended and 30 GB of storage. These are published targets, not measurements from HLLV Wiki.

Choose TSR or DLSS deliberately

TSR and DLSS render internally at a lower resolution and reconstruct the final image. That trade can improve performance at the cost of some image detail or stability, depending on the mode and hardware. Begin with the official baseline closest to your system rather than selecting the most aggressive upscaling option automatically.

Change one setting, replay the same scene and observe frame pacing as well as the average rate. A higher number that feels uneven is not necessarily a better result.

Treat Frame Generation as an extra step

Supported RTX 40-series and newer GPUs can use Frame Generation. The developer warns that enabling it while the base frame rate is too low may increase input latency. First reach a stable underlying result, then enable the feature and compare both responsiveness and smoothness.

Frame Generation does not replace work on CPU, network or memory bottlenecks. The performance update says optimization spans rendering, game systems, networking and memory, so a graphics toggle cannot explain every hitch.

Disable Hardware Lumen before cutting everything

Hardware Lumen is an optional visual upgrade for high-end systems and adds significant GPU load. Switch it off before reducing every other quality setting. That preserves a clearer test: you remove one known expensive feature and then evaluate the result.

If more adjustment is needed, Shadows, Reflections, Foliage and FX are sensible third-party test candidates. Dexerto also suggests Fullscreen, VSync off, Motion Blur off and Film Grain off. Those values are not developer presets and are presented here only as a starting checklist.

A conservative testing order

  1. Match the official minimum or recommended TSR/DLSS baseline.
  2. Turn Hardware Lumen off.
  3. Stabilize the base frame rate before testing Frame Generation.
  4. Lower Shadows, Reflections, Foliage and FX one category at a time.
  5. Record the same map, scene, resolution and frame-rate measurement for every comparison.

AMD FSR 4.1 was described in launch information as a later update, so this page does not treat it as a current release setting. It also makes no claim that a listed change adds a fixed number of frames on every PC.