117
edits
FlightGear Newsletter September 2011: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter September 2011 (view source)
Revision as of 20:23, 25 September 2011
, 25 September 2011→--parkpos=AVAILABLE
| Line 11: | Line 11: | ||
[[File:Fgfs-screen-334.png|thumb|San Francisco International becomes busy with traffic.]] | [[File:Fgfs-screen-334.png|thumb|San Francisco International becomes busy with traffic.]] | ||
As part of a new initiative to make the FlightGear skies more lively, we are currently in the process of adding 344963 new individual flights, from about 65 airlines to FlightGear's AI system. At the moment of writing, The schedules for the major american carriers (American Airlines, Delta Airlines, and United Airlines), as well as that of one of the Leading European Airlines (British Airways) have been added and more traffic will follow soon. | As part of a new initiative to make the FlightGear skies more lively, we are currently in the process of adding 344963 new individual flights, from about 65 airlines to FlightGear's AI system. At the moment of writing, The schedules for the major american carriers (American Airlines, Delta Airlines, and United Airlines), as well as that of one of the Leading European Airlines (British Airways) have been added and more traffic will follow soon. | ||
=== Starting at the most appropriate parking position === | |||
At selected airports, it is now possible to let FlightGear decide at which parking it should start. You can do this by passing the commmand line option <nowiki>--parkpos=AVAILABLE</nowiki> to FlightGear. This way, you don't need to worry about the details of whether the parking is of the right type, whether it is large enough, etc etc. | |||
However, in order to get it to work, you need to set some properties: | |||
'''/sim/dimensions/radius-m''' should be a nummeric estimate of the size of your aircraft. A small aircraft fits into a large parking, but a large aircraft does not fit into a small parking space. Because the AI part of radius is also used for slightly different purposes (prioritizing gate assignments), the given value may deviate slightly from the real aircraft's size. See [[Aircraft_radii|our wiki for an overview of standard aircraft radii]] currently in use. | |||
'''/sim/aircraft-class''' can be any one of "ga", "cargo", "gate", "mil-fighter", "mil-cargo", or "vtol". See [[Interactive_traffic#A_technical_perspective|our wiki documentation]] for more information. | |||
In addition, the property '''/sim/aircraft-operator''' can be set to a three letter icao airline code. The first two properties are mandatory for the system to work, the last one is optional, but will generally result in a better parking location. | |||
Fortunately, it is also possible to set these properties in the aircraft's configuration file. Currently, two aircraft have been updated to automatically take advantage of this new system. These are the Boeing 777-200ER, and the Embrear 170. The properties aircraft-class and aircraft-operator can also be changed by FlightGear's livery select mechanism, so that depending on whom you're flying for, you'll spawn at a different part of the airport! See [http://www.flightgear.org/forums/viewtopic.php?f=18&t=13527 the corresponding forum discussion] for more information on how to update the aircraft configuration and corresponding livery select files. | |||
== Snapshot releases == | == Snapshot releases == | ||