No More Room in Hell 2 System Requirements (1.0)

No More Room in Hell 2 asks for a Core i5-6600 or Ryzen 3 1200, 12 GB of RAM, a 4 GB card like the GTX 1650 or RX 570, and 35 GB of free space at minimum. The recommended sheet moves that to an i7-10700K or Ryzen 5 5500GT, 16 GB and an RTX 2070 or RX 5700 XT — and even then, Torn Banner Studios only promises 1080p at 60Hz with upscaling switched on. That last detail is the part almost nobody quotes, and it changes how you should read the whole table.

Official PC system requirements

The store sheet covers Windows only — there are no published macOS or Linux requirements. Note also that four of the eight rows are identical across both tiers: OS, DirectX, storage and network never move. Moving from minimum to recommended is purely a CPU, RAM and GPU upgrade.

What the Super Sampling note actually means

This is the line most sites strip out when they copy the table, and it is the most useful thing on the sheet.

Two things follow from that. First, hitting the minimum spec buys you 30fps at a sub-1080p render resolution — that is the floor the developers were willing to sign off on, not a comfortable experience. In a co-op zombie shooter where a missed swing costs you a permadeath character, 30fps is a real disadvantage.

Second, for a 2026 release the recommended tier is conservative — plenty of games this year quote their recommended spec at 1440p or at a high refresh rate. NMRIH2 quotes 1080p at 60Hz with the upscaler on. If you play at 1440p, at 4K, or on a 144Hz monitor, there is no official spec covering you, and anyone claiming to know what an RTX 2070 does at 1440p here is guessing.

As for which upscaler: the 1.0 patch notes confirm DLSS 4.5, with Frame Generation on RTX 40 and 50 series cards. The store sheet only says "Super Sampling" without naming what AMD, Intel or older NVIDIA cards fall back to, and Torn Banner has not published that mapping. Don't take a guess from a third-party page as fact.

Why 12 GB of RAM is the line to watch

Most co-op shooters still list 8 GB as their minimum. NMRIH2 lists 12 GB, which is a genuinely high floor — and 12 GB is an awkward number to actually own, since dual-channel kits are usually 8 or 16 GB. In practice the minimum tier means a 16 GB machine for most people, and an 8 GB PC is not "close enough" to try.

The launch build backs this up. Torn Banner's own hotfix notes flag a memory problem tied to heavily customized Responders, and the Hotfix #2 plan (week of August 24) explicitly lists memory optimization aimed at low-end machines and Xbox Series S. Memory pressure is a known weak point of this build, not a theoretical concern.

Ignore third-party requirement tables

The tells are easy to spot: an outdated table shows Windows 7 instead of Windows 10, 8 GB instead of 12/16 GB, 25 or 30 GB instead of 35 GB, or a recommended GPU from the GTX 900 era. Others copy the CPU and RAM correctly but drop the DirectX 12 line, the broadband line, and both Super Sampling notes — the parts that actually matter. Some still label the game Early Access at its old $19.49 price, a week after 1.0 shipped. None of them publish FPS benchmarks for NMRIH2 either, so their can-I-run-it verdicts are arithmetic on a table they got wrong.

You meet the spec and it still stutters

Being above the recommended tier does not guarantee a clean run in this build, and Torn Banner has acknowledged as much. Work through the officially confirmed causes before you start tweaking settings:

• Crashes tied to cosmetics. Torn Banner traced a memory issue to heavily customized Responders and advised players to avoid outfits with logos and patterns until the fix lands. If you are crashing rather than stuttering, strip your character back to plain clothing and retest.
• Performance sliding downhill over a long run. 1.0 shipped a fix for audio objects accumulating across a match and dragging framerate down, which Torn Banner said was worst on backtracking-heavy maps like Lewiston and Hospital. If a run feels fine for ten minutes and terrible at thirty, confirm you are patched rather than blaming your GPU.
• GeForce NOW is not a workaround. Cloud streaming was still under investigation as of launch week, with users unable to get past the terms-of-service screen. If your PC is under spec, streaming is not currently a reliable escape hatch.
• Frame Generation is a real lever on RTX 40/50. The 1.0 notes confirm it, and the recommended sheet never accounts for it.

Beyond that we're not going to invent a settings checklist. The graphics menu options — FOV, HDR, frame cap, borderless — aren't documented anywhere official we could verify, and guessing would put us in the same bucket as the aggregators above.

Steam Deck, consoles and handhelds

Per the same launch-week post, Steam Deck is rated Playable, not Verified, while Steam Machine was certified Verified. That gap is not really about raw performance — controller handling has been the long-running complaint here, and inventory management with a gamepad is central to how the game plays. Torn Banner patched a Steam Input bug just before 1.0 and says full controller support now works across configurations, but if you plan to play handheld, test that inside your refund window.

For PS5 and Xbox Series X|S there are no published requirements — consoles are fixed hardware, so there is nothing to check. The one official statement worth knowing is that Xbox Series S is the console optimization baseline, and Torn Banner says that work also benefits low-end PCs. Also useful: our 1.0 and console release rundown, whether the game is worth buying right now, and the mod support page on what the move to Unreal Engine 5 means for the old NMRIH toolchain.

System requirements FAQ