MAESTRO plugin 1.1 beta 8

Juha Holopainen (839337)

Changes from beta 7:

Vectored aircraft that freeze should no longer mess up the whole sequence, instead they start getting pushed back and get displayed and treated like disconnected tracks (i.e. grey by default, and automatically removed from the sequence after a defined time). If the fix doesn't work, a workaround is to remove the assigned heading -> the aircraft should be calculated into the sequence again and can then be de-sequenced.
A new airport-specific setting line DELAYPATH introduced. The defined part of the predicted flightpath will not be taken into account for the time predictions (example use scenarios would be sequencing legs of PMS procedures and other lengthy STARs where a specific portion is so rarely flown that it's best to just forget about it). Only one of these will be taken into account for any one flight, it's not possible to define one sequence to remove from one part of a STAR and another one later on.

Should there be issues with these, I'll need a EuroScope log from the session as both of them are somewhat tricky to troubleshoot if I can't see them happening in real time.

Max Kuhla (1157125)

As a follow-up to the DELAYPATH option.

Would it be possible to instead manually define the entire path from the FF used for predictions?

Juha Holopainen (839337)

I'm afraid custom route predictions would be well outside the scope for this project at this time.

Adrian Bjerke (1339353)

Testing out this plugin abit in Norway and we keep experiencing the following issue:
One aircraft gets a bugged routing, which make its estimate being much later than it actually is going to be.
However the issue with this, is that MAESTRO seems to delay every other aircraft behind - requiring us to manually resequence or desequence that aircraft.

Examples:

Shouldnt there be any logic if an aircraft suddenly gets delayed, it will automatically resequence that aircraft to avoid issues like this? Have we configured something incorrectly?

Juha Holopainen (839337)

I will probably add a safeguard to force an aircraft back to unstable state if its STA is outside the timeline's time span which is clearly undesirable and makes it impossible to adjust the sequence. Other than that, coding enough intelligence to decide which routes/delay changes are bugged and what to do with them is not realistic at this point. For cases like yours there, your best bet would be to try and find out what causes the routing to go wrong, and then prevent that from happening. Based on those images alone, my guess would be that someone (a controller) or something (a plugin) is inserting NOVPO at the end of the aircraft's FPL route and that causes the prediction to calculate the roundtrip from the last point of the STAR to NOVPO and then to the destination.