Aircraft-set.xml: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 213: Line 213:


Preview file paths are relative to the -set.xml file. Permitted types at present are 'exterior' and 'panel' - the type can also be committed. By default all previews are considered for random selection as the splash screen - to prevent a particular preview being used as the splash screen, set the 'splash' tag to false.
Preview file paths are relative to the -set.xml file. Permitted types at present are 'exterior' and 'panel' - the type can also be committed. By default all previews are considered for random selection as the splash screen - to prevent a particular preview being used as the splash screen, set the 'splash' tag to false.
==== Flight-model (FDM) ====


<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
Line 226: Line 228:
The filename of the FDM file, without <code>.xml</code>.  For instance, if your FDM file is sopwithCamel1F1.xml, the aero section would look like <code><nowiki><aero>sopwithCamel1F1</aero></nowiki></code>.
The filename of the FDM file, without <code>.xml</code>.  For instance, if your FDM file is sopwithCamel1F1.xml, the aero section would look like <code><nowiki><aero>sopwithCamel1F1</aero></nowiki></code>.


The next section is the <code><startup></code> section, which can contain two elements:
==== Startup ====


<syntaxhighlight lang="xml">
The startup section contains information used to show the splash screen for your aircraft. The recommend approach is to use the previews system described above, optionally marking some previews as suitable or unsuitable for use as a splash screen. When using the previews system to provide a splash screen, you can optionally provide a logo image. This replaces the default text (with the aircraft name) with a presumably partially-transaprent overlay,
  <splash-texture><!-- File path --></splash-texture>
allowing more interesting graphics to be displayed on the splash screen.
</syntaxhighlight>
 
Path to an image you would like to show during loading of the aircraft. FlightGear will randomly pick one of the generic splashes in <code>[[$FG ROOT]]/Textures/</code> when this line is not found in the aircraft-set.xml file.


<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
   <splash-title><!-- Title --></splash-title>
   <sim>
    <startup>
        <splash-logo-image>beechcraft-logo.png</splash-logo-image>
    </startup>
</sim>
</syntaxhighlight>
</syntaxhighlight>


A small text to be shown above the splash texture during loading of an aircraft.
When using a logo image, it should be a PNG with an alpha channel enabled, and will be blended over the selected preview image automatically. At present the placement is hard-coded, but this could be extended in the future - if you'd like this added please ask on the developer mailing list.


Example:
The legacy splash screen system does not use previews, but instead uses the following syntax:


<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
<startup>
  <sim>
  <splash-texture>images/splash.jpg</splash-texture>
    <startup>
  <splash-title>My Aircraft!</splash-title>
          <splash-texture n="0"><!-- File path --></splash-texture>
</startup>
          <splash-texture n="1"><!-- File path --></splash-texture>
    </startup>
</sim>
</syntaxhighlight>
</syntaxhighlight>


Because old splash screens typically included text and logo elements, the splash screen appearance is different in this case, to ensure all text is legible.
==== Visual aircraft model ====


<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
580

edits

Navigation menu