Best Helldivers 2 Settings on the Steam Machine
Helldivers 2 is GPU and CPU heavy in chaotic 4-player drops. Tune the Steam Machine for stable, dip-resistant frame-time instead of peak fps.
Set Helldivers 2 up for the worst moments, not the calm ones. In a quiet menu or a solo patrol almost any config will look fine on the Steam Machine. The fight that matters is a full 4-player drop with a bug breach or bot drop on screen: dozens of enemies, stratagem explosions, smoke, and fire all at once. That's where the RX 7600-class GPU and the 8 GB VRAM ceiling get squeezed, and where your CPU has to track every ragdoll and projectile. Tune for that and the rest of the game runs comfortably.
A quick honesty note: SteamFPS does not yet have a measured, curated Steam Machine verdict for Helldivers 2. The game is SteamOS-compatible via Proton, and the advice below is derived from its known demands plus the Machine's hardware profile. Treat every framerate description here as estimated / qualitative. Measured numbers will follow once we've benched it, and we'll link them from /games.
Start here: the target
Helldivers 2 is a shooter, so your aim and your dodge timing live and die on frame-time consistency, not your average fps. A run that sits at a rock-steady 50 feels far better to play than one that averages 65 but slams to 30 every time a stratagem lands. Your goal on the Steam Machine is a framerate that holds its floor during chaos.
Realistic, estimated target: 1080p, a tuned High-ish preset, with FSR set to Quality, aiming for a stable mid-range framerate that doesn't collapse in breaches. Native 4K is not the goal here, and neither is a max-settings average you can't sustain.
The recommended baseline
- Set resolution to 1080p on the Steam Machine's display output. If you're on a 1440p or 4K TV, let FSR upscale (next section) rather than rendering native.
- Start from the Native / High preset, then apply the cuts below — don't run the Ultra/max preset.
- Cap your framerate to a number you can actually hold in a breach (e.g. an estimated 40 or 50), and enable V-Sync or your TV's VRR if it has it. A held cap beats a number that spikes and dips.
- Turn the in-game framerate/frame-time overlay on for one session and go pick a fight. Watch the floor, not the peak.
What to cut (in priority order)
These are the settings that cost the most during exactly the moments that matter — heavy particle and post-processing loads — so they're the first to trim:
- Render / Resolution Scale — the single biggest lever. Drop it before you touch anything cosmetic; lowering internal resolution buys you headroom everywhere. This is also what FSR effectively manages, so set it via FSR rather than the raw slider.
- Particle Quality — go Medium. Helldivers 2's explosions, fire, and stratagem effects are the main GPU spike during a breach. This is your highest-value cosmetic cut.
- Cloud Quality — Low or Medium. Volumetric clouds are expensive and you rarely look at the sky in a firefight.
- Screen-Space stuff — Screen-Space Global Illumination, Screen-Space Reflections, and Screen-Space Ambient Occlusion. Set GI and reflections Low/Off, AO Low. These are quietly heavy and barely visible mid-fight.
- Ambient Occlusion — drop to Low; the visual difference is small, the cost is not.
- Bloom / Sharpness / Motion Blur — turn Motion Blur off in a shooter (clarity and target tracking), tune bloom to taste; these are mostly free but motion blur hurts readability.
Leave Texture Quality as high as you can without crowding the 8 GB VRAM ceiling — textures are mostly a memory cost, not a frame-time cost, and they do the most for how the game looks. If you see stutter or texture pop-in during long missions, that's your VRAM warning: step textures down one notch.
FSR: use it, but pick the right mode
FSR is your friend on this hardware. It renders the game at a lower internal resolution and upscales, which directly relieves the GPU during particle-heavy chaos.
- On a 1080p display, use FSR Quality. It's the best balance of clarity and headroom and you'll barely notice the upscale in motion.
- On a 1440p or 4K TV, lean on FSR harder (Quality → Balanced) rather than rendering native — native 4K is not a realistic target for this game on the Machine.
- Avoid the most aggressive FSR modes (Performance/Ultra Performance) unless you're desperate; Helldivers 2's fine UI text and thin enemy outlines get soft, which hurts target acquisition.
- Prefer FSR over dropping the raw render-scale slider — the upscaler reconstructs detail the flat slider just throws away.
Why frame-time stability beats peak fps
A shooter punishes inconsistency. When the framerate lurches from 60 to 30 the instant a breach pops, your camera stutters at the exact moment you need to dodge a charger or place a precise stratagem. A lower but steadier framerate keeps your inputs predictable and your aim honest.
That's the whole logic behind the cuts above: every one of them targets the chaotic-moment spikes, not the calm baseline. You're trading a few fps in quiet rooms — fps you didn't need — for a floor that holds when four players, a bug breach, and a 500kg eagle all happen at once. On the Steam Machine, with its fixed GPU and tight VRAM budget, that trade is almost always worth it.
Once you've found a cap that holds, leave it. Resist the urge to chase a higher average; the held floor is the number that actually feels good in the drop.
Frequently asked
In calm moments, very likely — but the honest question is whether it holds 60 during a full 4-player breach, and that's much harder given the game's particle and CPU load. We don't yet have measured Steam Machine numbers, so treat 60 as an aspiration in chaos, not a promise. A held 40–50 cap will often feel better than a 60 that collapses. Measured figures will follow on /games.
Use FSR Quality at 1080p. The internal-resolution drop gives you real GPU headroom during explosions, and at Quality mode the image stays sharp enough that you won't notice in motion. Native 1080p looks marginally crisper in screenshots but gives up the breach-time stability that actually matters in a shooter.
Render/resolution scale (managed via FSR) first, then Particle Quality. Particles — the explosions, fire, and stratagem effects — are the dominant GPU spike during the exact moments your framerate dips, so dropping them to Medium directly defends your floor. Screen-space effects and cloud quality are the next-best cuts.
Both, and that's why this game is hard to keep stable. The GPU handles the particle and post-processing load, but a chaotic 4-player drop also makes the CPU track dozens of enemies, ragdolls, and projectiles at once. The Steam Machine's Zen 4 6-core part is capable, but CPU-bound spikes are real — another reason a sustainable capped framerate beats chasing a high average.