Verifying orders?

[Pyrocumulous]

Sometimes either I mess up or one (or more) of my flights go on the wrong objective, or perhaps something goes wrong in the F10 menu. Not sure. Either way, is there a way to see what orders were actually applied early in the mission. It's frustrating to realize after flying the entire mission that Devil 3 was off on some suicide mission all by themselves. It's obvious in Tacview after the fact, because I can see their tasking right there in the label for each aircraft.

Brilliant campaign, well done!

[Sandman Simulations]

4 hours ago, Pyrocumulous said:

Sometimes either I mess up or one (or more) of my flights go on the wrong objective, or perhaps something goes wrong in the F10 menu. Not sure. Either way, is there a way to see what orders were actually applied early in the mission. It's frustrating to realize after flying the entire mission that Devil 3 was off on some suicide mission all by themselves. It's obvious in Tacview after the fact, because I can see their tasking right there in the label for each aircraft.

Brilliant campaign, well done!

Hi,

Thank you for your feedback.

Due to work I'm unable to get into DCS until tomorrow and need to check to be certain. I might also remember wrong but when you select tasking for a flight, there should be text for few seconds showing which task has been selected and for which operating area (for CAS, SEAD and CAP missions) or which target (for strike missions). After that you can also go to map view and click on the flight you want to check. Units should be named so that you can see what tasking is given to flights of your squadron. I wouldn't call it cheating when your flights are still on the deck 

Still unfortunately sometimes even if you have selected right tasking AI might end up into situation where it kills itself for nothing like flying very low over AAA battery. Fortunately most of time they do what they are supposed to do.

[Pyrocumulous]

You are correct, I see it listed under Group for each aircraft on the F10 map. E.g. "DEVIL 4 CAS H"
It's also buried in the message history, but F10 is certainly the easier way to verify prior to launch. Still super easy to accidentally RTB a flight when I go too rapidly on the Push commands, but that appears to be resolved by just counting at least 5-seconds after the prior flight confirms command on radio.