Install Through the Inferno missions in DCS World, launch them solo or in multiplayer, use the F10 menu, and fix missing maps, slots or scripts.
To install Through the Inferno in DCS World, extract the downloaded package but leave the .miz file intact, then place that file in your active Saved Games\DCS\Missions folder. Start the single-player build from My Missions, or load the multiplayer build when hosting a server, and select a flyable slot.
How do you install a Through the Inferno .miz file?
Through the Inferno (TTI) is distributed as a DCS mission rather than a conventional mod with its own installer. For a normal release, its scripts and mission data are already contained inside the .miz file.
- Choose the correct package. Use the mission made for the DCS terrain you own and install any asset packs or dependencies identified in its accompanying documentation. If separate single-player and multiplayer versions are supplied, choose the one matching how you intend to play.
- Extract only the outer archive. If the download is a ZIP, 7z or similar package, unpack it until you can see one or more files ending in
.miz. Do not extract the.mizitself; DCS mission files are internally archive-based, so extraction utilities may misleadingly treat them as ordinary ZIP files. - Find the active DCS profile. The normal location is
C:\Users\<Windows user>\Saved Games\DCS\Missions. An older installation may useSaved Games\DCS.openbeta\Missions. Steam and standalone DCS both use Saved Games for user missions. - Copy the mission into place. You may create a subfolder such as
Missions\Through the Inferno. Copy the actual.mizfile there, not a folder that contains another identically named folder. - Keep the DCS installation directory clean. TTI missions do not normally belong under
Program Files,CoreModsorMods. Our notes on placing custom DCS mission files correctly cover the same folder-nesting trap in more detail.
Where several Saved Games profiles exist, the active one is usually the folder whose Logs\dcs.log file changes when you run DCS. Dedicated Server installations use their own Saved Games profile, so place the mission in that server profile rather than the desktop client's folder.
How do you start TTI in single-player or multiplayer?
Launch the single-player file through DCS's Mission screen; use a server for a multiplayer or client-slot build.
| How you want to play | What to do |
|---|---|
| Solo with an SP build | Open Mission, select My Missions, browse to the TTI folder and load the .miz. |
| Solo with only an MP build | Create a private local server, add the .miz to its mission list and join one of its client slots. |
| Host friends | Create a multiplayer server, add the TTI mission, set an optional password and start it. Everyone needs the mission's terrain. |
| Join an existing TTI server | Join through the multiplayer server browser. You do not need to install its .miz locally, but you do need the required terrain and the aircraft module for your chosen slot. |
For firewall, server-list and hosting details, use our practical DCS multiplayer connection steps. A terrain is fixed when the mission is built and cannot be substituted; our guide to installing and checking DCS terrains explains how to confirm that the required map is available.
How do you play a Through the Inferno mission?
Choose your coalition and an aircraft slot you own, read the briefing, then use the radio menu's F10 Other section to control or request dynamically generated tasks.
- Select an appropriate slot: TTI packages may contain cold-start, hot-start, runway or airborne slots. A slot using an unowned aircraft module cannot be flown.
- Check the briefing: It identifies mission-specific rules, frequencies, target areas and any package-specific controls.
- Open the communications menu: The general menu commonly uses
\, but full-fidelity aircraft may require the relevant radio push-to-talk binding. Open F10 Other and select the available TTI mission or support options. - Follow mission messages: Task details, coordinates and status updates are normally displayed after a mission is requested or generated. The F10 map key and the F10 Other radio-menu entry are separate controls.
- Expect a sandbox session: A plain
.mizinstallation does not create campaign-style save data. Persistent state, statistics or progress exist only when that particular release or server has been configured to provide them.
The exact F10 entries differ between TTI releases and server configurations. Some hosts restrict map icons, external views, aircraft or support functions, so the server briefing takes precedence over generic instructions.
Why is Through the Inferno not working?
Most TTI installation failures come from an extracted .miz, the wrong Saved Games profile, a missing terrain or launching a client-slot mission as an ordinary single-player mission.
| Problem | Likely fix |
|---|---|
| The mission does not appear | Confirm that the file itself ends in .miz, remove unnecessary nested folders and check that it is under the active DCS Saved Games profile. |
| DCS reports that a terrain is required | Install or enable the exact map used by that TTI build. Updating DCS does not grant ownership of paid terrain. |
| There is no selectable aircraft | Choose a slot for a module you own. If every slot is marked Client, run the mission through a local multiplayer server or obtain its single-player variant. |
| F10 Other is absent | Wait for the mission scripts to initialise, verify the correct radio binding and try a fresh, unmodified copy of the mission. |
| Script errors appear after editing | Restore the original .miz. Do not unpack and rebuild it manually, and do not alter DCS security-related Lua files unless that release explicitly requires an optional feature. |
| Friends cannot join | Check server connectivity first, then confirm that every player has the required terrain. Clients receive the mission automatically but not missing maps or aircraft modules. |
Can you customise a TTI mission?
You can edit a copy in the DCS Mission Editor, but TTI relies on linked triggers, zones, flags and embedded scripts that are easy to disrupt.
Keep the untouched download as a backup, save customised versions under a new filename and avoid deleting unfamiliar triggers or zones. Our explanation of .miz files, client slots and missing assets is the useful starting point before changing aircraft slots, weather or mission options. When replacing TTI with a newer release, move deliberate edits across carefully rather than assuming that overwriting the old file will preserve them.