Version 0.2c -- July, 19. 2003 03:00 CEST
Bugfixes:
-
Launch: Multi-vessel support broke the rocket launch mode - fixed.
-
Profile: Unaligned ascent if no reference plane is defined.
-
FltOp Manager: New name for the REDSHIFT MFD in the selection menu.
|
Version 0.2b -- July, 18. 2003 01:30 CEST
Bugfixes:
-
Reentry: Crash at process start fixed.
-
SyncOrbit: Main engine burn problem fixed.
-
Atlantis: Put the wrong files into 0.2a (sorry). Modified FOP
to make use of new Profile parameters.
-
Launch: Mode "Hover" - Smooth operation of hover thrust during lift-off and
delay of re-orientation until safety altitude is reached.
Changes:
-
Profile: The Ascent processor has two new parameters. MaxG
limits the acceleration to a defined limit and LockVz controls
the pitch at the "end" of the profile to keep a vertical velocity close to zero.
|
Version 0.2a -- July, 17. 2003 01:30 CEST
This is a major upgrade! Many features (and a lot of kernel stuff) has changed,
so make sure you read the enhanced manual on how to use REDSHIFT.
I hope that this version is not too instable although it changed dramatically (inside)... But at
least I can put a feature freeze on the project and spent the rest of the time on bug hunting.
Changes:
-
Multi-vessel support
REDSHIFT now handles an independent autopilot for every vessel in an Orbiter
scenario. This allows to fly more than one vessel automatically in one session
or to fly one (or more) vessels on autopilot and one vessel manually.
-
Reworked user interface
There is a consistent button handling for processes now that allows the user to terminate,
run and stop processes at any time.
|
Version 0.1i -- July, 14. 2003 01:30 CEST
Changes:
-
REDSHIFT can now use a user-defined key to button mapping. Some vessels (like SpaceShuttles and
many rockets) use the default keys used by REDSHIFT for their own purpose and don't check
for MFD shift keys. This results in some mess-up with some spacecraft. So you can now map
the keys you want to the REDSHIFT MFD buttons.
|
Version 0.1h -- July, 13. 2003 08:30 CEST
Changes:
- The Launch processor now avoids the drop at the beginning of the launch
by operating the hover thruster a bit longer. It is a less spectacular launch when
viewed from outside - but some crafts didn't make it into the sky, so safety first!
New stuff:
- The AlignOrbit processor has new variables that allow more
orbit parameters to be aligned from a reference or via direct specification
(more details)
- The SyncOrbit processor has new variables also (more details).
This allows to control how much fuel you will spend on the interception.
|
Version 0.1g -- July, 11. 2003 04:30 CEST
This release now includes a SpaceShuttle-specific extension DLL. Currently
this REDSHIFT extension allows you to launch the shuttle into orbit - so docking,
reentry and landing (other shuttle specific processes) have still to be done.
The ascent profile for the shuttle that comes with the version is just a quick
shot to get you into orbit. I will leave it "as an exercise to the reader" to
make a better one ;-)
|
Version 0.1f -- July, 10. 2003 17:00 CEST
I have been able to reproduce the freeze when REDSHIFT switches from Launch
to Ascend mode (that problem was still reported with 0.1e). So please test
this version if you had freezes yourself.
The only other thing changed is in a part not used until now and involves the
external processor interface. The processors for the SpaceShuttle (Launch,
Docking and Landing) I am currently working on, will be put into an external
processor DLL that get loaded by REDSHIFT on demand. This will also be the way
for external developers to write spacecraft specific processors.
|
Version 0.1e -- July, 9. 2003 14:00 CEST
Major bugfixes:
-
The crashes and freezes that people still report made me curious. I now
believe that it was my variable handling in the MFD update() method. This
is plausible since there seems to be relation to the MFD refresh rate
(which defines how often the update() method is called). So I reworked
every processor to check everything is in place as it should.
If you had crashes or freezes please check this version and report remaining
problems back. Thanks a lot.
-
I have reworked the Landing processor (guess I messed it up
in the last version). The Deltaglider now behaves more like a plane
and comes "sailing" in to Baikonur. The last part of the approach now lands
you right in the middle of the pad. Still not what it could be, but much
better than before (see Landing).
Minor bugfixes:
- The Undock process now has a consistent timeline. There was some confusion
about a wrongly displayed time (overrunning the "time to undock" clock) which is
fixed now.
The new module also fixes the "problem" that OrbiterSound only reports "undocking"
and plays the "lock mechanism" sound when a vessel is undocked and not at
docking position, so REDSHIFT is now accelerating after undocking just a bit to
fulfill that need.
|
v0.1d -- July, 8. 2003 06:30 CEST
Major bugfixes and improvements (hopefully)
- The Launch processor can now handle the Ariane 5
scenario (until now it tried to start the Ariane5 with a hover
engine and the booster rockets on ;-)
- I am working hard on the "crash to desktop" problem people have
reported. One thing seems to be switching scenarios without quiting Orbiters
Launchpad dialog in between. I made some changes to trigger a reset on the
module if a scenario is switched.
-
There was a problem that processes didn't switch correctly if you have the
REDSHIFT MFD turned off or are in an outside (external) view. This should work
now, so it should now be possible to view the complete mission from outside.
|
v0.1c -- July, 7. 2003 16:30 CEST
The problem with the Deltaglider at launch ("flipping over") is fixed.
|
v0.1b -- July, 7. 2003 08:50 CEST
Minor changes and bugfixes applied:
- The Launch processor now turns slower to the
final launch attitude (pitch) giving the vessel more
time to take up speed and to use aerodynamic lift during
launch.
- The SyncOrbit processor now stops time acceleration
correctly if the closest approach is before the calculated time.
|
v0.1a -- July, 6. 2003 16:50 CEST
Initial pre-alpha test release
|