377
edits
Changelog 2016.4: Difference between revisions
Jump to navigation
Jump to search
→Scenery: More precise "title" for the apt.dat-in-scenery-folders change
Parnikkapore (talk | contribs) (→Scenery: Formatting cleanup, revert if it is an issue!) |
(→Scenery: More precise "title" for the apt.dat-in-scenery-folders change) |
||
| Line 54: | Line 54: | ||
=== Scenery === | === Scenery === | ||
* '''new [[File_Formats#.2A.stg_files|STG verbs]] '''<ref>https://forum.flightgear.org/viewtopic.php?f=5&t=22809&p=295366#p295342</ref> | * '''new [[File_Formats#.2A.stg_files|STG verbs]] '''<ref>https://forum.flightgear.org/viewtopic.php?f=5&t=22809&p=295366#p295342</ref> | ||
* ''' | * '''Support for apt.dat files inside scenery folders''' For years, FlightGear has been reading a large file called apt.dat.gz and located in [[$FG_ROOT]]/Airports. This file, which is maintained in collaboration with the X-Plane developers and users<ref>Via [[WorldEditor]] and the [https://gateway.x-plane.com/ X-Plane Scenery Gateway].</ref>, contains a lot of information about airports (names and geometry of runways, taxiways, aprons, surface type, position of runway thresholds, light beacons, position of Control Tower, communication frequencies... even startup locations, though FlightGear reads parking positions from other files called ''airportID''.groundnet.xml). Data from this file is used to create the scenery files for airports (.btg.gz), to display airports in the FlightGear built-in map, as well as to let the simulator know how to place your aircraft when starting on a runway—among others. | ||
: Despite the possibility to have FlightGear read portions of the scenery from various folders (cf. [[$FG_SCENERY]]), this data was only read so far from this one file, [[$FG_ROOT]]/Airports/apt.dat.gz. As a consequence, custom sceneries could not bring new or updated airport layouts without FlightGear having part or all of the information wrong concerning these airports, since it was read from a file that is maintained independently from said custom sceneries—and tied to FlightGear's current World Scenery, and therefore frozen in FlightGear since 2013. | : Despite the possibility to have FlightGear read portions of the scenery from various folders (cf. [[$FG_SCENERY]]), this data was only read so far from this one file, [[$FG_ROOT]]/Airports/apt.dat.gz. As a consequence, custom sceneries could not bring new or updated airport layouts without FlightGear having part or all of the information wrong concerning these airports, since it was read from a file that is maintained independently from said custom sceneries—and tied to FlightGear's current World Scenery, and therefore frozen in FlightGear since 2013. | ||