No More Room in Hell 2 Performance Guide for Stable FPS

Start from the official PC targets

No More Room in Hell 2 is a DirectX 12 game with large spaces, dynamic hordes, lighting, gore, audio, and networked players competing for system resources. Begin with the published target closest to your hardware instead of selecting High immediately.

These are complete experience targets, not guarantees for every horde or background workload. Close heavy applications, allow shader compilation and asset loading to settle, then measure performance during combat. An empty room is too light to reveal the settings that fail during the final objective.

Install the game on an SSD where possible, keep adequate free space, and use a current stable graphics driver. Confirm that Windows selects the dedicated GPU on laptops. A system accidentally running the integrated GPU can show severe frame loss regardless of in-game settings.

Settings order for a stable frame rate

Change one group at a time, then repeat the same test. This produces a useful cause-and-effect result and prevents a large quality loss for a small gain.

1. Select Low on minimum-class hardware or High on recommended-class hardware.
2. Choose the vendor-supported upscaler and the official baseline mode.
3. Set a frame-rate cap your machine can hold during a horde.
4. Reduce shadows, lighting, effects, gore, foliage, model detail, and distance settings in that order when the GPU remains saturated.
5. Lower output resolution or use a more aggressive upscaling mode only after the scene settings are controlled.
6. Retest in a busy Objective or Survival encounter.

Shadows and lighting affect many objects at once, so they are strong first candidates for a GPU-limited machine. Effects and gore become expensive when combat fills the screen. Foliage, model detail, and distance rendering matter most across open sections of larger maps. The developers optimized all of these areas for 1.0 and removed the old Ultra option because it served cinematic capture rather than normal gameplay.

Avoid reducing every visibility setting to its minimum without testing. Clear silhouettes, stable motion, and readable attack animations support survival. A steady 45 or 60 FPS with consistent frame times is more useful than a higher average that collapses when a horde arrives.

Tune for the worst horde you expect, not the empty corridor where the benchmark begins.

DLSS, upscaling, and Frame Generation

Armageddon added DLSS 4.5 support. Start with Quality on recommended hardware at 1080p. Balanced or Performance can recover GPU headroom, though they render from a lower internal resolution and may soften fine detail.

RTX 4000 and RTX 5000 series cards can use Frame Generation. It can improve displayed smoothness when the base frame rate is already stable. It does not remove CPU stalls, network latency, or inconsistent simulation timing. If controls feel delayed, disable Frame Generation and compare the same area with a normal frame cap.

For cards without supported Frame Generation, focus on a stable base frame rate. Upscaling remains useful when GPU load is the limit, while scene-detail reductions are more relevant when crowded encounters overwhelm the processor.

Separate low FPS from network lag

Low FPS changes how the whole scene is rendered. Camera motion, menus, weapon animation, and local effects become uneven together. Network lag more often appears as delayed interactions, remote players or zombies snapping between positions, rubber-banding, or actions resolving late while camera movement remains smooth.

Use this diagnostic sequence:

1. Reproduce the slowdown in solo practice with the same map area and graphics settings.
2. Watch the frame-rate and frame-time graph while turning the camera and fighting.
3. Join an online match and compare local camera smoothness with remote movement and interaction delay.
4. Use a wired connection or stable 5 GHz or 6 GHz Wi-Fi for a second online test.
5. Stop downloads, cloud synchronization, and video streams during the comparison.

If solo performance also drops, adjust local rendering or background load. If solo remains smooth while online actors jump or inputs resolve late, investigate latency, packet loss, region, and connection stability. Lowering shadows will not repair a congested network path.

Broadband internet appears in both published PC profiles because the main game is online. A stable frame rate and a stable connection are separate requirements, and both must hold during an extraction.

CPU, GPU, and memory troubleshooting

A GPU-limited system usually improves when resolution scale, upscaling mode, shadows, or effects are reduced. A CPU-limited system may show low GPU utilization while frame time spikes during large hordes. In that case, reduce distance, model detail, foliage, and effect density, close CPU-heavy software, and cap the frame rate.

Four-gigabyte GPUs sit at the minimum target. Keep texture and scene settings conservative to avoid memory pressure. Repeated stutter after entering new areas can indicate asset or shader activity, while continuous stutter during every crowded fight points toward sustained CPU, GPU, or memory limits.

Restart the game after major driver or graphics changes. Verify local files through Steam when performance changes suddenly after an interrupted update. Keep a record of the preset, upscaling mode, cap, resolution, and the test scene so each comparison remains meaningful.

Recommended starting profiles

Treat these as starting points. Resolution, cooling, background processes, laptop power modes, and the chosen map can move the result significantly.

Frequently Asked Questions

What frame rate does the minimum specification target?

What does the recommended specification target?

Should I use Frame Generation?

Why does the game stutter mainly during hordes?

Can lower graphics settings fix rubber-banding?