Help going simple plight plan please

[BlacleyCole]

I think I might be able to designat waypoints and as/alt and choose where it is a fly by or fly thru point or start on ramp etc or do a landing. But that’s about my limits right now I would like to use those or at least some of the wpts as triggers also to generate messages verify if the ac is on course and or speed That’s the next thing I would like to do then I would like to assign a ai lead or wingman and have it do messages at specific times and others when the no ai ac is not within limits for alt, crs or speed. If you would like to tutor me on the me please respond.

[SnowTiger]

I am certainly not the one to tutor anyone on mission scripting but I have created a couple simple missions.

 

What you need to take a look at in the DCS World Manual is "Triggers".

 

In your case, you create the WP's and then create Triggers with Actions at the WP's or along the Paths to WP's. The size or area of Triggers can be set (in case a pilot is not flying directly along a Path).

 

The AI stuff I haven't dealt with. And messages is a whole new ball game if you wish to have Voices. However, Triggers can be used for Text Message that show on the screen at specific locations and/ OR Times.

 

Hope this helps.

[feefifofum]

One of the buttons on the left side will allow you to create a "trigger zone."

You will place the zone by clicking on the map, then name it and define the radius. You can click and drag it where needed.

 

One of the other buttons will read "set rules for trigger", it looks like a switch in a circuit diagram

Use this to define rules where something happens. The trigger menu is divided into 3 sections: type, conditions, and triggered actions.

 

Click "new" in the type section to create a new trigger. Select the trigger type from the drop down menu. ONCE type will execute the action one time when the conditions are met. SWITCHED CONDITION will execute the action every time the conditions are met.

CONTINUOUS ACTION will execute the action once per second as long as the conditions are met.

MISSION START will execute the action a single time before AI or anything else is initialized when the player unpauses the mission. I.E. clicks the "Fly" button.

 

You can also associate a particular game engine event i.e. ON SHOT, ON DESTROY, etc. You almost always want to leave this set to NO EVENT, so I won't go into further details here.

 

For your example:

Create a new trigger zone by selecting the create trigger zone button from the left hand toolbar and click the map at your waypoint 1. Set the desired radius and name it something easily recognizable.

 

Open the "set rules for trigger" menu by clicking the button on the left hand toolbar.

In the type column click "new." Leave the default "1 ONCE" and "NO EVENT" items as they are and name the trigger "WP1 heading check"

 

With the "WP1 heading check" trigger selected, click "NEW" in the conditions menu. Select "UNIT'S HEADING WITHIN LIMITS" then choose your helicopter from the UNIT drop down menu, and define the heading limits. Click "NEW" under conditions again and add a second condition, "UNIT INSIDE ZONE" and select the helo and your waypoint 1 zone from the drop down menus.

 

Click NEW in the "triggered actions" column and select MESSAGE TO ALL from the drop down menu. Type the desired message and select the time it will display on the screen.

 

All together now:

Type:

1 ONCE (WP1 heading check, NO EVENT)

Conditions:

UNIT'S HEADING INSIDE LIMITS (Helo1, 120, 130)

UNIT INSIDE ZONE (Helo1, Waypoint1)

Triggered Actions:

MESSAGE TO ALL ("You are flying the correct heading", 10 )

 

I encourage you to explore the other conditions and triggered actions on your own. It's pretty intuitive once you understand the basic concept which hopefully you now do. Create simple missions to test different triggers and build an understanding before trying anything overly complex.

 

The other major concept in the DCS editor is flags. A flag is both a boolean (true/false) and numeric variable with a 5 digit identifying number assigned to it. All flags start with a value of 0, or false. You can turn a flag on for it to become true (a value of 1) or increase its value and use it as a measurement.

As an example: every time a unit in a 4-ship group is shot down, you increase the value of flag number 1. When flag number 1 is equal to 4, you know the whole group is dead and use the FLAG EQUALS condition to play a message. That would look like this:

 

First the triggers to increase the flag's value

Type:

1 ONCE (Bandit 1 dead, NO EVENT)

Conditions:

UNIT DEAD (Bandit 1)

Triggered Actions:

FLAG INCREASE (1, 1)

 

We would repeat this for all 4 bandits. Then we create a final trigger to display our message.

 

Type:

1 ONCE (4 ships down, NO EVENT)

Conditions:

FLAG EQUALS (1, 4)

Triggered Actions:

MESSAGE TO ALL ('All hostile aircraft are down', 10)

Edited April 17, 2018 by feefifofum