[FIXED] Flight Plans Broken

[runedog48]

I'm having several issues with flight plans. If you try to copy a flight plan / make a template, the flight plan (all the waypoints) will just delete itself, and you won't be able to edit that plan anymore. If you do anything remotely complicated, it seems the flight plan will just delete itself once the aircraft takes off, so the aircraft will just wander aimlessly in the same heading that it took off from. Also, when I set my aircraft type and loadout from the flight plan editor when I have multiple aircraft on one mission, sometimes the loadout I selected will not be the loadout that is displayed when I view the flight; Eg. Flight Kachow (3x F-16C Blk 52 Mk84...), if you expand that flight from the mission editor under assigned aircraft, the individual loadouts that are shown will not match the loadout in the flight header. One might be correct, but the others will be the wrong loadout type; however, the aircraft that are assigned to the flight always depart. I've had several instances where an aircraft with a different loadout than specified in the flight plan but assigned to the mission was included in a new flight plan I made which specified a different loadout than the one that was assigned to the flight. Frustratingly, I would notice after they took off and have them RTB, but when I went to copy the flight plan to try again, it would just get deleted, and I would have to create the flight plan all over again.

TLDR:
1. Flight plans sometimes delete all of their waypoints with no explanation provided when the aircraft takes off; the aircraft will then fly in the same heading that it took off from indefinitely.
2. Copying flight plans/flight plan templates doesn't work and will delete your flight plan.
3. Aircraft assigned to a flight sometimes display a loadout that is different from what is specified in the flight plan and the header for that flight.
4. Aircraft with a loadout that is different from the one specified in a flight plan will be assigned to the flight.

Build Version 1.06.1328.15 (Hotfix Build, but the issues persisted before this hotfix)

I've attached a scenario that demonstrates the 1st bug. When/if I encounter the others, I'll also post them.

[blu3s]

Hi runedog48,

Did you generate the flight plans before changing the flightsize in the mission?

There's a 3 AC flight plan while the mission sets 1 AC per flight plan.


Logged 0015643

[runedog48]

Hi runedog48,

Did you generate the flight plans before changing the flightsize in the mission?

There's a 3 AC flight plan while the mission sets 1 AC per flight plan.


Logged 0015643

I might have, but I can definitely reproduce it either way. I don't see where the flight plan is set to 4 AC in the mission I provided. Stand by, I'll set it up again. Also, I attached a screenshot of #3. They're all supposed to be the short-range MK84 loadout (all ACs are equipped with that loadout), but it displays the regular MK84 and one with no loadout.

E: While making the mission again, I noticed there were 4 vacant slots once I activated the mission instead of 3 and 3 aircraft being assigned to the mission. I ensured it was 3 AC minimum/desired when I made the mission. Is this what you were observing?
E2: Same scenario, new mission, making sure the entire time the flight size was 3 and only setting the loadout one time. Only changed the location of the waypoints and added a split, then activated the mission without touching anything else.

[blu3s]

What I mean is that there's one filght plan with 3 ACs



But the mission flight size shows only 1 AC per flight plan




But don't worry, I can reproduce the issue with you scenario and also using another flight plan.

[Dimitris]

Is this still an issue in B1328.17 ?

[Deserere]

hi runedog48 ,
this was tested with the current codebase and as long as your flightsize matches the actual AC in the flight it seems to generate no issues.
I was able to copy the flightplan, create a new flight and having both of them take off as expected.
Let us know if any issue persists, I'm marking this as closed