MAESTRO plugin 1.1 beta 4

[Juha Holopainen]

Beta 4 attached.

Changes from beta 3:

• bug fixes

Mplugin11b4.zip

[Jan Naslund (812053)]

Hi,

I can't find an installation instruction anywhere. Do i search my computer for the files within the zip and just replace them or is there another way of installing this beta?

Thanks / Janne
 

[Max Kuhla (1157125)]

If you do not have sufficient knowledge how to update this, I suggest using the version included in the Swedish package.

2 hours ago, Jan Naslund (812053) said:

Hi,

I can't find an installation instruction anywhere. Do i search my computer for the files within the zip and just replace them or is there another way of installing this beta?

Thanks / Janne
 

 

[Juha Holopainen]

The "Documentation" folder you've highlighted there is a good place to look for instructions. You can either build a completely new setup in which case you'll need to look at the developer documentation, or use an existing one - the one provided in your normal sector package as-is, or updated to the beta version by overwriting the old files. The settings file in the beta package is just an example setup though, it will work, but it may not have up-to-date information on the airports and the settings values might need adjustment. Its purpose is mainly to make the plugin useable in some way without extensive setup, and to act as a starting point for developers.

[Lukas Agerskov (1226374)]

@Juha Holopainen We have done some testing with MAESTRO at LIVE and at some VTC, and while the program as a whole is fine, it breaks halfway down the line it seems. 

 

Planes have a tendency of getting bounced around, once they pass that feeder fix they are calculated on. Once they are on the other side of the fix on the scope they have a tendency of jumping back on the wrong side of the MAESTRO side and then get calculated again, and that makes them build up a whole lot of double delay. 

The "Remove Flight" function also removes them but makes them pop back up again some moments later, and then being taken into the recalculation.

The "Frozen" feature seems to be only valid in relation to the landing time, but it would be great to have a feature for them to be marked frozen in relation to the feeder fixes, as well as having a chance of them being completely locked by the time they pass the feeder fix, so they don't inadvertently jump back into the queue, but stays on the bottom side of the red line after they pass it. 

In the beginning all the times fits, but after the first 45 minutes everything starts to show an enormous amount of delay and i think its due to the planes already passing the fix being recalculated and jumps back into the queue, or sometimes, it just gets stuck and calculating being at the feeder fix within 1 minute event though it already past it inbound. Not sure what we can maybe to to tackle this?

Edited Tuesday at 09:40 by Lukas Agerskov (1226374)

[Stephen Odgaard (811390)]

@Juha Holopainen 

 

A couple of clarifying questions to the terminology:

I understand Curr. delay (Remaining delay) as what ATC needs to introduce in order to not overload capacity at the time of landing. Correct? This is in other contexts defined as the Time to Loose (TTL).

How about the Total delay?

Also ETA at Feeder Fix. This is assuming the Curr. delay is introduced by ATC right?

 

Edited Wednesday at 20:08 by Stephen Odgaard (811390)