Official press-kit image © Team17 / Expression GamesChoose features by constraint
- TSR and DLSS: the official performance page presents both as image-reconstruction options. The correct choice depends on supported hardware, output resolution and the result you measure.
- Frame Generation: officially supported on compatible NVIDIA GeForce RTX 40-series cards and newer. The same source warns that a low base frame rate can increase input latency.
- Hardware Lumen: described as an optional, high-end lighting workload that needs GPU headroom. It is not a default recommendation for every PC.
Measure one variable
- 1Baseline
Same sceneSame routeSame duration
- 2Change one
Change one settingKeep everything else exactly the same
- 3Repeat
Same sceneSame routeSame duration
- 4Keep / undo
Keep if betterUndo if worse
Equal in importance
| Build | Resolution | Setting changed | Observation | Result |
|---|---|---|---|---|
If a setting does not persist after relaunch
The current official launch thread has acknowledged settings-persistence problems, but it does not authorise deleting configuration files, editing .ini files, changing permissions or disabling cloud saves. Keep the recovery check reversible:
- Record the platform, current build and the original setting.
- Change one setting and apply it through the visible game interface.
- Relaunch once and compare the displayed value with the record.
- If it reverted, restore the original value and stop stacking local changes.
- Recheck the current official thread, then report the platform, build, original value, tested value and relaunch result.
When to stop tuning
Keep a change only when the repeated run is meaningfully better for your stated goal and does not introduce a worse tradeoff. Undo unclear results. After a game, driver or operating-system update, start a new row rather than averaging unlike builds.