219
edits
m (→Ratings: Typo) |
m (Explain use of -set.xml file for multiplayer aircraft, for multiplayer views.) |
||
Line 35: | Line 35: | ||
{{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><variant-of></code> and <code><primary-set></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><variant-of></code> and <code><primary-set></code> tags.}} | ||
=== | === Multiplayer aircraft === | ||
In Flightgear version 2020.3.1 and later, the aircraft-set.xml file is also used when showing [[Howto:Multiplayer|multiplayer]] aircraft, as part of the implementation of Multiplayer Views [http://wiki.flightgear.org/Changelog_2020.1#Multiplayer]. For historical reasons multiplayer packets contain only the path to the aircraft model (in essence the string in the <code>/sim/model/path</code> [[Property tree|property]]), not the -set.xml file. Internally Flightgear use a heuristic to find a corresponding -set.xml file. | |||
There is also a feature that will load an AI aircraft model if it shares the same path, in essence from | There is also a feature that will load an AI aircraft model if it shares the same path, in essence from |
edits