![]() ![]() ![]() ![]() One building: British Airways Maintenance FacilityĬomplete and fully modeled to highest level of detail with day and night textures AI parking and ground network A modified tile is available at Torsten's scenery site Tower,buildings,shared-models and signs doneĪlmost complete, home of the Seneca used to model the FlightGear version. Signsīasic models of tower, terminals and hangars Tower, terminals, Signs and unique buildings downtownįully modelled, avail on github, see EDDB Gliders often start from here.įully modeled, plus unique buildings downtownįully modelled based on Shared-Models, incl. (Buildings may not align with taxiways in default scenery, until it starts using the newest recommended airport data from X-Plane.)įully modeled with tower, terminal, animated hangars etc.įully modeled with Signs and AI Traffic and unique skyscrapers downtown ICAOĬustom objects for all major buildings, including public terminal. Note You can sort the table by clicking one of the symbols in the row headers. Green dots: taxi signs placed at the airport.Dark red dots: shared models in the scenery database placed at this airport.Red dots: static objects in the scenery database made especially for this airport.The current airport layout with runways, taxiways and aprons.The ICAO codes link to the FlightGear mapserver, which - among other things - contains information about the current status of the FlightGear Scenery Database. For a list of currently ongoing scenery related projects, please check out Current Scenery Projects. parking.xml files under scenery/Airports.If you are currently developing an airport, please feel free to add it to Airports under construction. Shipping the most relevant airport data with the Scenery. Reading of startup information: When set to "true", the runway dimension data in apt.dat are overwritten by those in the $FG_SCENERY/Airports///, so that there is more flexibility in regenerating the terrain tiles without having to force the updated runway positions back into apt.dat.Whenever this boolean property is set to false, ground network data will be read from $FG_ROOT/AI/Airports/ and when set to true, it is read from $FG_SCENERY/Airports////.groundnet.xml. Users of those versions can choose which set of data to use, by toggleing the property /sim/use-custom-scenery-data. A tool to create a condensed runtime-extract is being prepared and is expected to get introduced until the next FlightGear software release is due.įor the transition periode (FlightGear 2.0.0 till 2.4.0), a new property was introduced. Instead, this directory structure is designed as a transport to be editable by the average developer. Note, this directory structure is not meant to be used primarily as a datasource during runtime. The directory is organized using sort of a poor-man's alphabetical index, using three stages of subdirectories: Airports//// (with the three first characters of the ICAO code). This information is stored in a couple of XML files in the relatively new $FG_SCENERY/Airports/ directory alongside the well known Terrain/ and Objects/ directories. Aircraft parking positions (to avoid airliners parking on the grass or inside the terminal building).Taxiway ground network (we do not want AI airliners to taxi off the tarmac).ILS positions and orientation (apparently depends on runways).Threshold positions and orientation (typical startup positions).Several entities were identified as overlapping between the visual representation of airfields in the scenery and the respective data files in the base package, namely: In other words, deriving an absolute minimal subset, basically: the geographic information that is required to match with the scenery airport layout, from the respective sources and store this in a 'traditional' file format that, as usual, allows every contributor to verify his contributions before submitting to some general repository. The task was to achieve this goal by a solution as minimalistic as possible, still keeping compilance with traditional rules in the FlightGear development process. The scenery on the other hand depends on the base package because we rely on deriving runway threshold positions and other geographic entities from the files which are shipped as a part of the base package.įrom FlightGear 2.0.0 onwards, efforts have been made to untie the scenery from this dependency chain, leading to the $FG_SCENERY/Airports/ directory.The base package depends on the SimGear and FlightGear source, mainly because aircraft features are being developed in sync with the available FDM and rendering facilities.Traditionally, the "three main sources of FlightGear users' joy" are tightly coupled together: This article gives an introduction to the $FG_SCENERY/Airports folder. ![]()
0 Comments
Leave a Reply. |