I want to consolidate all the issues and questions I see with the flight plan editor so I can finish documenting it (and completely understanding it). Its the best tool that has been added to Command in its 10-year history. But it is still being tweaked and parts of it's capabilities and limitations are somewhat opaque. I want to use this thread to suss out the details to get feedback from players and the devs. Here is my starting point:

Changes or issues:

• Disable Flight plan buttons on non-aircraft missions. Just a UI clean up.

• Warning for disabling dynamic missions removing units. Avoids important mistakes.

• In FP editor, Doctrine/ROE feedback not working. It seems the changes and settings work, but no feedback in the editor

• No WRA in doctrine through flight plan editor.

• Targeteering button doesn’t seem to function. Not sure if its supposed to.

• Define who the leader is in the tab. Is it always the first tab?

• Re-evaluate attack altitude for each target in the mission? Causing issues in multi-target attacks in very rough terrain.

Questions

• Is the flight plan editor going to have access from lua or events? Having an event trigger based on waypoint in the flight plan would be very useful.

• What is the difference between a FP and an FP template? Is it more than just leaving units out?

• There are only three formations available in the flight plan editor. Can that be expanded to custom formations?

And of course, my one big request that is already in the requests thread is to expand its capabilities to non-aircraft. As anyone adds comments or tips, I'll update the first post and eventually update the doc.

Going to put this here because its inter-related to flight plans.

This is a test of the mission behavior within the context of the Ops Planner. I have a two test missions built that dynamically use the same six F-15s on patrol. The Ops Planner's initial mission is listed. It runs for an hour then shifts to satisfied that should trigger Second Mission. It seems to work overall, but take a look at the mission editor for one of the flights before Second Mission is triggered through Frist Mission goes satisfied.

• Second Mission is Waiting on Trigger

• In the Assign box, Cajun flight is already listed as being on Second Mission

• On unit task, Cajun is listed on First Mission (active).

• If you check the unit on the map, it still says First Mission

• When First Mission is satisfied, Second Mission is triggered

• In the assigned box the Cajun flight switches to First Mission

• On unit Task, Cajun goes to Second Mission (active)

• The on-map unit says Second Mission

It seems like the Assigned box reflects the opposite mission. I'm a little confused by why Assigned box disagrees with the task listing and map display. I have refreshed the mission editor to make sure the text and messages are current.