67
edits
Paul Richter (talk | contribs) (multiple texture example - use clearer names) |
Paul Richter (talk | contribs) (→Models/Liveries: Change "texture" to "klm-747-texture" to emphasize that this tag is user-defined) |
||
| Line 28: | Line 28: | ||
<livery> | <livery> | ||
<name type="string">KLM Royal Dutch Airlines</name> | <name type="string">KLM Royal Dutch Airlines</name> | ||
<texture>Liveries/KLM.png</texture> | <klm-747-texture>Liveries/KLM.png</klm-747-texture> | ||
</livery> | </livery> | ||
</model> | </model> | ||
| Line 36: | Line 36: | ||
In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft. | In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft. | ||
Note that the texture path is relative to the model's xml in which it is used. If your aircraft's model.xml is located in <tt>Aircraft/ | Note that the texture path is relative to the model's xml in which it is used. If your aircraft's model.xml is located in <tt>Aircraft/../XML/</tt> for example, you'll have to use | ||
<texture>/../Models/Liveries/KLM.png</ | <klm-747-texture>/../Models/Liveries/KLM.png</klm-747-texture> | ||
The <tt>/../</tt> indicates the FlightGear should "move" one directory up. You can add more than one of these, depending on your directory structure. | The <tt>/../</tt> indicates the FlightGear should "move" one directory up. You can add more than one of these, depending on your directory structure. | ||
edits