OHM OFSS III - Flight Package #16

OrbitHangar

Addon Comments
Joined
Apr 9, 2008
Messages
3,832
Reaction score
18
Points
0

Author: tex

Orbiter Forum Space Station III (OFSS) is a community project with lots of orbinauts participating! This package contains everything you need to begin.

*Be sure you read the documention included for the required addons, flight objectives, and general information you will need! Each flight has its own page in the documentation with details about the flight. They will be updated with each new flight released, so refer back to the documention for your flight objectives when it is released. You will also find the flight objectives listed in the scenario descriptions.


Release History:

v16 - Flight #16 package released.
v15 - Flight #15 package released.
v14 - Flight #14 package released.

  • OFSS-HabitatModule4 config updated.
  • Fuel added to OFSS-Core.
v13 - Flight #13 package released.
v12 - Flight #12 package released.
v11 - Flight #11 package released.
v10 - Flight #10 package released.
v9.0 - Flight #9 package released.

  • Typo in flight #8 objectives fixed.
v8.0 - Flight #8 package released.
v7.0 - Flight #7 package released.

  • Due to inclination, Ariane5 guidance config has been edited.
v6.0 - Flight #6 package released.
v5.0 - Flight #5 package released.

  • URMS grapple bug info added to page 6 in the documentation.
  • Neesys2 config edited for less attitude thrust.
v4.0 - Flight #4 package released.
v3.0 - Flight #3 package released.
v2.0 - Flight #2 package released.
v1.1 - Fixed first scenario guidance file.
v1.0 - Initial package release (Flight #1).

DOWNLOAD
 
Thanks for releasing this! I'll fly this tomorrow, and post all of the results in their respective places.

There's one though that you missed in the package: the proton guidance file. I got a CTD at launch. I've had this problem before, and knew what was missing...
It goes into ~orbiterroot\Config\Vessels\Proton_LV

I have it as an attachment here.
 

Attachments

:facepalm:

My fault. I was testing changes to the launch config file with no luck. You can use the default config file for this launch. I will update the package now. Give me one minute to fix that. Sorry!
 
Package updated. If you've already downloaded it, you only need to use this updated scenario:

Code:
BEGIN_DESC
OFSS III

Flight #1

July 6, 2011

01:00:59 UTC


Departure: Baikonur

Vehicle: Proton-K

Payload: Zarya



1.) The countdown clock is already running. Let the auto-pilot launch you into orbit with an
inclination 51.60. You don't have to do or press anything for the launch.


2.) Aim to keep the orbit altitude relatively low so it's easier for 'Zvezda' to rendezvous on
flight #4. The best way to do that is to disable the launch auto-pilot JUST as your ApA reaches
200km by quickly pressing 'M', then press * on the numpad twice, to kill all engines. 'Zarya'
separation will then occur.


3.) Once in orbit, press Ctrl+1 and Ctrl+2 to deploy the solar panels and antennas on 'Zarya'.


4.) Raise the orbit altitude so it's at least 200km, but no higher than 230km at this point. We
also don’t need to worry about getting the eccentricity to 0, just relatively low.

END_DESC

BEGIN_ENVIRONMENT
  System OFSS-Sol
  Date MJD 55748.040625
END_ENVIRONMENT

BEGIN_FOCUS
  Ship P2
END_FOCUS

BEGIN_CAMERA
  TARGET P2
  MODE Extern
  POS 8.64 81.36 -3.29
  TRACKMODE Ground Earth
  GROUNDLOCATION 62.98882 46.06999 13.76
  FOV 30.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Surface
  SPDMODE 1
END_MFD

BEGIN_MFD Right
  TYPE Orbit
  PROJ Ship
  FRAME Equator
  ALT
  REF Earth
END_MFD


BEGIN_SHIPS
Zarya:ISSR\Zarya
  STATUS Orbiting Earth
  PRPLEVEL 0:0.500 1:0.500
  MSSTATE 1
END
Fairing1:Proton_LV/fairing
  STATUS Landed Earth
  PRPLEVEL 0:1.000
  MASS 1100
  MESHNAME Proton_LV\KTYPE1
END
Fairing2:Proton_LV/fairing
  STATUS Landed Earth
  PRPLEVEL 0:1.000
  MASS 1100
  MESHNAME Proton_LV\KTYPE1
END
P3:Proton_LV/P3
  STATUS Landed Earth
  PRPLEVEL 0:1.000 1:1.000
  GUIDANCE
  TRAJECTORY Config\Vessels\Proton_LV\ZG.txt
  TYPE 0
  PAYLOAD Zarya
  PREF -0.007 0.01 0.3
  FAIRING1 Fairing1
  FREF1 0 -2.31 -0.5
  FAIRING2 Fairing2
  FREF2 0 -2.31 -0.5
  FROT2 -1 0 0
END
Skirt:Proton_LV/Skirt
  STATUS Landed Earth
  TYPE 0
END
P2:Proton_LV/P2
  STATUS Landed Earth
  PRPLEVEL 0:1.000 1:1.000
  GUIDANCE
  TRAJECTORY Config\Vessels\Proton_LV\ZG.txt
  TYPE 0
  DATA 1 0
  PAYLOAD P3
  SKIRT Skirt
  FOCUS 1
