Aircraft-set.xml: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 31: Line 31:
   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.
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.xml 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. Typically the name might be <code>fkdr1-common-sounds.xml</code> or <code>fokker-shared.xml</code> - but anything is fine so long as it doesn't end in <code>-set.xml</code>


{{note|When defining multiple versions of an aircraft, it's important to use some additional tags to link the aircraft together correctly - this improves the user experience by telling various places which -set.xml is the most important one. See below for the <code>&lt;variant-of&gt;</code>  and <code>&lt;primary-set&gt;</code>  tags.}}
{{note|When defining multiple versions of an aircraft, it's important to use some additional tags to link the aircraft together correctly - this improves the user experience by telling various places which -set.xml is the most important one. See below for the <code>&lt;variant-of&gt;</code>  and <code>&lt;primary-set&gt;</code>  tags.}}


=== Not used for loading multiplayer aircraft ===
=== Not used for loading multiplayer aircraft ===
580

edits

Navigation menu