-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Rewrite to break dependency on A32NX.
Have got as far as pulling in the nav log from SimBrief and calculating for each waypoint the current distance. To identify a reporting point we're looking for a waypoint which is getting closer, gets to a sufficiently small distance (one mile, maybe?) and is then getting further again. Once we've logged it we should clear the list up to that one.
Initial version is now working, minus the waypoint clearup. In a VA with no flight time restrictions, we should try a route with some extreme turns at both high and low altitude to see what the minimum distance we need to support to consider a waypoint "passed" is. The furthest so far was between 1 and 2 miles, a 90+ degree turn during approach.
Not sure whether we can get fuel used in general. I assuming fuel remaining is standard FS stuff.