Project Space Shuttle Vessel

Yeah and some of the order can be confusing. That's why I switched to the real FDFs once I learned what is and isn't implemented. I've been thinking about making a video on a ISS rendezvous so people can see how to use FDO MFD and tune a maneuver plan. And maybe a video about creating a maneuver plan for a rendezvous, since that is a beast in its own regard.
That would be a valuable video.
 
I think the hardest part of the FDO MFD is the initial trial and error part before OMS2 to get the Ti sunset timing correct. So for me personally, that's what I'd like to see, but would welcome anything additional.
 
I think the hardest part of the FDO MFD is the initial trial and error part before OMS2 to get the Ti sunset timing correct. So for me personally, that's what I'd like to see, but would welcome anything additional.
yeah it took me a few reads to figure it all out haha. ill prob do 3 parts: Ascent, OMS-2 planning through docking, and then undocking and return.
 
The Cape terrain in Orbiter might look flat but absolutely isn't. It's riddled with uneven spots.
 
yeah it took me a few reads to figure it all out haha. ill prob do 3 parts: Ascent, OMS-2 planning through docking, and then undocking and return.
That would be really cool to see those. I know it's not easy making videos like that, and can eat up valuable free time, but they'd be helpful on many levels.
 
So, I'm a life long MSFS user going back to the earliest versions, and a part time Orbinaut going back to Orbiter 2006. Like a lot of people, I drift in and out of Orbiter. I messed around with SSU back in the day, and was waiting on Orbiter 2024 to release, and SSV to move to the new Orbiter version.

Up until now I've been just playing around with SSV scenarios, nosing around the checklists, and just getting reacquainted with everything in general. With that said, I have an embarrassing question to ask. Can someone please give me a hint on how to set the DAP, and anything else required, to get the keyboard numpad RCS working? I loaded up a test scenario from the SSV package...I think it's the "Atlantis on orbit" scenario...and thought I'd try a little RCS maneuvering. You have no idea how much time I've spent trying to figure this out myself but to no avail, so I wouldn't have to ask here and look foolish. But, here we are. :confused:
 
Up until now I've been just playing around with SSV scenarios, nosing around the checklists, and just getting reacquainted with everything in general. With that said, I have an embarrassing question to ask. Can someone please give me a hint on how to set the DAP, and anything else required, to get the keyboard numpad RCS working? I loaded up a test scenario from the SSV package...I think it's the "Atlantis on orbit" scenario...and thought I'd try a little RCS maneuvering. You have no idea how much time I've spent trying to figure this out myself but to no avail, so I wouldn't have to ask here and look foolish. But, here we are. :confused:

So, usually in orbit the manual maneuvering would be done on the aft station (e.g., proximity ops, docking), and so the 2 forward DDUs (which power the controllers) would be turned off to save power (not a thing in SSV, but it was in real life). If you check panels O14, O15 and O16, the CBs for left and right DDUs are pulled, and only the aft DDU is on (maybe I forgot to update all scenarios, but that one only has the aft DDU powered).
So, a DDU must be powered for the corresponding controllers to work. Then there's the more common on/off control of controllers which is the Flt Cntlr Power switch/lever at each station, which would be on when manual control is/might be needed, and turned off when it is not (e.g., it would be turned off very soon after docking).
Then there is another "layer" to take into account: which station has which controls and where is the user located. The CDR station has the RHC, THC, SBTC and RPTA, but the PLT station does not have a THC, and the aft station only has the RHC and THC, and only when in those positions will the existing controls be available, so no control is possible from the MS2 position.
In the end you have the DAP part (might not be 100% accurate, as I haven't really ventured into the inner workings of this area):
  • DAP A or B, for different deadbands, translation pulse lengths, rotation rates, etc, defined in SPEC 20;
  • Auto, which will have the GPC do whatever is configured, Inrtl for inertial attitude hold, LVLH for LVLH att hold, and Free to let the vehicle att drift;
  • Translation controls: Norm for continuous firing while an input is made, or Pulse for just a pulse per input;
  • Rotation controls: Pri, Alt or Vern for which set of thrusters to fire, Disc Rate to rotate the vehicle up to a certain rate while and input is present, vs Pulse which will just pulse the thrusters once per input.
 
Thanks for that! I'll get back at it tonight.

Edit: Well, it was the CB's pulled on the test scenario. I did a few launch tests, and was able to tool around with the RCS and DAP. I need to read up on the RCS system to figure out how to null the rates. I miss the old orbiter sound addon that used to speak "rotation!" "translation"....LOL. I need to figure out how to tell which mode I'm in.
 
Last edited:
I've experienced this as well, so I believe it is some terrain issue
I made a couple of landings there and it was flat... I'll have to check the Terrain Editor.
 
Back
Top