Problem with Attack area MCU

[DN308]

Hello,

I've designed a mission in where a flight have to reach a point and search for aircraft. Simple, uh?

 

Well, I used a simple MCU "attack zone" linked to the leader and from the last WP. Duration: 10 minutes. Classical.

 

I've let my mission on Auto pilot, and my flight continued to turn until running out of fuel (spitfire IX with full gas tank capacity).

 

Maybe I missed something...

 

Next waypoint (after the attack area) should be linked to the plane, no? Is that not an automatic sequence after the time out?

[LLv34_Temuri]

So you don't trigger the next waypoint after the attack with anything? That's probably your problem, you need to trigger the WP.

[DN308]

With what?

[LLv34_Temuri]

46 minutes ago, DN308 said:

With what?

For example with a timer. So your first waypoint will trigger the Attack Area MCU and a Timer to which you've set for example 10 minutes delay. That timer then should trigger the next waypoint.

[JimTM]

I haven't tested lately but I wonder if the OnAreaAttacked report message is generated when the attack begins or is it generated when the Attack Area MCU time setting expires? If the later is the case, that could be used to trigger the RTB waypoint. Note that you need to select "Attack Ground" in the MCU to get OnAreaAttacked (last time I tested, long ago).

Edited October 2, 2020 by JimTM

[Gambit21]

4 hours ago, DN308 said:

With what?

 

My workflow is...

 

OnBingoBomgs - timer 1sec - Deactivate Attack

                               timer 2 sec - Force Complete HIGH

                               timer 3 sec - Form UP waypoint.

 

I actually daisy chain them together to that the first time pipes directly into another 1 sec timer for Force Complete, then to another 1 sec timer for Form up.

You can do it any way you want, even lower the time increment, point is they don't happen simultaneously.

[DN308]

Ok, Manu thanks 

I thought the Timer in the MCU properties was enough to trigger the next waypoint 

[Gambit21]

3 hours ago, DN308 said:

Ok, Manu thanks 

I thought the Timer in the MCU properties was enough to trigger the next waypoint 

 

One helpful thing to keep in mind, you can trigger anything with anything else.

You can trigger the next waypoint in a flight with a truck hitting and intersection on the other side of the map if you want.

That wouldn't take sense, but the point is, the editor is EXTREMELY flexible. 

[DN308]

Funny as hell, I’ve made another mission where this attack area command was used and stopped when another a/c triggered a WP.

But i’ve Never used this MCU alone (I mean, for a fighter hunting around it for some time before proceeding to another wp) with the need to trigger the next WP after a moment. I use to play with attack area for some bombers, and in that case I use a check zone or complex trigger because onbingobombs don’t work evytime.

 

I just wonder what’s the interest or the reason why there is an activation time in the MCU.