8,564
edits
Moyes Dragonfly: Difference between revisions
Jump to navigation
Jump to search
m
→Configuration: fix path reference on Windows
m (Bot: Automated text replacement (-|fgname = <tt> +|fgname = )) |
m (→Configuration: fix path reference on Windows) |
||
| Line 43: | Line 43: | ||
==== Configuration ==== | ==== Configuration ==== | ||
Do use this feature, a small configuration file is needed telling FlightGear where the banners are on the ground. It is a small XML file placed in your FlightGear home directory (which is ~/.fgfs on Linux | Do use this feature, a small configuration file is needed telling FlightGear where the banners are on the ground. It is a small XML file placed in your FlightGear home directory (which is <tt>~/.fgfs</tt> on Linux and <tt>.../Users/.../AppData/Roaming/flightgear.org/</tt> on Windows) named <tt>groundbanner.xml</tt>. Create this file and paste the following content into it; it will tell FlightGear where to put the banner: | ||
<syntaxhighlight lang="xml"> | |||
<PropertyList> | <PropertyList> | ||
<groundbanner> | <groundbanner> | ||
| Line 52: | Line 53: | ||
</groundbanner> | </groundbanner> | ||
</PropertyList> | </PropertyList> | ||
This example places one banner at KSFO left to 28R | </syntaxhighlight> | ||
This example places one banner at the runway intersection of [[KSFO]], left to 28R. There can be any number of <groundbanner> elements in the file, to place more of them. | |||
You can verify that the banners were loaded on the output of your console window. For each configured and loaded groundbanner there is a message | You can verify that the banners were loaded on the output of your console window. For each configured and loaded groundbanner there is a message | ||