no more room in hell 2 stuck on loading screen
No More Room in Hell 2 Stuck on Loading Screen / Logging In — Fix
First separate a still-loading session from a map-loading crash: official 1.0 notes document a reconnect option after a map-loading crash, not a universal cure for every loading stall.
Advertisement
Direct answer
- Official 1.0 notes mention reconnect after a map-loading crash.
- A loading screen and a confirmed crash should not be diagnosed as the same issue.
- The PC release requires DirectX 12, so an undocumented DX11 launch flag is not included as a repair.
Identify the exact loading stage
| What you see | What it narrows down | Next check |
|---|---|---|
| The game stalls before reaching the main menu | This is a startup or login path, not a map-load recovery case. | Update and restart first; on PC, verify files and compare the system with the DirectX 12 requirements. |
| The game crashes while loading a map | This matches the specific Reconnect boundary documented for 1.0. | Reopen the game and use Reconnect when the active session offers it. |
| Solo loads but party matchmaking stalls | The current version, party state or service condition needs testing. | Match versions, rebuild the squad and check official service reports. |
| Only one map repeatedly stalls | The support report needs map-specific evidence. | Record the map, platform, party size, last visible screen and time before reporting it. |
Before you start
Record the platform, version 1.0.4.0, whether the game is still responsive, and whether the stall happens at login or map load.
Fix 1: Identify where loading stops
Login, lobby, map loading and a confirmed crash are different failure stages and should not be treated as one problem.
- Note the last visible screen or message and whether the game still responds to input.
- Give a still-responsive first load a short, measured wait; force-close only when it has clearly stopped progressing.
- Record whether the problem happens alone, only in a party or only on one map.
Fix 2: Update first and use Reconnect only when offered
Armageddon 1.0 added Reconnect specifically for a crash during map load, and later hotfixes fixed named crash and stability issues.
- Install the current 1.0.4.0 patch and restart the game and platform client.
- After a confirmed map-loading crash, reopen the game and use Reconnect if the live session offers it.
- Do not treat Reconnect as a repair for a login stall or a game that never reaches the menu.
Advertisement
Fix 3: Verify the installed game files on PC
Steam and Epic provide file verification as the supported check for incomplete or damaged local files.
- Steam: Library → NMRIH2 → Properties → Installed Files → Verify integrity of game files.
- Epic: Library → three dots beside NMRIH2 → Manage → Verify.
- Let verification finish, then test one launch before changing another variable.
Fix 4: Check the PC baseline and graphics driver
Steam lists DirectX 12 and 12 GB RAM as part of the minimum PC baseline, while the official launch issue post recommends current graphics drivers for reported hitching.
- Install pending Windows and graphics-driver updates, then restart the PC.
- Compare the machine with the current Steam minimum requirements and close memory-heavy background applications for one test.
- Keep the default DirectX 12 launch path while diagnosing; the current sources do not support forcing DX11.
Fix 5: Isolate party and service conditions
If solo loading succeeds but a party load stalls, test the current service, version and party state before changing files again.
- Confirm every party member uses the same current build.
- Check official channels for an active service incident, then disband and form one fresh squad.
- If the same stage still stalls, save the platform, map, party size, time and screenshot for support.
If it does not work
If the same stage repeatedly stalls, preserve the exact message and platform context for official support. Do not present cache deletion, firewall changes or reinstalling as verified fixes without a current official instruction.
Evidence boundary
The official notes support only the reconnect-after-map-loading-crash boundary; they do not publish a universal loading-screen repair path.
Advertisement