END
P1:Proton_LV/P1
  STATUS Landed Earth
  POS 63.0423200 46.0353000
  HEADING 0.00
  ATTACHED 0:0,LC81
  PRPLEVEL 0:1.000
  NAVFREQ 0 0
  GUIDANCE
  TRAJECTORY Config\Vessels\Proton_LV\ZG.txt
  TYPE 0
  PAYLOAD P2
  INCLINATION 51.60
END
LC81:Proton_LV\LC81
  STATUS Landed Earth
  POS 62.9869700 46.0708400
  HEADING 210.11
  PRPLEVEL 0:1.000
  NAVFREQ 0 0
END
kmlWriter:Proton_LV/kmlWriter
  STATUS Landed Earth
END
END_SHIPS
 
I just realized, the first mission is the easiest because you don't have to rendezvous with another object.
 
Recommend adding to the manual a note reminding people that URMS and UCD unpack to a .exe not standard files. Also recommending people use the completed station scenario to check their installation.
 
I think you just found me out.... :lol::tiphat:

You could try to change the ZG.txt trajectory file into this.
Code:
0 40 89.5 88 0
40 115 88 30 0
115 143 30 23 0
143 200 23 22 0
200 330 22 16.5 0
330 500 16.5 4.5 0
500 557 4.5 5 0
557 599 5 5 1
565 570 1.5 1 2

It should get you into a ~200 km ~circular orbit.
 
You could try to change the ZG.txt trajectory file into this.
Code:
0 40 89.5 88 0
40 115 88 30 0
115 143 30 23 0
143 200 23 22 0
200 330 22 16.5 0
330 500 16.5 4.5 0
500 557 4.5 5 0
557 599 5 5 1
565 570 1.5 1 2

It should get you into a ~200 km ~circular orbit.

Thanks for that info. I'll try that with the Zvezda flight. I couldn't find any details about setting the altitude for the auto-pilot in Thorton's documents... :shrug:

How did you figure this out?
 
How did you figure this out?

Trial and error. :lol: (and a bit of experience)
The format in the documentation is actually wrong.

Proton Launch Vehicle.pdf
Code:
[SIZE=4]
[LEFT][SIZE=2]Pitch program file format [/SIZE][/LEFT]
[/SIZE][FONT=Times New Roman,Times New Roman][SIZE=4][FONT=Times New Roman,Times New Roman][SIZE=4][LEFT][FONT=Verdana][SIZE=2]Pstart Pend Tstart Tend Stop[/SIZE][/FONT]
[FONT=Verdana][SIZE=2] [/SIZE][/FONT]
[FONT=Verdana][SIZE=2]Pstart – initial pitch value [/SIZE][/FONT]
[FONT=Verdana][SIZE=2]Pend – end pitch value [/SIZE][/FONT]
[FONT=Verdana][SIZE=2]Tstart – time when pitch maneuver start [/SIZE][/FONT]
[FONT=Verdana][SIZE=2]Tend – time when pitch maneuver end [/SIZE][/FONT][/LEFT]
[FONT=Verdana][SIZE=2]Stop – cut off value, 0 – normal flight, 1 – main engine cut off, 2 – rudder engine cut off[/SIZE][/FONT] 
[/SIZE][/FONT][/SIZE][/FONT]

From the original files I realized that the format was:
Tstart Tend Pstart Pend Stop

I'm not entirely sure about the "rudder engine" value (2) in the last line, but it doesn't make that much difference.
 
Thanks! That was most helpful. :cheers:

I sometimes have trouble finding things in his documents because they are so many, I wish it was all in one. :)
 
I completed the second flight succesfully and in under 12 hours!!!
 
hiya all,

I'd love to participate, but I can't get the package to work. I've followed the OFSS readme to the letter, with a clean orbiter install, & installed all the addons in the proper order, but I get CTD's or missing launch vehicles whenever I try to run the OFSS scenarios. the add-ons for the most part work... but there are a few that do not. help!

in the mean time I'm going to completely wipe my orbiter install & start over from scratch with the OFSS readme docs..
 
Last edited:
You must not have installed something correctly or in the wrong order. I've tested it numerous times and never had a problem. So far no one else has either. I'm afraid I can not effectively help you without more information such as the contents from your Orbiter log after the CTD.
 
Remember URMS and UCD DON'T unpack to orbiter correctly, they unpack to a .exe, which caught me out for a minute.
 
hmm, ok I'll post the orbiter log later today, (at work as I write this). I guess I should ask the question, when installing the add-ons, and asked if I want to overwrite the files present with the ones from whichever add-on I'm installing do I overwrite them? or leave them?
 
I guess I should ask the question, when installing the add-ons, and asked if I want to overwrite the files present with the ones from whichever add-on I'm installing do I overwrite them? or leave them?

Add-ons that modify files from Orbiter or other add-ons include the modified versions of those files, or instructions how to modify them to make the add-on working properly. If you install an older add-on, it's better to merge changes to those files manually than overwrite them all with older versions, as there might be some conflicts. If add-on is newer than Orbiter version, or there are no conflicting modifications from other add-ons to the overwritten files, it's safe to overwrite them.
 
If you use a clean install, and follow the instructions EXACTLY, overwriting all conflicts, you shouldn't have any problems. Just remember my tips above.
 
Back
Top