Performance Settings for No More Room in Hell 2

No More Room in Hell 2 is an Unreal Engine 5 eight-player horde game. Pretty foliage does not extract a Responder. A hitch during a shove, a scanner, or a helicopter door does. Armageddon 1.0 added DLSS 4.5 on compatible GeForce RTX cards and refactored impact and gore effects so dense fights cost less. This page is the practical settings pass that belongs next to System Requirements and Controls.

Console players still care: cross-play lobbies include PC friends who may be dropping frames you cannot see. If a teammate’s audio stutters every wave, ask them to read this before you queue Nightmare.

Official hardware baseline

Meet or beat the recommended PC spec before you chase cinematic presets. DirectX 12 and Easy Anti-Cheat are part of the install, not optional overlays you can “optimize away.” Storage type matters when maps stream hospital wings or flooded industrial yards. If you are under minimum RAM or on an integrated GPU, lower expectations and difficulty together—see Difficulty Modes.

1.0 also fixed several Low/Medium pop-in cases and a main-menu highlight bug on Low. If you play on Low, you are not “doing it wrong.” You are choosing survival.

DLSS 4.5 and upscalers

On supported RTX GPUs, enable DLSS 4.5 before you turn every cinematic slider to film. Quality or Balanced is the usual first stop; Ultra Performance is for emergency Survival holds on hardware that is already sweating. Frame Generation can feel wonderful in empty streets and dishonest in a speaker choke—test it on Flooded or a Power Plant finale, not in the menu courtyard.

If you do not have DLSS, use the in-game upscaler or a lower internal resolution before you disable shadows entirely. Shadows and fog sell the horror, but they are cheaper than a 200 ms hitch when a Prime grabs you.

Preset advice that actually helps

Start at High if you are on recommended hardware, then drop these first when waves hitch:

1. Effects / gore / decals — 1.0 already made impacts cheaper; still the first spike in a crowded door.
2. Shadows and volumetric fog — keep enough to read interiors; cut the rest.
3. Foliage and view distance on rural Lewiston approaches.
4. Reflections and anti-aliasing after upscaling is on.

Turn off unnecessary overlays (hardware monitoring skins, Discord full overlay, extra recording presets) for graded characters. Overlay hitches are indistinguishable from “the game is badly optimized” in a Discord argument.

VSync: prefer a frame-cap near your display refresh over raw unlimited frames that swing from 120 to 40. Consistency beats peaks when shove timing matters.

Mode-specific stress

Scenario hitch points are Critical interacts, plant interiors, and extract cinematics. Survival hitch points are speaker waves and supply-drop scrambles. Flooded’s water made confirmation of kills harder; it also stresses effects. If only Survival stutters, lower effects before you reinstall drivers.

Known 1.0 issues that can feel like performance problems: a short delay after picking up an item before you can use it; a rare ADS-plus-empty-mag lock that a grab resets. Those are gameplay bugs, not GPU settings. Check Patch Notes when a client update lands.

A 10-minute tune loop

1. Update GPU drivers after a major game patch.
2. Set a preset, enable DLSS if available, cap frames.
3. Run one Solo Mode walk through a dense interior.
4. Run one online Normal match—pubs add eight characters, ragdolls, and VoIP.
5. If hitching remains, drop effects and shadows one step, then stop. Do not spend an hour chasing 4K.

Share your preset in party chat so the squad knows whether you can hold a landing zone. Performance is part of Play with Friends etiquette: a beautiful slideshow is a wipe machine.

Stable frames keep melee honest, keep scanners completable, and keep extracts boardable. That is the only benchmark that matters in a permadeath co-op game.