vigo68 / dcs-mission

Demonstration mission for the mission creation tools (see https://github.com/VEAF/VEAF-Mission-Creation-Tools)

VEAF demonstration mission

Abstract

This is a barebones mission to demonstrate the VEAF Mission Creation Tools framework Please read the documentation for further information on the concept.

TODO Link to the documentation - in progress

This mission uses the normalizer and radio preset editor tools, also found in the VEAF Mission Creation Tools framework

Templates

Empty templates with preset triggers on different terrains can be found in the templates folder.

Prerequisites

• 7za from the 7-Zip Extra: standalone console version
• lua from Lua for Windows
• npm from NodeJS

Note: it is easier to install all the prerequisites with Chocolatey

We created some scripts that you can use (in the folder named setup) :

1. run install-chocolatey.cmd in an elevated shell (as administrator)
2. restart your shell (important)
3. run install-requirements.cmd in an elevated shell (as administrator)
4. (optional) run install-optionals.cmd in an elevated shell (as administrator)

Workflow

Build the mission

Simply execute build in order to build the mission.

For developpement purpose you way want to use some special flags.

• VERBOSE_LOG_FLAG if set to "true", will create a mission with tracing enabled (meaning that, when run, it will log a lot of details in the dcs log file); defaults to "false"
• LUA_SCRIPTS_DEBUG_PARAMETER can be set to "-debug" or "-trace" (or not set) ; this will be passed to the lua helper scripts (e.g. veafMissionRadioPresetsEditor and veafMissionNormalizer); defaults to not set
• SECURITY_DISABLED_FLAG if set to "true", will create a mission with security disabled (meaning that no password is ever required); defaults to "false"
• MISSION_FILE_SUFFIX (a string) will be appended to the mission file name to make it more unique; defaults to the current iso date
• SEVENZIP (a string) points to the 7za executable; defaults "7za", so it needs to be in the path
• LUA (a string) points to the lua executable; defaults "lua", so it needs to be in the path

Edit the mission

Use the DCS World Mission Editor to make whatever change you want to the .miz file you built in the previous step

Test the mission

Within DCS World; you can have a look in the dcs.log file (specially if you set the VERBOSE_LOG_FLAG to "true")

Save your changes

Copy the built .miz file (the one you edited and tested) to the root directory of this project and run extract. This will :

• explode the mission into its constituing files
• copy these files in the src folder
• clean up everything that is not needed (i.e. lua scripts)
• normalize the mission files so they can easily be compared with the previous version (see the normalizer tool)
• commit the changes to your source control system