Start with the published requirement target
The existing PC Requirements page records the published minimum/recommended hardware. SteamDB currently records Windows, partial controller support and the retail release, but it is not a benchmark source.
Build a repeatable baseline
- Choose native or intended resolution and record display mode.
- Use one checkpoint with a repeatable camera path.
- Record frame rate and frame-time behavior before changing anything.
- Change one visible in-game option.
- Repeat the same path twice and keep the change only if the result repeats.
Prioritize readability
In a swarm shooter, consistent frame pacing and clear target silhouettes matter more than an unsupported “Ultra is always best” rule. Preserve effects needed to read hazards unless your own repeatable test shows they are the bottleneck.
Menu FPS is a separate test
One Steam thread reports very low menu performance while other commenters report acceptable gameplay. Record menu and mission behavior separately so a menu symptom is not presented as a whole-game benchmark.
DLSS and upscaling
The sources checked for this page do not establish the available upscalers in every storefront/build. Use what the current in-game menu actually displays and record the build date; do not follow a guide that invents an option.

Evidence used
SteamDB structured store record · conflicting Steam performance discussion · Patch 1 platform/performance fixes
Community reports describe individual experiences and demand. They do not prove that every player, platform or mission has the same result.