MAESTRO plugin 1.1 beta 7

Juha Holopainen (839337)

Changes from beta 6:

Flight Information Window available on slave instances
For aircraft past the feeder fix with an assigned heading set, a shortest vectoring path with current groundspeed is assumed for calculations instead of the EuroScope calculated route. By default the path takes the aircraft to a 10nm final but this can be adjusted using the settings file.

Lim Chan (1493429)

Hello, is it possible to have 2 runway manage into one sequence? So it can be worked for VHHH where 2 runway share the same IAF and approach path.

Juha Holopainen (839337)

The plugin assumes all runways to be completely independent. It is not possible to set up one sequence to depend from one or more other sequences.

Lim Chan (1493429)

Understood, thank you!

Max Kuhla (1157125)

When one aircraft in the sequence pauses he delays all aircraft behind it assuming they are all stable (which is the case below).

Is a workaround possible the handling of frozen/paused aircraft, so that they at least show up in the flow so that you can remove/de-sequence them, which is not possible when they disappear off the timeline as all aircraft behind it?

Juha Holopainen (839337)

I can see how a zero groundspeed is going to be problematic for the new feature where vectored tracks' predictions are calculated with their current groundspeed. I'll figure out something.

Bernardo Reis (1096507)

Any setup recommendations for PMS arrivals?

Currently the ETA at the RWY is being calculated with the whole sequence arc flown. We would like to setup a "default" time from the FF down to the RWY. Something like the System_Default_Feeder_Time setting, but for flights routing trough defined FF.

Juha Holopainen (839337)

For the time being, your options would probably include:

Leave everything as it is, accepting that the aircraft will in most cases be able to reach the runway earlier than the software thinks is possible, and the implications that has on the sequence prediction
Adjust the STAR definitions in the ESE file to not include the sequencing arc. This will calculate the "best case" ETA not only for MAESTRO but also to EuroScope and all plugins based on its predictions (such as TopSky), the downsides being an incomplete route prediction (confusion, difficulty in issuing direct-to clearances to the missing points, possible nuisance RAM alerts, ... )
Create a special sector file to be used only with MAESTRO, with the sequencing legs removed from PMS STARs. Then run MAESTRO in its own EuroScope instance with this sector file and TopSky in another instance with the normal sector file.

I've been working on a setup possibility where you can define PMS sequencing arc waypoints or other parts of arrival procedures not expected to be flown and the plugin would remove them from the time predictions. Will likely be available for testing with the next version.