title: "No More Room in Hell 2 Known Issues Tips & Strategies" description: "Fix known issues tips & strategies in No More Room in Hell 2 with our comprehensive troubleshooting guide. Solutions for common errors, crashes, and." keywords: ["NMRiH2", "No More Room in Hell 2", "fix", "error", "crash", "bug", "issue", "problem", "known", "issues"] date: "2026-08-16" lastModified: "2026-08-16" category: troubleshooting tags: bugs, errors, crashes, performance, workarounds, patch notes updated: 2025-06-01 version: Early Access (0.7.x)
Known Issues
No More Room in Hell 2 (NMRiH2) is a cooperative zombie survival game developed by Torn Banner Studios, currently in Early Access. As with any Early Access title, players may encounter a variety of bugs, performance issues, and compatibility problems. This article documents known issues acknowledged by developers, community-reported problems, and workarounds to improve your experience. It will be updated as patches release and community findings emerge.
Note on Severity Ratings: Severity is rated Critical (game-breaking or progress-blocking), High (severely impacts gameplay), Medium (noticeable but playable), and Low (cosmetic or minor). Status reflects the developer's public acknowledgment and whether a permanent fix has shipped.
Developer-Acknowledged Issues
The following issues have been publicly acknowledged by Torn Banner Studios on official forums, Steam Community posts, or developer livestreams. They are actively being investigated or have a known fix under development.
| Issue | Severity | Workaround | Status |
|---|---|---|---|
| Client-side crash after several hours of play (memory leak related) | High | Restart game every 2–3 hours; lower texture settings | Open – Monitoring |
| Server browser fails to list all populated servers | Medium | Refresh server list multiple times; use Steam server browser as backup | Open – Monitoring |
| VOIP audio dropping or recipients hearing static/garbled voice | Medium | Exit and rejoin party voice channel; disable auto mic volume in audio settings | Open – Monitoring |
| Character experience not saving if the game closes improperly | High | Always return to main menu before closing; verify progression after restart | Open – Workaround Available |
| Zombie AI pathfinding failure near stairwells and loading zones | Medium | Lead zombies to open areas; avoid funneling them into doorways | Open – Under Investigation |
| Save game corruption when dying (respawn screen soft-lock) | Critical | Force-quit and rejoin the server; relaunch the game if spawn fails | Fixed in 0.5.2 (reported ongoing in niche cases) |
Key Developer Response: In official patch notes for 0.4.0, Torn Banner stated: "We are prioritizing stability and performance fixes over new content in this Early Access phase. Please continue to report issues with detailed reproduction steps." Several fixes from that statement have since shipped; see Issues Fixed in Recent Patches below.
Platform-Specific Issues
NMRiH2 runs on the Unreal Engine 5 fork used by Torn Banner, which behaves differently across Windows versions. The development team primarily tests on Windows 10 and Windows 11 builds-in-progress; this has led to several platform-specific discrepancies.
Windows 10 vs. Windows 11
| Issue | Severity | Workaround | Status |
|---|---|---|---|
| Windows 10: Occasional invisible collision frames causing player to get "stuck in air" | Medium | Jump repeatedly to break free; toggle prone/stand; if persistent, relog | Fixed in 0.6.0 |
| Windows 11 (24H2+) only: Unexpected texture popping when Ray Tracing (RT) is enabled | Low | Disable RT shadows; set global illumination to SSGI instead | Open – Confirmed by Devs |
| Windows 10: Mouse input latency spikes during mass zombie hordes (100+ entities) | Medium | Lower "Maximum Crowd Density" to Medium; disable V-Sync | Open – Under Investigation |
| Windows 11 (23H2 and earlier): Audio crackling in 5.1/7.1 surround setups | Low | Switch to Stereo in Windows audio settings; lower in-game audio channels | Fixed in 0.5.4 |
Steam Deck / Linux
The game is not officially verified for Steam Deck, but community testing has produced reliable findings:
| Issue | Severity | Workaround | Status |
|---|---|---|---|
Proton 9.0-1: Crash on first launch unless -nomovie is appended to launch options | Critical | Add launch option -nomovie; force Proton 9.0-4 or newer | Open – Community Workaround |
| Deck: FPS drops below 30 during cooperative play | Medium | Set Steam Deck's TDP to 10W+; lower internal resolution to 800p | Open – Community Workaround |
| Deck: Save data not syncing with Windows after cross-progression | Medium | Manually copy NoMoreRoomInHell2/Saved/SaveGames folder to console and vice versa | Open – Community Workaround |
Note: Torn Banner has not yet announced official Steam Deck support. Expect further deviations until they do.
Hardware Compatibility Issues
Despite being an Early Access title, NMRiH2 has relatively broad hardware support. However, certain configurations trigger unique bugs.
NVIDIA Graphics Cards
| Issue | Severity | Workaround | Status |
|---|---|---|---|
| NVIDIA driver 552.44+: Black flickering on RTX 30-series cards | Medium | Roll back to 546.65; or enable "Debug Mode" in NVIDIA Control Panel | Fixed in 0.6.2 (driver bug workaround included) |
| DLSS 3 Frame Generation causing ghosting on RTX 40-series | Low | Use DLSS Quality without Frame Generation, or switch to TSR | Open – By Design? |
AMD Graphics Cards
| Issue | Severity | Workaround | Status |
|---|---|---|---|
| AMD FSR 2.2 creating intense shimmer at distance | Medium | Use Low FSR sharpness (or 0%) | Open – Monitoring |
| RX 6000 series: Crash when transitioning to darker areas (bug in radiance cache) | High | Update driver to Adrenalin 24.8.1+; disable dynamic shadows | Fixed in 0.5.8 |
CPUs and RAM
| Issue | Severity | Workaround | Status |
|---|---|---|---|
| 16 GB RAM: occasional hitching when streaming high-res textures | Low | Reduce texture pool to High (from Epic) | Open – Workaround Available |
| AMD Ryzen 7xxx/9xxx with memory EXPO enabled: random crash with "LowLevelFatalError" | High | Disable EXPO in BIOS; manually set RAM speed to rated non-EXPO frequency | Unconfirmed – Community Report |
Issues Fixed in Recent Patches
The following issues have been resolved in recent patches (as of this article's update). If you still experience them, ensure your game is fully updated and consider verifying game files (Steam → Right-click NMRiH2 → Properties → Installed Files → Verify Integrity).
| Version | Fix Description | Original Severity |
|---|---|---|
| 0.7.0 | Resolved server-side lag spikes when multiple doors are opened simultaneously | High |
| 0.6.3 | Fixed crash when using the Spawn Protection syrette while sprinting | Critical |
| 0.6.2 | Addressed NVIDIA driver mismatch causing black flickering pop-in | Medium |
| 0.6.1 | Server browser now fully populates after two refreshes | Medium |
| 0.6.0 | Windows 10 player stuck in mid-air collision bug fixed | Medium |
| 0.5.8 | AMD RX 6000 crashing in dark zones resolved | High |
| 0.5.4 | Surround audio crackling resolved | Low |
| 0.5.2 | Death/respawn soft-lock resolved | Critical |
| 0.5.0 | Memory leak reduced by 60% via pre-culling changes | High |
Community-Reported Issues and Workarounds
Community repositories and the NMRiH2 Discord server have surfaced issues not yet formally acknowledged by the developers. These are gathered from player reports and may be inconsistent; use caution with workarounds.
| Issue | Severity | Workaround | Status |
|---|---|---|---|
| Zombie ragdolls occasionally fly horizontally across the map at high speed | Low | None (cosmetic) – report with clip | Frequently Enjoyed |
| Items requiring two-handed carry (e.g., gas cans) despawn when dropped near doors | High | Place items at least 3 meters from doors; use the "drop" key instead of throwing | Open – Community Workaround |
| Friendly-fire warning remains on screen after the round ends | Low | Restart round; or enter/exit menu once | Open – Community Workaround |
| Pickaxe hitbox registering on the second swing instead of the first | Medium | "Swing-and-hold" trick: hold attack until the full animation finishes before clicking again | Open – Community Workaround |
| Party leader's ready-up status not syncing for other members | Medium | Everyone ready-up individually; if stuck, re-invite party | Open – Community Report |
| Host migration to a player with worse connection causes rubber-banding | Medium | In the in-game server vote, prefer hosts with low ping | Open – Community Workaround |
| Painkiller audio loop continuing after being revived | Low | Re-open your inventory and close it; if persistent, rejoin voice chat | Open – Community Workaround |
| Zombie spawns too close to the extraction point on "Fresno Road" | Medium | Use flare grenades to redirect horde; delay extraction until second wave | Open – Balance Discussion |
Stability Tip: Several community members report that disabling the Steam Overlay reduces the frequency of random stutters on Windows 10. Try it if you experience halting gameplay (Steam → Settings → In-Game → uncheck Enable Steam Overlay).
Mod Compatibility Issues
NMRiH2 currently has limited official mod support; the game relies on Unreal Engine's content bundles. Tools are not yet available for the public, so modding remains unofficial community patching.
| Issue | Severity | Workaround | Status |
|---|---|---|---|
| Loading a custom texture mod after a patch causes "Blueprint mismatch" errors | High | Reinstall the mod after every game patch; incompatible mods may render heads invisible | Open – Community Workaround |
| Mods that override audio packages cause crashes at mission end | Medium | Remove audio-affecting mods; use a mod manager to disable and re-enable per patch | Open – Community Report |
| "Skinned Mutator" mods (cosmetic reskins) increase VRAM usage by ~1GB | Low | Lower texture pool to compensate; alternatively, remove all skins | Open – Community Workaround |
| Server-side mods trigger "Connection Lost" when joining from a standard client | Critical | Do not join modded servers unless you have identical mod files in Mods folder | Open – By Design |
Official Stance: Torn Banner Studios states that "modding support is planned but not yet implemented" in the Early Access roadmap. Any unofficial modifications are used at your own risk and may lead to account or matchmaking restrictions in the future.
How to Report New Bugs Properly
Bug reports greatly help developers reproduce and fix issues. A well-written report follows the R.U.C.D. format (Repro, Utility, Context, Details):
- Reproduction Steps: Provide a numbered list of actions to trigger the bug.
- Utility Information: Hardware (CPU, GPU, RAM, OS version, driver), game build (visible on main menu bottom-left), and whether you're on a dedicated server or listening server.
- Context: Was this in solo mode, co-op, or online multiplayer? Which map and game mode?
- Details: Include screenshots, video clips, or a console log (if available).
Where to Report
- Official Discord: https://discord.gg/nmrih2 →
#bug-reportchannel. Pin the report and do not spam react. - Steam Community Hub: Search for existing thread before creating a new one; respond to existing threads with your reproduction steps.
- In-Game Report: Press F9 to take a screenshot and open the report window automatically. This brings up a pre-filled form with system information.
- Email Support: support@tornbanner.com — use only for critical gameplay-breaking issues.
Bug Report Information to Include
| Field | Example | Why It Matters |
|---|---|---|
| Short bug title | "Crash to desktop when using Syrette on downed teammate" | Quick scanning |
| Build version | 0.7.0 | Confirm if it's already patched |
| OS | Windows 11 23H2 | Platform-specific |
| GPU + driver | RTX 3080, driver 560.81 | Narrow hardware-related crashes |
| Server type | Dedicated / Listen / Single-player | Affects netcode bugs |
| Steps to reproduce | 1. Equip Syrette. 2. Walk toward downed teammate. 3. Press E. Repro rate: 100% | Enables fix confirmation |
| Crash log/console | Paste console output in a code block or upload to pastebin | Developer trace |
| Video clip | Length < 60 seconds, highlight the bug | Visual confirmation |
Pro-tip: Prior to sending logs, set the game to use debug logging: right-click NMRiH2 → Properties → Launch options → add -log. This will generate a Logs folder under C:\Users\<YourUser>\AppData\Local\NoMoreRoomInHell2\Saved\Logs.
General Troubleshooting Checklist
Before submitting a bug report, try the following checklist; it resolves a substantial number of issues:
- Verify game files (Steam → Properties → Installed Files → Verify Integrity).
- Update graphics drivers to the latest stable version.
- Disable third-party overlays (Steam Overlay, Discord Overlay).
- Disable Ray Tracing (if enabled) and set Global Illumination to SSGI.
- Lower "Maximum Crowd Density" to Medium and "Texture Pool" to High.
- Close background applications that use more than 4 GB RAM (e.g., Chrome) if you have 16 GB total memory.
- Move the game from a HDD to an SSD if you are experiencing loading-time crashes.
- Reset the in-game key bindings if buttons become unresponsive in menus.
Final Thoughts
No More Room in Hell 2 is a work-in-progress, and the frequency of bugs will decrease as Torn Banner Studios develops the game toward a full release. The majority of current issues are non-critical and easily worked around. For the most up-to-date information, check the official Discord announcements channel and the game's forums after each patch.
Remember that every bug report matters — the community thrives when players submit clear, concise reproductions. If this article resolves your issue, consider editing it to mark the bug as "Resolved" for future players, or add your own workaround to the community table.
Stay together, stay quiet, and watch your back.