AttackGroup task don't work on spawned (teleported) AI.

[EasyEB]

I've ran into a problem assigning an AttackGroup task to a, via MIST, spawned (teleported) AI aircraft. I can assign an Orbit task to it without issues, but it seems to refuse to accept AttackGroup.

 

I wonder if it's role gets lost in the teleportation perhaps? Any input on this would be much appreciated.

 

Cheers!

[EasyEB]

Tried mist.getGroupRoute to no avail, the AI aircraft copies the rout all right, but is still not accepting the AttackGroup task.

[Pikey]

Might need to refer to the name which will change during tp. Tp clone and spawns are kinda limited that way hence went to moose as you can refer to moose spawns as they are wrapped in the database.

[EasyEB]

Which name do you mean needs refering?

 

I can assign tasks to the AI aircraft just fine, the problem is that it will not execut attackGroup tasks as it has lost it's "CAS" role. Names stay the same, both group and unit.

 

Is a teleportation of a unit where it keeps it's group name, unit name, task (CAS) and all other data possible via Moose?

[USSR_Rik]

Please attach simple mission for test.

[EasyEB]

Sure, mission is attached. Thanks for taking the time.

 

In mission TeleportAttackExample.miz Reaper1 will be teleported to the enemy group, and after 10 seconds Reaper1 and Reaper2 will be given the attackGroup command.

 

In mission TeleportOrbitExample.miz Reaper1 will be teleported to the enemy group, and after 10 seconds Reaper1 will be given the orbit command instead.

TeleportAttackExample.miz

TeleportOrbitExample.miz

Edited March 2, 2017 by EasyEB

[Coupon4Coffin]

Has this bug been confirmed, and eventually fixed ? I'm experiencing the very same issue while building a mission using scripting and the MIST library.