Developer Ops
Introduction
As developers we don't need to operate aircraft or other vehicles to get things done or undone (destructed) in the Missions. All of the events in DCS can be programmed. This part of the guide concentrates on modifying, altering, expanding and improving the simulation. Or incorporating DCS in a Distributed Simulation Environment. Below you'll find an abbreviated sum up of the available tooling for developers and / or modders 🛠.
the DCS Mission Editor (M.E.)
- Check examples by Iain Christie (Its not you its M.E.) and others
- M.E. uses Lua scripting (compare VR Forces)
scripting
DCS scripting is accomplished using LUA, a widespread scripting language. A few very active modders have added some useful basic scripts:
These scripts enable the modder to enrich missions to a very high degree with patterns of life and other automated actions and outcomes.
mods
- examine Community Mods design and file content
- Standard Flight Model (SFM) vs. other flight models (EFM, AFM, PFM),
- DCS (Wags) explanation thereof,
- try our own Mod: e.g. UAV X-47B for Loyal Wingman?
- a beautiful example: BAAS SK60B Mod uses an EFM and is ready in time for the 2022 Holiday Season!.
hacking the game
- multiplayer games and missions,
- campaigns or even dynamic campaigns, where the next missions depend on the results of the previous,
- dedicated DCS server (on our own SBL server?)
tools
- Wireshark?
- other tooling
- hacking thereof?
- Tacview
possible experiments
- emulate TDL?
- linking different platform (simulations) information and interaction through simulated Tactical Data Link technology
- incorporating our other tools or sims like our MQ9 simulation,
- Loyal Wingman concept research
| MQ9 Reaper | Reaper Operators |
|---|---|
 |
 |
🚩 Mist or comparable tools are no mods but must be activated through DO SCRIPT FILE trigger actions at mission start; programmed in the M.E.