Questions about planning inbound AAR for AI package in a campaign.

[FreqiMANN]

FYI: all occurring in Mideast campaign.

primary issue:
when planning a refuel steerpoint and a holdpoint in the same flight plan, the hold duration for both are linked and repeat the same value. if one is set for 10 minutes, the other is set for 10. if i modify it for 20, the other is 20.

i’m trying to get multiple AI flights refueled at the same time, then have them hold and push from separate steerpoints. given the above, it appears that’ll never happen. is this intended? if so, how do the AI handle flying this? will they hold double duration at each point, or just hold once?

Side issue:
how long of a hold should i put in for each plane? i’ve been putting in 5 minutes per aircraft, so 10 minues for a 2-flight, 20 for a 4-flight. 10 for 2 seems justified, but 20 for 4 seems a little long. how do you guys calculate this?

WDP issue:
when planning a mission using WDP, the flight plan seems to take into account the advisory “tanker” steer as part of the plan, as if i would fly to my landing point, then continue from there to a tanker. this grossly overestimates required fuel on the datacard. i can solve this by deleting the advisory steerpoint, but i would rather not, if given a choice. any workaround to get it to stop doing this?

[MaxWaldorf]

Changer one waypoint or add one with refuel task…

Make sure a tanker isn’t too far

[FreqiMANN]

@MaxWaldorf sorry, but this doesn’t address anything i’ve asked.

“when planning a refuel steerpoint and a holdpoint in the same flight plan…”

i already know how to do that.

[FreqiMANN]

Further testing, today:

switched to KTO. flight plan shows same behavior. noted that there is a hold accounted for in time-on-station after the refuel point, but not after the hold point. created TE and tested flight plan in 2D with all AI. AI flight flies to refuel point, holds there. after station time ends, flight continues on. at the hold point, the AI flies on regardless of station time on the flight plan as if it was a regular nav point. this corresponds to the time-on-station observations i saw on the flight plan, itself. I’ve observed that target waypoint station time seems unaffected, like TARCAP.

while i’m glad BMS isn’t doubling the amount of time my AI spends flying in circles, that still isn’t optimal for what i wish to accomplish. i would like to frag and fly large package missions with AI. i would like them to hold away from the tanker for deconfliction, then continue on at a predetermined time/order. that seems impossible, currently.

to anyone in the know:
why is the station hold time mirrored on refuel/holding points?
why do the AI ignore the hold point?
is this a limitation of BMS? if so, can it be changed?
any workarounds people can think of?