Juha Holopainen (839337) <DOWNLOAD LINK> 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.