FlightGear configuration via XML: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(+related content; cat sort)
(Rewriting the article)
Line 1: Line 1:
{{stub}}
{{stub}}
You can set up a '''FlightGear configuration via XML''' by creating a XML file that loads on to of FlightGear's other settings.


Next to using graphical launchers like [[FGRun]] or [[FGx]] or parsing console commands to FlightGear's binary, FlightGear's configuration can also be set by means of two .xml files.
Next to using graphical launchers like [[FGRun]] or [[FGx]] or parsing console commands to FlightGear's binary, FlightGear's configuration can also be set by means of two .xml files.


== preferences.xml ==
== preferences.xml and autosave.xml ==
This is FlightGear's main configuration file and located within [[$FG_ROOT]]. It contains nearly all options that can be set, enabled or disabled to configure FlightGear to the user's preference. All options contained within this file get parsed to FlightGear's binary file upon its startup.
FlightGear installs with a configuration already set up in a XML file, <code>preferences.xml</code>. Some of these settings are preserved between FlightGear sessions in another file, <code>autosave.xml</code>. All settings contained in these two files get parsed by FlightGear while it starts up.


=== Personalized settings ===
Some of the properties in <code>preferences.xml</code> have an XML attribute, <code>userarchive</code>, that automatically add any changes of those properties to <code>autosave.xml</code>.
If you are doing modifications to preferences.xml, keep in mind that those might cause problems with your FlightGear installation and that changes to these files will be lost when you install a newer version of FlightGear or uninstall FlightGear.


In order to have your settings separated from preferences.xml and be used instead of the default settings you could add your changes to a separate configuration file and adding this command-line parameter either in .fgfsrc or when you start FlightGear:
=== preferences.xml ===
<code>preferences.xml</code> is FlightGear's main configuration file and is located within [[$FG_ROOT]].  Using the [[PropertyList XML files|property-list]] format it sets up a large number of [[Property tree|properties]] and their values that determines various settings of FlightGear. It more or less contain all settings that can be set.  All settings contained within this file get parsed by FlightGear while it starts up.


--config=/home/<user name>/.fgfs/<my-preferences>.xml
=== autosave.xml ===
<code>autosave.xml</code> is a child of <code>preferences.xml</code> in user space that contains the properties with an <code>userarchive="y"</code> attribute. Location depends on the operating system used:
 
{| class="wikitable"
! OS !! Path
|-
| Windows Vista/7/8
| <code>C:\Users\{Your username}\AppData\Roaming\flightgear.org\</code>
|-
| Windows XP
| <code>C:\Documents and Settings\{Your username}\Application Data\flightgear.org\</code>
|-
| Linux/OS X
| <code>~/.fgfs</code>
|}
 
If not present, it is generated upon launching FGFS with the options set in its parent file Preferences.xml.
 
Any changes you do within FlightGear's user interface are saved into <code>autosave.xml</code>, so a manual edit is, in most cases, not necessary.  The next time you launch FGFS, the settings stored in <code>autosave.xml</code> will be used.
 
== Adding your own settings ==
Rather than modifying <code>preferences.xml</code> or <code>autosave.xml</code> you should create your own configuration file using the same format and load it using the <code>--config</code> command-line parameter.  You are not limited only to use properties from those files, but can use any properties from the property tree.  You can also add entirely new properties if that is needed.


== autosave.xml ==
When you use the <code>--config</code> option to load your own configuration, it will be loaded into FlightGear just as <code>preferences.xml</code> and <code>autosave.xml</code>, but your configuration will be used instead. To use your own configuration add this command-line parameter either in <code>.fgfsrc</code> or when you start FlightGear:
autosave.xml is a child of preferences.xml in user space. Location depends on the operating system used.


* '''Windows Vista/7/8''': C:\Users\{Your username}\AppData\Roaming\flightgear.org\
--config=/home/<user name>/.fgfs/<my-preferences>.xml
* '''Windows XP''': C:\Documents and Settings\{Your username}\Application Data\flightgear.org\
* '''Linux/OS X''': ~/.fgfs


If not present, it is generated upon launching FGFS with the options set in its parent file Preferences.xml.
The reason to why you should not modify <code>preferences.xml</code> or <code>autosave.xml</code> is that the modifications can cause problems with your FlightGear installation and, unless you manually make a copy of them, they will be lost when you upgrade or uninstall FlightGear.  In addition, using a configuration file from one version of FlightGear with another version may not work too well either.
Any changes you do within FlightGear's user interface are saved into autosave.xml, so a manual edit is, in most cases, not necessary.
The next time you launch FGFS, the settings stored in autosave.xml will be used.


== Related content ==
== Related content ==

Revision as of 12:14, 19 May 2015

This article is a stub. You can help the wiki by expanding it.

You can set up a FlightGear configuration via XML by creating a XML file that loads on to of FlightGear's other settings.

Next to using graphical launchers like FGRun or FGx or parsing console commands to FlightGear's binary, FlightGear's configuration can also be set by means of two .xml files.

preferences.xml and autosave.xml

FlightGear installs with a configuration already set up in a XML file, preferences.xml. Some of these settings are preserved between FlightGear sessions in another file, autosave.xml. All settings contained in these two files get parsed by FlightGear while it starts up.

Some of the properties in preferences.xml have an XML attribute, userarchive, that automatically add any changes of those properties to autosave.xml.

preferences.xml

preferences.xml is FlightGear's main configuration file and is located within $FG_ROOT. Using the property-list format it sets up a large number of properties and their values that determines various settings of FlightGear. It more or less contain all settings that can be set. All settings contained within this file get parsed by FlightGear while it starts up.

autosave.xml

autosave.xml is a child of preferences.xml in user space that contains the properties with an userarchive="y" attribute. Location depends on the operating system used:

OS Path
Windows Vista/7/8 C:\Users\{Your username}\AppData\Roaming\flightgear.org\
Windows XP C:\Documents and Settings\{Your username}\Application Data\flightgear.org\
Linux/OS X ~/.fgfs

If not present, it is generated upon launching FGFS with the options set in its parent file Preferences.xml.

Any changes you do within FlightGear's user interface are saved into autosave.xml, so a manual edit is, in most cases, not necessary. The next time you launch FGFS, the settings stored in autosave.xml will be used.

Adding your own settings

Rather than modifying preferences.xml or autosave.xml you should create your own configuration file using the same format and load it using the --config command-line parameter. You are not limited only to use properties from those files, but can use any properties from the property tree. You can also add entirely new properties if that is needed.

When you use the --config option to load your own configuration, it will be loaded into FlightGear just as preferences.xml and autosave.xml, but your configuration will be used instead. To use your own configuration add this command-line parameter either in .fgfsrc or when you start FlightGear:

--config=/home/<user name>/.fgfs/<my-preferences>.xml

The reason to why you should not modify preferences.xml or autosave.xml is that the modifications can cause problems with your FlightGear installation and, unless you manually make a copy of them, they will be lost when you upgrade or uninstall FlightGear. In addition, using a configuration file from one version of FlightGear with another version may not work too well either.

Related content