FIELD NOTE 18 / PC PERFORMANCE
Performance
and FPS.
Start with the checks the developer actually documents before copying an unverified settings preset.
Quick answer
Section titled “Quick answer”For NMRiH2 performance problems, first update the game and your graphics driver, then compare your PC with the official requirements. Compatible RTX 4000- and 5000-series cards can use the game’s DLSS 4.5 Frame Generation support. The developer specifically says the 1.0 work reduced the cost of gore, impact effects, audio, loading, shadows, lighting, model detail, and distance rendering—but no official source publishes one universal “best settings” preset.
Verification scope: Reviewed September 7, 2026. This is a source-backed diagnostic order, not a benchmark for every CPU, GPU, resolution, or map.
Run these checks in order
Section titled “Run these checks in order”- Install the latest game update so you have the current optimization and crash fixes.
- Update the GPU driver. The official launch-week report says some Nvidia hitching cases appeared to resolve after a driver update.
- Confirm the PC meets the official minimum target before treating low performance as a settings bug.
- On compatible RTX 4000- or 5000-series hardware, test the supported DLSS 4.5 and Frame Generation options.
- Reproduce the issue in the same map and combat situation before comparing changes.
- If the problem remains, report the map, hardware, driver, and reproduction steps through the official support route.
Changing several settings at once makes it impossible to know which adjustment mattered. Use the same scene, change one option at a time, and keep the result only if it improves the symptom you are measuring.
What 1.0 optimized
Section titled “What 1.0 optimized”| Area | Official 1.0 work |
|---|---|
| Upscaling | DLSS integration upgraded to 4.5; Frame Generation supported on RTX 4000 and 5000 series |
| Gore and VFX | Impact and gore rendering refactored to reduce performance cost during busy combat |
| Audio | Streaming, memory loading, compression, and sound prioritization revised |
| Long-session audio load | An object-loading issue that could increase simultaneous sounds was resolved for Armageddon |
| Console and low-end scaling | Shadows, lighting, model detail, and distance rendering adjusted; Xbox Series S work also benefited lower-end PCs |
These are engine-side changes already described by the developer. They are not instructions to disable every listed effect, and they do not establish that one graphics option is the bottleneck on every machine.
Official PC targets
Section titled “Official PC targets”The Steam listing requires Windows 10 64-bit, DirectX 12, broadband internet, and 35 GB of storage. The minimum target lists an Intel Core i5-6600 or AMD Ryzen 3 3100, 8 GB RAM, and a GTX 1650, RX 570, or Arc A380 for 1080p Low at 30 FPS. The recommended target lists an i5-12600K or Ryzen 5 5600X, 16 GB RAM, and an RTX 3060 Ti, RX 6750 XT, or Arc A770 for 1080p High at 60 FPS.
Use those targets as the first boundary. A minimum-spec PC is not promised the recommended 60 FPS target, and a recommended-spec PC is not promised the same result at a higher resolution or in every large combat encounter.
Symptom-to-check map
Section titled “Symptom-to-check map”| Symptom | First verified check |
|---|---|
| Nvidia hitching | Update the graphics driver, then retest the same scene |
| Low FPS on minimum hardware | Compare resolution and quality with the official 1080p Low / 30 FPS target |
| Heavy combat slowdown | Confirm the current build; 1.0 specifically changed gore and impact rendering |
| Performance worsens over time | Update to Armageddon or later; the developer documented an audio/object-loading fix |
| Lower-end PC struggles | Compare CPU, GPU, memory, and storage against the official table |
| Crash or repeatable map-specific problem | Check Known Issues, then submit a reproducible report |
What this page does not claim
Section titled “What this page does not claim”- A single “best FPS settings” list for every GPU.
- A guaranteed frame rate beyond the official 1080p target examples.
- That Frame Generation replaces meeting the base hardware requirements.
- That every hitch is caused by an outdated driver.
- Benchmark numbers gathered on hardware that this site did not test.
Sources
Section titled “Sources”| Source | Reliability | Used for |
|---|---|---|
| Road to 1.0: Optimization & Performance | Official | DLSS 4.5, VFX, audio, loading, and console optimization details. |
| Launch Week Known Issues & Hotfix Info | Official | Nvidia driver observation and launch performance status. |
| No More Room in Hell 2 on Steam | Official store | Current minimum and recommended system requirements. |