## Configuration

All configuration data as well as the flight operation plans are stored in files in a directory. REDSHIFT expects that this directory is named FOP and that it is located in the Orbiter folder.

The format of all files (regardless of their extension) is XML-based. To edit existing files (or to create new ones), you need a plaintext editor (like Windows notepad) and some basic knowledge of XML itself.

### RedShift.cfg

The basic configuration file is `./FOP/RedShift.cfg` and it is parsed when you start Orbiter (the Launchpad dialog actually) with the REDSHIFT module activated. The configuration file allows to define the keys used with the REDSHIFT MFD in a scenario and some vessel-specific FOP repositories.

#### <Setup> section

The <Setup> section of the config file has two definitions:

      <Setup>
        <Activation> F </Activation>
        <Keys> 1234567890-= </Keys>
      </Setup>

The Activation key let you specify the key which will be used to activate the REDSHIFT MFD. The default is SHIFT-F but can be changed if you are using another MFD that uses the same key.

You will interact with the MFD with the help of buttons (displayed at the side of the MFD if your vessel has a panel) or via keyboard commands (LSHIFT, RSHIFT keys). The default setting is that all buttons are mapped to the "numeric row" on the keyboard:

(If you have a non-US keyboard layout, the last two keys may have a different character assigned than displayed. Make sure you are using the two keys right of "0" and not the MINUS and EQUAL keys on your keyboard!)

The Keys string let the user define a twelve-character string that maps the twelve MFD buttons to keys. The left-side buttons map to characters 0 to 5 (top down), the right-side buttons map to characters 6-11. Spaces are allowed and are not counted as keys. If you want a NULL assignment for a button (because it is not used), use an underscore as an assignment.

An example is my current setup: The MFD is activated with SHIFT-Z, and only assigned buttons are mapped to keys - Terminate, Stop, Run, Manual, Back, Up, Down, SElect and Configuration.

      <Setup>
        <Activation> Z </Activation>
        <Keys> TSRM__BUDE_C </Keys>
      </Setup>

#### <Vessel> section

The <VesselList> section let the user define vessel-specific mission files. The default entry (marked by class *) associates the default mission file with (any) vessel:

      <Ship class="*">
        <XFlights> ./FOP/Missions.lst </XFlights>
      </Ship>

In case you want all DeltaGlider missions to be listed in one file, you could add the following entry:

      <Ship class="DeltaGlider">
        <XFlights> ./FOP/DG_Missions.lst </XFlights>
      </Ship>

Whenever you switch on the REDSHIFT MFD in a DeltaGlider, you would now see the DeltaGlider missions in the main menu. Of course you have to write your own DG_Missions.lst file for this to work.