[REPORTED] AI ignores tasks?

[Reflected]

Missions that have worked before don't work anymore. AI seems to ignore tasks such as "follow". I'm going to try to replicate this. Have you noticed anything weird?

[Reflected]

OK I made a simple test mission. Flight 1 takes off then circles. Flight 2 is supposed to take off and follow flight 1, yet they head to the next waypoint:

taskingtest.miz

[Grimes]

Looks to be dependent on when the task is given and whether or not the AI thinks it can complete it at that point.

 

The task works if assigned after take-off. It also works if flight 1 is already airborne while flight 2 is on the ground.

 

I added another flight with a simple bombing task which was ignored if assigned as part of a take-off waypoint, but again works correctly with the first waypoint. Gonna need to test this some more to make sure its not impacting other tasking.

[SUNTSAG]

In addition to this another advanced Waypoint issue I have found is that AI message transmissions do not function and have to be assigned via the AI push task functionality.

[Reflected]

Thanks for looking at this Grimes. It's got to have an impact on all campaigns I believe.

[Tippis]

I've come across this as well, and Grimes' interpretation of what's happening makes sense. A work-around I've found (which coincidentally happens to be a good idea to implement anyway) is to set up timed holing areas before assembling packages.

 

You take flight #1, send it off to orbit at some waypoint until a specific time (it doesn't have to be long — just enough to account for various take-off queues and delays). You then take flight #2, and do the same to it.

 

Once both have completed the orbit task, only then do they get assigned their “collaborative” tasks (escort, follow and the like). Everyone's in the air, everyone's close-by so they don't have to waste tons of fuel chasing each other down on AB, and it just (usually) operates more smoothly in general. Once you've gotten it to work, you can shave down the orbit times to match the actual time the AI takes to get there.

[Reflected]

Sorry, but workarounds are no good for me. I don't want to completely rework the logic of all my campaigns and missions. This is basic stuff that should work, and I'm sure ED is looking at it already. Thanks for the advice anyway.

 

I tried to create a new mission, and the AI completely ignored all their tasks. Take off from boat, WP1 - refuel - nothing. WP2 orbit - nothing...

[Reflected]

I've done a lot of testing and I think I've nailed down the exact problem. it's not about when the task is pushed, at what waypoint. AI will ignore follow/ escort tasks, if the unit they need to follow is not airborne at that moment. If it is airborne, AI will perform the task even at WP0, cold start, takeoff, whatever.

 

Can anyone please confirm or deny?

 

Can we please have an official word whether or not it is the case, and whether or not I should go ahead and redesign all my missions accordingly?

Edited August 15, 2019 by Reflected

[Grimes]

I've done a lot of testing and I think I've nailed down the exact problem. it's not about when the task is pushed, at what waypoint. AI will ignore follow/ escort tasks, if the unit they need to follow is not airborne at that moment. If it is airborne, AI will perform the task even at WP0, cold start, takeoff, whatever.

 

Can anyone please confirm or deny?

 

Can we please have an official word whether or not it is the case, and whether or not I should go ahead and redesign all my missions accordingly?

 

The task works if assigned after take-off. It also works if flight 1 is already airborne while flight 2 is on the ground.

 

Thats a confirmation.

 

 

I don't know how much of a redesign is needed. From my perspective it looks like you'd need to insert an extra waypoint with a few specific tasks so they get executed after take-off. As it stands it appears that enroute tasks, commands, and options are executed as expected.

[Surrexen]

I've had some interesting things happen lately with Pinpoint Strike groups using F-117's and Tornado GR4's where if the unit has RTB on Bingo Fuel as part of their tasking options, they will do their bombing task and then stop following the flight plan. Maybe try removing RTB on Bingo Fuel and see if things go back to normal?

[Bruce_D]

Hi,

 

I’ll try to complement this tread with another situation.

 

After air to air refueling AI will ignore the engage task and will only orbit on the waypoint. I’ve created a small mission example to show what’s happening.

 

Tks

AA Test.miz