More about the mission system

I'm not going to go into great detail here because that is what the SDK is for, and it will provide everything you need to build a mission.

What I will do is offer some examples of triggers and actions we may use in a mission.

We use triggers to fire off actions which result in something happening in the world. One such trigger would be a timer. A timer can be started when the mission launches or can be activated by another action. It can count up or down and start and stop at a preset value. When the timer reaches a specific value it can fire an action or several actions. One or more of those actions may be to activate or deactivate other triggers.

Another trigger that we use a lot is a proximity trigger. In this case you define a 3D area in the world which when entered and/or exited will trigger an action. Another popular trigger is a property trigger which will fire an action when a simulation state or combination of states is reached (such as altitude, speed, attitude, etc). You can also check properties upon entering or exiting an area or filter for certain AI objects and use that criteria to determine if an action should be fired.

The actions are many and varied. The most common actions are to activate or deactivate objects (triggers, AI, scenery, animation, etc), play voice over dialog or sound effects, initiate aircraft system failures, define success or failure, and there are many more.

I hope this gets ideas flowing and when the SDK comes out you can be building missions in no time. When I am cleared to do so, I will release some screenshots of the mission editor we are using and plan to release in the SDK.