XR Flight Operations Manual Version 3.0
Copyright 2006-2018 Douglas Beachy. All Rights Reserved.
19
The sample
Scenarios\XR2 Ravenstar\Configuration File Override Example
1.scn
scenario file does just that. If you open that scenario in a text editor you will
see our XR2 is named as follows:
XR2-EXAMPLE
:XR2Ravenstar
STATUS Landed Earth
POS -80.705714 28.632274
HEADING 150.00
When you rename your XR2, be sure to replace
all
the occurrences of the old vessel
name in the scenario file. For example, we also have this section near the end of the
file:
XR2-EXAMPLE
_Bay:XRPayloadBay
STATUS Landed Earth
POS -80.7098293 28.6270272
HEADING 149.98
ATTACHED 0:3,
XR2-EXAMPLE
END
XR2PayloadCHM-01-1:XR2PayloadCHM
STATUS Landed Earth
POS -80.7098140 28.6270040
HEADING 149.98
ATTACHED 0:0,
XR2-EXAMPLE
NAVFREQ 0 0
END
When that XR vessel loads in Orbiter, it will check whether a preference override file
exists with this name:
$ORBITER_ROOT\Config\
XR2-EXAMPLE
.xrcfg
(the filename is
case-insensitive). If the file exists, it will be read and any preference settings in it
applied
after
the default configuration file is processed. Any XR vessels in any
scenarios with the name
XR2-EXAMPLE
will use that
.xrcfg
file, so once the .
xrcfg
file is created you need only rename your XR vessel in a given scenario to match in
order for it to use that configuration override file. This lets you share a single
configuration file across multiple scenarios, so if you want to make a change to those
settings you only need to edit the
.xrcfg
file to have it affect all scenarios (vessels)
that use it; this is easier than editing each individual scenario file separately.
In our example here, our
XR2-EXAMPLE.xrcfg
override file contains these settings
(comments snipped for brevity):
[GENERAL]
MainFuelISP=5
LOXLoadout=5
APUFuelBurnRate=1
All other preferences will use their default values as specified in the default
configuration file,
$ORBITER_HOME\Config\XR2RavenstarPrefs.cfg
.
