![]() ![]() The route-manager maintains a current waypoint, which is shown in route-manager dialog, the GPS dialog (in LEG mode), on the default HUD, and potentially in cockpit displays in the aircraft. In the future, other data, especially speed restrictions, may also be associated with waypoints. Each waypoint may also have an altitude associated with it, for vertical navigation modes (VNAV). Route manager waypoints are entered as a navaid ident, an explicit latitude/longitude pair, or as an offset (bearing and distance) from another navaid. All information is currently optional, which is highly unrealistic, but convenient. The route-manager maintains a flight-plan, consisting of departure, destination, alternate airport and cruise information, as well as a list of waypoints. In general core features exist in whichever place seems the most natural, and it's up to instruments to aggregate the core modules as they require. It's important to realize that the route-manager (and GPS) are pieces that a panel instrument might present as a single real world device - the mapping between C++ modules, generic user interface and in-panel instruments is very fluid, by design. The route-manager is also how a flight plan is made available to FlightGear - in the future this will hopefully permit better ATC and multi-player interactions, since ATC logic or controllers will be able to observe the filed plan associated with a pilot. ![]() Some panel instruments may provide access to the route manager via their own UI, but the route-manager is always available through a generic dialog box. The route-manager models part of the functionality found in real-world GPS and FMS devices, but is usable in any aircraft. (in the following sections, familiarity with basic IFR concepts, Autopilot usage and radio navigation is assumed) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |