Installation

Currently there is no automatic installation. Unzip the file REDSHIFT-0.2g.zip into the Orbiter installation folder. The next time you start Orbiter, select the Modules tab and activate the REDSHIFT module.

The example mission can be flown without any additional addons, so it works with a "vanilla" Orbiter installation. If you want to try one of the rocket or SpaceShuttle missions, you need some extra stuff installed (see Links for more information).

Upgrade

As you can see, REDSHIFT is in an early development stage and so a lot of bugs and glitches are found by people using it. I try to fix these problems as soon as I can - but this results in a frequent release of new versions.

To minimize download size for people trying new versions and that have the lastest full package (Version 0.2f) already installed, the latest upgrade REDSHIFT-Upgrade-0.2g.zip can be downloaded here (please unzip the archive into the ...\Orbiter folder of your installtion).

v0.2g Sep, 25. 2003 21:15 CEST Bugfixes:
  • (Un-)Docking:
    • After undocking, the vessel now moves away from the docking port correctly for all docking directions.

  • Reentry:
    • If no base is defined in the variables of the processor, the base defined in the MapMFD is ignored.

    • Improved course correction (to target base).

  • AlignOrbit:
    • Fixed bug that caused multiple peri-/apoapsis corrections in one run.

  • Approach:
    • Less flickering thrusters while killing relative velocity.

Changes:
  • Landing:
    • The Landing processor has been reworked and now handles the "Glide" mode. This means REDSHIFT can now land shuttle-like vessels on RCS (no main or hover thrusters used). Currently the processor can not land a shuttle straight on the runway (I am working on that) - but it will land pretty close to the given base and with a smooth touch-down...

  • (Un-)Docking:
    • It is now possible to define the time we stay docked; the new variable "TimeDocked" can be used instead of "StartAt". This variable (obviously) only makes sense in fully automated missions

  • Reentry:
    • Process can now be split into two seperate processes ("deorbit burn" and "reentry") by setting the mode string in the processor definition to "Deorbit" or "Trajectory". (This split was necessary for vessels that have a separate deorbit stage like Hermes)

    • New variable "MaxRollSpeed" defines the max speed for course corrections during reentry. The default value is 4500 (m/s).

    • New variable "TurnTime" to adjust to the vessels speed of attitude change.

    • The existing variable "CompleteAt" can now be defined in terms of airspeed (e.g. "Va = 2500").

  • REDSHIFT.cfg:
    Ship properties can now be assigned based on vessel instance names also. This allows to assign properties to vessels that use a generic spacecraft / multistage DLL.

  • Scenarios:
    The SpaceShuttle and Hermes missions have been made complete "launch-to-landing" missions and make fully use of the new REDSHIFT features. Of course landing is far from being perfect (see notes above), but you can terminate the landing processor with SHIFT-T any time and land the shuttle yourself ;-)

  • Mission charts:
    All new missions will include "mission charts" that explain how to sucessfully run that REDSHIFT mission. Charts for the "Shuttle to ISS" and "Hermes to ISS" missions are included in this release.

More history...