3.10 Feature: Chained Missions
Posted: Wed Jul 08, 2009 8:05 pm
A new feature introduced is chained missions. This feature allows the user to set up a series of missions so that the mission's craft will be assigned to the next on mission completion.
This is accomplished with a secondary mission field of each mission. The secondary mission can be set to any other mission. When mission A has mission B set as its secondary mission, mission A craft will be assigned to B on completion of A. The definition of 'complete' will vary from mission type to mission type. Some mission parameters will also impact what 'complete' is. i.e. Setting a transit mission to select reference points sequentially will have the transit mission complete when the last craft has reached the last reference point.
One use of this feature is to create an attack profile for a strike. An initial egress transit mission can take strike craft to a safe rally point (avoiding any SAM sites), strike the target, regress to the rally point, and then RTB. A demonstration of this scenario will be provided.
This is accomplished with a secondary mission field of each mission. The secondary mission can be set to any other mission. When mission A has mission B set as its secondary mission, mission A craft will be assigned to B on completion of A. The definition of 'complete' will vary from mission type to mission type. Some mission parameters will also impact what 'complete' is. i.e. Setting a transit mission to select reference points sequentially will have the transit mission complete when the last craft has reached the last reference point.
One use of this feature is to create an attack profile for a strike. An initial egress transit mission can take strike craft to a safe rally point (avoiding any SAM sites), strike the target, regress to the rally point, and then RTB. A demonstration of this scenario will be provided.