Beta
Known limitations
The honest list. Updated as the beta runs.
Current limitations (0.9.x beta)
- Terrain analysis is bare-earth. Elevation, line-of-sight, and viewshed calculations use terrain shape only — buildings and trees are not included. A ridge will mask a radar correctly; a city block won't.
- One writer at a time. If you edit the same mission in both dcs-mcp and the DCS Mission Editor, save from one before touching it with the other. Simultaneous edits can lose changes.
- Mission Editor data from DCS 2.9.28's new DTC features (F/A-18 HARM/GPS partitions, F-16 VRP/VIP, ME map drawings in the cartridge) may not survive a dcs-mcp save if the mission was previously saved in the 2.9.28 editor. We're confirming exact behavior; until then, treat DTC-configured missions as Mission-Editor-only.
- Theater coverage: Caucasus ships built-in; Syria, Kola, Iraq, Persian Gulf, Sinai, Mariana Islands, Nevada, Germany Cold War, Afghanistan, and the Falklands are available through the built-in Terrain Manager. The Channel, Normandy, and Marianas WWII are not supported during the beta; support beyond that is to be determined.
- Newest DCS content lags slightly. Modules and weapons added in the most recent DCS updates (e.g. the F-14B(U) and this month's new weapon entries) can't be placed by dcs-mcp yet. Missions containing them load and save safely — dcs-mcp preserves what it doesn't recognize.
- Kola parking accuracy: DCS 2.9.28 resized parking at several Kola airfields; occasionally DCS may relocate an aircraft dcs-mcp parked. Cosmetic; fix comes with our next data update.
- SmartScreen warnings: early beta builds are new binaries without download reputation; expect the More info → Run anyway dance for now.
- First start after install or terrain changes is slow. One-time cost per change; subsequent starts are fast.
Found something not on this list? #mcp-issues on Discord — that's what the beta is for.