580
edits
Aircraft-set.xml: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 122: | Line 122: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
The aircraft rating, | The aircraft rating, using the the criteria outlined in the article [[Aircraft rating system]], which gives a (reasonably) objective rating based on the availability and quality of various aspects of the aircraft. | ||
==== Authors & Maintainers ==== | ==== Authors & Maintainers ==== | ||
| Line 130: | Line 130: | ||
<author><!-- Name of author (development area), Name of author (development area), etc. --></author> | <author><!-- Name of author (development area), Name of author (development area), etc. --></author> | ||
<!-- new in | <!-- new in FlightGear 2018.3.0 style --> | ||
<authors> | <authors> | ||
<author n="0"> | <author n="0"> | ||
| Line 253: | Line 253: | ||
Previews are tagged to allow automatic selection for certain use cases. It's recommended to include at least one exterior, daytime shot of the aircraft, and one interior shot fo the main instrument panel from the pilot's viewpoint. Beyond this any image of the aircraft is acceptable. Avoid including logo, badge or text elements in preview images since this gives poor quality results and restricts how the images can be used - different uses of the images will composite their own elements on top. | Previews are tagged to allow automatic selection for certain use cases. It's recommended to include at least one exterior, daytime shot of the aircraft, and one interior shot fo the main instrument panel from the pilot's viewpoint. Beyond this any image of the aircraft is acceptable. Avoid including logo, badge or text elements in preview images since this gives poor quality results and restricts how the images can be used - different uses of the images will composite their own elements on top. | ||
Preview file paths are relative to the -set.xml file. Permitted types at present are | Preview file paths are relative to the -set.xml file. Permitted types at present are <code>exterior</code> and <code>panel</code> - 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 <code>splash</code> tag to <code>false</code>. | ||
==== Flight-model (FDM) ==== | ==== Flight-model (FDM) ==== | ||
| Line 271: | Line 271: | ||
==== Startup ==== | ==== Startup ==== | ||
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 ( | 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 (containing the aircraft name) with a presumably partially-transaprent overlay, | ||
allowing more interesting graphics to be displayed on the splash screen. | allowing more interesting graphics to be displayed on the splash screen. | ||
| Line 282: | Line 282: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
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 | 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- if you'd like this added please ask on the developer mailing list. | ||
The legacy splash screen system does not use previews, but instead uses the following syntax: | The legacy splash screen system does not use previews, but instead uses the following syntax: | ||
| Line 295: | Line 295: | ||
</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. | 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. (Information added by FlightGear such as version and startup progress, is moved to avoid overlapping, and the scaling behaviour is different) | ||
==== Visual aircraft model ==== | ==== Visual aircraft model ==== | ||