![]() ![]() As of X-Plane 11, the default GNS430/530 and the new default FMS get their airport data from the apt.dat that contains X-Plane default and gateway airports. ![]() There is no longer a mismatch between default scenery data and GPS data. But in the GNS units, the airport can be found via the ICAO. I actually have to type the name, Sekiu for it to be found and the ICAO is blank. So when I am in the Flight Configuration Window and try to type 11S in the Search bar, nothing is found. I am assuming that like 10, there is a miscorrelation of the GNS units and the airport database in x-plane, meaning I noticed with 11 that many of the airports (not all) with 3 digit codes like 11S don't have the ICAO associated with it. Is this also the reason why some 3rd party planes like the Twin Otter show Exp 30/JUNE/15 even though I have the latest 1613? Now the 1613 cycle is valid from 8 December 16 to 5 January 17, but X-Plane doesn't know if it is 2016 or 2017!įor the next beta, I just take the year of the machine time (your computer's clock) and that will lead to correct indication of validity even with cycles that cross the year boundary. You can set day and month and hour and minute, but there's no inherent year to X-Plane's time. The problem is, X-Plane's internal time has no year. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |