Yup. Big guessing game for people like me that know little about fs9gps. Since the FS Flight Planner generates a cruising altitude for you once departure and destination airports are set, I assumed there ought to be a fs9gps function to do that. But no luck yet getting it to work. Don't know if I am incorrectly identifying the necessary input parms, if this an asynchronous issue or what, but no success.
I note with some interest that inside FS Flight Planner, cruising altitude is set along a straight line flight path between departure and destination airports only. Even if you add waypoints that would obviously require different cruising altitudes, the initial airport to airport cruising altitude is not affected. So, even if I figure out how to get a value out of FlightPlanWaypointMinAltitude, I am not sure what it will be. A waypoint altitude? A departure to destination altitude?
Here's what I have tried without success:
Code:
<Macro Name="c">C:fs9gps</Macro>
<Update>
(A:GPS FLIGHT PLAN WP Count,number) 1 - (>@c:FlightPlanWaypointIndex)
(@c:FlightPlanWaypointMinAltitude,feet) (>L:MinEnrouteAltitude,number)
(@c:FlightPlanWaypointAltitude,feet) (>L:WPAltitude,number)
(@c:FlightPlanWaypointRemainingTotalDistance,nmiles) (>L:DistanceToDestination,nmiles)
</Update>
I added FlightPlanWaypointAltitude and FlightPlanWaypointRemainingTotalDistance just for grins. Those work as expected, generating in this case, the altitude of the destination airport and the cumulative total distance of all remaining flight legs.
But only a 0.00 value for L:MinEnrouteAltitude. I know that FlightPlanWaypointIndex has been defined properly because the other two functions work correctly. Apparently it is not as simple as defining the Waypoint Index.
Maybe I have not given FS what it needs to know before generating FlightPlanWaypointMinAltitude, but I dont know what Im missing.
fs9gps experts, where do you go from here on this one?
(I am using FS9)