Fleet Of The Damned

How to Actually Get Fleet Of The Damned Running Without Pain

Fleet Of The Damned is a massive Doom total conversion created by John Romero and his team. It ships with over 200 new maps, several custom IWADs, a new soundtrack, and enough extra WAD content to fill most storage drives. I've spent more time than I'd like managing this thing across different setups, so here's how you get it working without spending six hours fighting source ports. First, grab the official release from the id Software or Romero Games download page. You'll want the full package — it's roughly 800 MB to 1.2 GB depending on the build. Extract it somewhere permanent, not a temp folder. The structure matters because some maps reference paths relative to the base directory. The critical part nobody explains well: you need a source port that handles modern Doom WADs properly. PrBoom+ is the safest starting point for the bulk of the content, but if you're playing the newer Romero Hell Revealed maps, you'll want GZDoom for the enhanced rendering and ACS scripting support. Don't try to run everything through Chocolate Doom — it will choke on the extended header data and missing lump names. I learned that the hard way on a first attempt and spent an hour wondering why half the levels loaded as black screens.

Here's the workflow that actually works. Open GZDoom, go to the wad file browser, and load the main fleetoftthedamned.wad first. Then add the supporting patches in order — read the includes.txt file inside the archive, it tells you exactly which WADs to load and in what sequence. Skip that step and you'll get missing texture errors or maps that refuse to start. I keep a dedicated save folder per level set because the game doesn't manage its own saves cleanly across different custom IWADs. If you hit crashes on startup with the Demon Stairs area reimagined or the later Romero maps, check your graphics backend. OpenGL 2.1 works for most content. DirectX11 gives you better performance on modern cards but occasionally stutters on map transitions in the Eternity Engine-based builds. D3D9 is the fallback if neither of those cooperate.

What Actually Goes Wrong and How to Fix It

The most common issue I've seen people wrestle with is sound. Fleet Of The Damned uses a custom MIDI and sample pack that doesn't always route correctly through default port settings. If audio cuts out or plays at the wrong speed mid-level, go into your sound config and switch from Auto to either FluidSynth or Timidity. FluidSynth sounds significantly better too, assuming you have a decent soundfont loaded. I use the FluidR3_GM soundfont and haven't looked back. Another thing that trips people up: the game has multiple difficulty-based variant maps. Some levels duplicate with slightly different monster placements depending on where you select them from the menu. The menu itself is a custom HUD overlay built on top of the source port's menu system, and navigating it with a controller requires remapping in the key config file. The default settings assume keyboard input. I spent considerably more time stuck on the main menu than I care to admit before realizing I needed to assign controller bindings manually in config.cfg. Performance note: Fleet Of The Damned is heavier than vanilla Doom. Expect 20 to 40 percent lower framerates on identical hardware compared to standard Doom II. This is especially noticeable in the dense multiplayer arenas and the later Romero Hell Revealed zones. Lower your view radius or disable some visual effects if you're running anything older than a GTX 10-series card. It won't break the gameplay, just the ambient detail layers.

One edge case worth mentioning: if you're trying to play the bonus maps that ship with the E3 1997 Demon Stairs prototype data, they won't appear unless you enable the compatibility flag for pre-release Doomer engine behaviors. The maps use older sector flag conventions that modern source ports filter out by default. In GZDoom this is under Options Compatibility Pre-Release Mode. Toggle it on, reload the map, and they show up. I discovered this only after comparing my install against a colleague's working copy and noticing his map list was populated while mine was nearly empty. Took about twenty minutes of hunting to find the flag. There are trade-offs with this project that deserve a straight answer. The sheer volume of content means the QoL is inconsistent — some maps are meticulously crafted with secrets and pacing, others feel like rough prototypes that never got fully tuned. Collision detection in a handful of the verticality-focused Romero Hell areas can be finicky, and I've had players clip through floors in at least three maps. Not a dealbreaker but worth knowing before you commit. If you want a more polished experience with fewer rough edges, pairing Fleet Of The Damned with a quality-of-life mod pack like Boom compatibility patches and extended hitbox fixes helps a lot. The community has good optional patches floating around the Doom forums and the GitHub repos. For people who just want to start without reading the whole manual: extract the archive, install GZDoom latest stable, load the main WAD, add the patches from includes.txt, switch your sound backend to FluidSynth, toggle pre-release compatibility for the bonus maps, and you're in. Usually takes about ten minutes from download to first level if nothing goes sideways. The worst case is spending an afternoon tweaking config files, which happens when you're chasing a specific framerate target or trying to get multiplayer sync working on a custom netgame.

Bottom Line on Fleet Of The Damned

The project is genuinely impressive for what it attempts — a full modern Doom experience with hundreds of new maps from one of the genre's founders. It's not flawless, and the setup isn't instant, but once you have the right port and the WADs layered correctly it runs solidly. The early game maps from the Romero Hell Revealed series are where the quality peaks, and the multiplayer arena content holds up if you're patient with the configuration. Just don't expect it to boot and play like a typical commercial release out of the box. That's not what this is.