XR Flight Operations Manual Version 3.0
Copyright 2006-2018 Douglas Beachy. All Rights Reserved.
17
By default each XR vessel is installed with all damage settings
enabled
, which means
that it is now quite possible to
destroy your ship if you don’t watch what you’re
doing. However, damage detection and simulation is fully configurable via your
vessel’s configuration file
, and you are free to turn any particular damage type on or
off as desired (
hull heating, hard landings, crashes, etc.
) If you turn off
all
damage
settings, your XR vessel will be as forgiving as the default DeltaGlider included with
the Orbiter core installation.
This allows novice pilots to “ease into”
realistic flight
gradually as they progress.
Note: XR configuration files are simple text files that you can edit with your favorite
text editor (e.g., Notepad)
. The default XR vessel configuration files are shown in
the table below:
XR Vessel
Configuration File
DeltaGlider-XR1
$ORBITER_HOME\Config\DeltaGliderXR1Prefs.cfg
XR2 Ravenstar
$ORBITER_HOME\Config\XR2RavenstarPrefs.cfg
XR5 Vanguard
$ORBITER_HOME\Config\XR5VanguardPrefs.cfg
For example, to configure (disable) different types of ship damage you would edit the
following parameters in your XR vessel’s configuration file
and set one or more to
zero to disable damage detection for that subsystem:
#----------------------------------------------------------------------
# Enable or disable ship damage due to wing stress, hull heating,
# hard landings, crashes, excessive dynamic pressure, and SCRAM
# engine overheat.
# 0 = damage disabled
# 1 = damage enabled
#---------------------------------------------------------------------
WingStressDamageEnabled=1
HullHeatingDamageEnabled=1
HardLandingsDamageEnabled=1
CrashDamageEnabled=1
DoorStressDamageEnabled=1
ScramEngineOverheatDamageEnabled=1
EnableDamageWhileDocked=1
In addition to editing the default configuration file for your XR vessel, which affects
all
of those types of vessels in
all
your scenarios (i.e., editing
$ORBITER_HOME\Config\DeltaGliderXR1Prefs.cfg
will affect all of your XR1
vessels in all scenarios), you can also override some or all of your default settings for
just one scenario by modifying that scenario file. There are two different methods of
doing this:
1)
Rename your XR vessel in your scenario file to match the name of a
corresponding
$ORBITER_HOME\Config\<vesselname>.xrcfg
override file, or
2)
Add one or more
CONFIG_OVERRIDE_<settingname>
settings directly to the
scenario file.
