Install DCS Retribution correctly: choose the packaged release, extract it outside DCS World, set both DCS paths and fix common launch errors.
To install DCS Retribution, download its packaged Windows release, extract the entire archive to a writable folder outside both DCS World and Saved Games, then run the included Retribution executable. On first launch, confirm the DCS installation and Saved Games paths. Retribution is a separate campaign application, not a DCS mod.
DCS Retribution installation steps
Installation is a portable-application setup rather than a conventional DCS module installation.
- Install and run DCS World first. Let the simulator create its profile under Windows Saved Games, then close DCS.
- Download the packaged release. Select the ready-to-run Windows release supplied by the project. Do not choose a source-code archive unless you intend to build the application yourself; source packages generally lack the bundled executable and runtime files.
- Extract the complete archive. Use Windows Extract All or another archive tool, placing every file in a dedicated writable folder. Do not launch the executable from inside the compressed archive.
- Run the Retribution executable. Keep its supporting files and data directories beside it. If Windows displays a security warning, verify that the archive came from the official project release before allowing it; do not disable security software globally.
- Set the two DCS paths. In the first-run setup or application settings, select the DCS World installation root and your active DCS Saved Games folder. These are different locations and must not be pointed at the same directory.
- Create a campaign. Once the application has loaded its DCS data, start a campaign and generate the first mission. Use Retribution's launch option or open the generated mission from the location shown by the application.
Retribution should remain separate from DCS Liberation rather than being extracted over it. Our explanation of how Retribution differs from Liberation covers which application to choose and why their folders should not be merged.
Where should DCS Retribution be installed?
Install Retribution in its own writable folder, not under the DCS program directory and not inside Saved Games\DCS\Mods.
| Location | What it contains | How Retribution uses it |
|---|---|---|
| Retribution folder | The executable and bundled application data | Runs the campaign generator |
| DCS installation root | The simulator files and folders such as bin | Provides DCS aircraft, terrain and weapon data |
%USERPROFILE%\Saved Games\DCS | Your DCS profile, settings and missions | Receives or exposes generated campaign files |
Some installations still use DCS.openbeta as the Saved Games folder name. Select the folder your active DCS profile actually uses rather than renaming it. Steam changes the simulator's program location, but it does not move the DCS profile out of Windows Saved Games.
Aircraft and asset mods are a separate matter. Install those using the correct DCS Saved Games mod layout; putting the Retribution application there will not make it appear in DCS Module Manager.
How do I know the installation worked?
The installation is working when Retribution opens without missing-file errors, accepts both DCS paths, loads the available theatres and can generate a mission file.
Retribution does not add a normal module tile or desktop entry to DCS World. Its job is to manage the dynamic campaign outside the simulator and produce the mission that DCS runs.
Why won't DCS Retribution start?
Most launch failures come from downloading the wrong package, running it inside the archive or selecting the wrong DCS directory.
| Symptom | Likely cause | Fix |
|---|---|---|
| No usable executable | A source-code archive was downloaded | Replace it with the packaged Windows release |
| Missing DLL, resource or data error | Incomplete extraction or a quarantined file | Re-extract the complete verified archive to a fresh folder and check the security-software history |
| Application opens but cannot find maps or units | The Saved Games folder was selected as the DCS installation | Point the installation field at the main DCS World folder containing the simulator files |
| Mission cannot be written or found | Wrong Saved Games profile or restricted folder permissions | Select the active DCS or DCS.openbeta profile and use a writable Retribution folder |
| Retribution is configured correctly but DCS itself fails | The simulator installation may be damaged | Repair the DCS World installation, then recheck the paths |
If a generated mission reports missing aircraft or assets, the application installation may be fine; the selected campaign depends on content that your DCS setup does not provide. Choose a campaign matching your installed maps and required assets, or install its stated dependencies separately.
How should I update DCS Retribution?
Update Retribution by extracting the new packaged release into a fresh folder rather than overwriting the existing application or a Liberation directory.
Close Retribution first, back up campaign saves and keep the previous folder until the new build opens them successfully. Campaign-save compatibility can change between major releases, so follow the compatibility information supplied with that release instead of assuming every old campaign can be continued.