As it was the default it used the XPLMNavigation SDK so these planes worked with both AirTrack and AirFMC. Providing a similar interface it would take waypoints and enter them into the plane using the datarefs that allowed to control it. the FMC that was present in X-Plane 9 and 10 for most planes. Up until recently AirFMC also supported planes in default FMC mode i.e. But the downside is that AirFMC doesn't work with all planes, only those supported, as each plane requires work to be done on the plugin to support its own data structures. This solves the problem for those planes where AirTrack doesn't support their FMC as users can still use AirFMC to create a flight plan. Anything the plane shows on its MCDU screen will be sent back to AirFMC and displayed as is.
XPLANE 11 FLIGHT PLANS SKIN
It will also save it for future use.ĪirFMC has a different mode of operation instead of relying on the XPLMNavigation SDK, it simply acts as a skin to the plane being used providing it is supported any key you press is sent to the plane's FMC as is and it is up to the plane to act on it. This should make life easier and will allow you to load the same flight plan on multiple devices at a click without having to re-enter it.
Using an Air Account and the Route section of this website users can enter flight plans easily by just entering or copy-pasting the sequence of waypoints and airways, and then have them beamed down to AirTrack. Not ideal and extra work but it is the only thing we can do as the planes simply don't support sharing their flight plans. In this case AirTrack's flight plan will work independently from X-Plane, but if a user loads the exact same flight plan on both, then AirTrack will show pretty much what's being flown in the third party plane in its ND. At the cost of redundant work, you can make AirTrack work with its Flight Plan Data locally by going to the iDevice Settings app (not the settings page of AirTrack), scrolling down to AirTrack and enabling standalone mode for FMC Flight Plan. If a third party plane totally doesn't work with AirTrack's FMC then there is still a way. This is however better than nothing because the flight plans entered in the plane's own FMC will display correctly in AirTrack and its ND, they just cannot be written to. if AirTrack writes to these data structures the planes won't take this into account. the route data you enter in their FMC interface is populated to the XPLM data structures but the reverse i.e. There are also third party planes that only support read mode, i.e. There are several third party planes that don't comply to this and there is nothing we can do except hope that they do one day. This tends to work with most planes but doesn't always why? because some third party planes have their own internal FMC systems (and with it route data) and they either don't expose their flight plan to X-Plane via the XPLMNavigation SDK or don't read from it. What is and what isn't supported in terms of flight planning in AirTrack and AirFMC.ĪirTrack uses the X-Plane XPLMNavigation SDK () to access, read and if possible write to the FMC engine. As this is a frequently asked question on our support mailbox, it is time for it to have its own article on the FAQ.
0 kommentar(er)
