580
edits
Aircraft-set.xml: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (→The -set.xml file itself: remove errant syntaxhighlight closing tag) |
No edit summary |
||
| Line 1: | Line 1: | ||
The '''aircraft-set.xml''' file (or rather ''name-of-aircraft''-set.xml) is the top level aircraft configuration file. The aircraft-set.xml file should be in the aircraft's root directory, for example <code>[[$FG_ROOT]]/Aircraft/747-400/747-400-set.xml</code>. | The '''aircraft-set.xml''' file (or rather ''name-of-aircraft''-set.xml) is the top level aircraft configuration file. The aircraft-set.xml file should be in the aircraft's root directory, for example <code>[[$FG_ROOT]]/Aircraft/747-400/747-400-set.xml</code>. | ||
When FlightGear loads an aircraft the aircraft-set.xml file is | When FlightGear loads an aircraft, the aircraft-set.xml file is the main source of information, about other files to load, such as the 3D model and FDM configuration. It also contains meta data that is important when packaging the aircraft before a release of FlightGear, or when searching for aircraft in the UI (for example, the launcher). | ||
== Overview == | == Overview == | ||
The aircraft-set.xml file is an XML file | The aircraft-set.xml file is an XML file which contains many recommended pieces. | ||
* A header with | * A header with meta-data such as author information and a description | ||
* [[Aircraft rating system|Aircraft ratings]] that can be used to select only the more well developed aircraft (or bad ones if you are looking for aircraft to improve) | * [[Aircraft rating system|Aircraft ratings]] that can be used to select only the more well developed aircraft (or bad ones if you are looking for aircraft to improve) | ||
* [[Howto:Reassign keyboard bindings|Keyboard bindings]] | * [[Howto:Reassign keyboard bindings|Keyboard bindings]] | ||
| Line 30: | Line 30: | ||
fkdr1-yasim-set.xml | fkdr1-yasim-set.xml | ||
fkdr1-uiuc-set.xml | fkdr1-uiuc-set.xml | ||
When creating multiple aircraft this way, it's very common to put shared XML data into a -common.xml file which is included by both of the -set.xm files. It's important that your common file does ''not'' end in -set.xml, otherwise some systems will erroneously consider the file as another aircraft. | |||
=== Not used for loading multiplayer aircraft === | === Not used for loading multiplayer aircraft === | ||