reported Working around buggy 'restrict air-to-ground' ?

[BuzzLine]

Context/bug : 'Restrict air-to-ground' has been "misbehaving" since forever, it is known. It considers a unit of type plane as an air target even when on the ground. Which is ... surprising and not very useful to mission designers. (see miz and track attached.)

Question : how to I setup two flights attacking an airfield so that my CAP flies high cover and lets my strikers shoot the targets on the ground ? I'd like to have a plane take off at some point during the attack so I can't have only statics. At this point, despite using restrict air-to-ground, any flight with task CAP or a variant of 'search and engage' will drop down low to strafe the uncontrolled airplane on the field... In range of air defenses, unfortunately.

Bug_CAP_strafing.trk debug_CAP_strafing.miz

[Flappie]

I tried setting it as "Invisible" but the Hornet kills it nonetheless. Then when I start the invisible airplane in the air, the Hornet ignores it.

I think there are two bugs here. I'll report both.

I reported uncontrolled aircraft being attacked when "restrict air-to-ground" is on.

Edited December 3, 2022 by Flappie

[Flappie]

I found the solution. An uncontrolled AI does not take into account advanced waypoint actions. It looks like a feature, not a bug.

You need to use Triggered actions on this one. Here's a fix.

Aircraft starts uncontrolled. It has two triggered actions:

1. Invisible, which will be activated at mission start.
2. Start, which will be activated whenever you want. In attached mission, the aircraft will start its engines as soon as the Hornet enters a trigger zone.

debug_CAP_strafing_FIX.miz

Edited December 3, 2022 by Flappie

[BuzzLine]

1 hour ago, Flappie said:

You need to use Triggered actions on this one. Here's a fix.

Oooh, fancy, I like that ! That solves my woes, many thanks.