To ensure that DCS AOC Tools correctly extracts takeoff and landing information from a DCS World mission file, the mission editor must be configured with dedicated takeoff and landing waypoints.
If you do not want the aircraft's takeoff time to be the same as the waypoint 0 ETA (spawn time), set waypoint 0 to a parking position, such as Takeoff from Ramp, and use waypoint 1 as the actual takeoff waypoint.
TASKUNIT/1FW/ICAO:LLKA//
AMSNDAT/N/0121C/-/AAF/-/BARCAP/-/-/DEPLOC:LBNA/010715ZOCT/ARRLOC:LLKA/010815ZOCT//
When configured correctly, DCS AOC Tools identifies the takeoff and landing waypoints and includes them in the 6ROUTE section of the generated Air Tasking Order (ATO).
You can define the names of takeoff and landing waypoints using different naming conventions.
If the waypoint name is TAKEOFF or LANDING:
6ROUTE/PN/ROUTEPT/TYP/ATIME/TAS/ALT/1/NAME:TAKEOFF/-/210400ZJUN/-/-///5/NAME:LANDING/-/210540ZJUN/-/-//
If the waypoint name includes the DEP: or ARR: prefix followed by the corresponding ICAO code (for example, DEP:UG5X or ARR:UGKO):
6ROUTE
/PN/ROUTEPT/TYP/ATIME/TAS/ALT
/1/ICAO:UG5X/-/210400ZJUN/-/-//
/2/ICAO:UGKO/-/210421ZJUN/-/-//
Using the ICAO-based naming convention allows DCS AOC Tools to identify the departure and arrival airfields directly from the waypoint data extracted from the DCS World mission file.
