ME time based movement trigger & JTAC conditionals

[coolts]

I am creating little mission where I have two arms smuggler ships in port and a convoy of trucks receiving the “goods” before hitting the road and once past a certain ROE point, becoming fodder for yours truly and his hog.

Once the deal is done, I want the trucks to start on their way and the ships to leave port. That will be my signal to shadow the convoy until it crosses a river bridge.

Now, if the mission starts at 12:00, how do I get the convoy to hold at WP1 till 12.30 for instance then set off?

I’ve got the ‘speed’ and ‘start’ parameters in the “vehicle group” tab, but I recall advice a while back to copy the entire group. (One static with no WP’s and one moving but not visible at start. Once my set time is triggered, I hide the static group and the second one becomes active and sets off on its waypoints).

Is this still best practice?

 

Once my convoy cross the bridge trigger zone I have flag triggered and a JTAC ‘s “condition” parameter “is user flag” set to trigger his “FAC – Engage group” action. This bit needs testing as I’m not sure it’s the best way to trigger a JTAC as I don’t want him available till the convoy gets near him.

[asparagin]

Now, if the mission starts at 12:00, how do I get the convoy to hold at WP1 till 12.30 for instance then set off?

 

For this you can select the convoy,

enter start at 12:30

and check "visible before start".

[coolts]

Elegant and simple. Thanks for that!

[asparagin]

:thumbup: have fun with your mission

[CrashEd]

Would be interested in flying that mission if you're thinking of sharing it when you've done mate? Can't get enough JTAC missions at the moment. Wish I had more time to create some of my own...

[Grimes]

I think I posted this somewhere in the beta forums, but I figure its sound advice in general.

 

There are now multiple ways to "spawn" AI ground forces and to keep them from moving. Each has their benefits and draw backs.

 

1. Group Activate/Visible before activation (method you used).

Pros: If invisible before start they cannot be killed via player exploit.

Cons: Slight lag spike/game pause whenever they spawn.

 

2. AI On/Off. With the use of triggers unit or groups AI gets turned off at mission start, and back on again when group needs to be activated.

Pros: No Lag spike. Can also be used to enable and disable groups

Cons: Ground units are an "empty shell." The cannot react to enemy threats and require trigger logic to re-enable

 

3. Hold Action. Using group actions a group is told to hold at current waypoint until condition is met to stop.

Pros: AI are still active and can react to threat

Cons: Currently can only be ordered at a waypoint.

 

4. (WIP Incomplete Feature) "Stop and Deploy to Template" trigger action. As its incomplete I'm note 100% sure what it does. I assume it just stops the group wherever they are at and they will go into a formation template.

Pros: Is performed wherever they are at?

Cons: I donno. Maybe they try to drive off a bridge if the trigger is given while they are on a bridge... not entirely sure as its incomplete. :D

[brewber19]

Does anyone know if this actually works? I cant seem to get the start or stop condition to be Flag X = False...it keeps putting the bloody tick back in the box.

 

Anyone know why? Banging my freaking head against the wall and all I want to happen is a group to hold at a WP until its killed its targets, then move on.

 

 

Aaaagggghhhh...I love and hate the ME in equal measure.

 

 

3. Hold Action. Using group actions a group is told to hold at current waypoint until condition is met to stop.

Pros: AI are still active and can react to threat

Cons: Currently can only be ordered at a waypoint.