SSU Development Thread (2.0 to 3.0)

Status
Not open for further replies.
OK, just finished the commit (after correcting a few things). What I need now is somebody to correct the position of the 5 vents at the rear of the orbiter (in function CreateMPSDumpVents in Atlantis.cpp line 7747)
Is there quick test scenario I could use to check the positions?
 
Is there quick test scenario I could use to check the positions?

nop, you have to launch and after MECO the vents will become active. First the LH2 B/U dump vlv right after MECO (I know timing is not correct), then at MECO + 120sec the LH2 F/D vlv opens and the LOX dump thru the SSMEs start.
 
The positions have been updated and the code checked in.
 
The positions have been updated and the code checked in.

Thanks! :thumbup:
Just one more think: could you move the LOX dump position to the end of the SSME nozzles? As it is, it vents "around" the nozzles...
 
Thanks! :thumbup:
Just one more think: could you move the LOX dump position to the end of the SSME nozzles? As it is, it vents "around" the nozzles...
Done and checked in.
 
I wouldn't go that far.:uhh:
 
Checked in improved sounds for the orbiter AC and switch throws. Panel R13L doesn't trigger the switch throw sound when the switches are operated.
 
I have one little (big) request to who is working on the new cockpit mesh in the VC branch: please add panel R4, and then add another POV (or whatever it is called... the "AltGr + Arrow" POV move) on the pilot side so that panel becomes more visible, because the current left-most POV (over panel R2) is not very good.
Thanks in advance :tiphat:
 
Just noticed this, in panel C3 both the "SRB SEPARATION" and "ET SEPARATION" controls have a typo and show "SRB SEPERATION" and "ET SEPERATION".
 
Just noticed this, in panel C3 both the "SRB SEPARATION" and "ET SEPARATION" controls have a typo and show "SRB SEPERATION" and "ET SEPERATION".

Should be an easy fix.
 
API

Are there any plans to implement an API (like XRVesselCtrl) in SSU, so that add-ons like Orb::Connect can be used to access spacecraft status?
 
Are there any plans to implement an API (like XRVesselCtrl) in SSU, so that add-ons like Orb::Connect can be used to access spacecraft status?

Poscik had implemented something in that direction, but no full telemetry stream.
 
I'm currently working on updating the STS-107 payloads meshes to fit the new orbiter. So far everything is going nicely. I am currently in the need for a new texture for the EDO cryo kit. I'm remaking it as the old one was not accurate. And it would be nice with a fresh new better looking texture on it as well.
 
Thanks. Where can I find this?

It was just my simple experiment with OGRE rendering engine. I made something like 3D Telemetry Visualisation, but It was only able to show position and orientation of the shuttle. In fact it is completely useless and I even don't have source code of it :)
 
Just commited code that added OAA extend in case of abort, and noticed that both OAA retract and extend are too slow: it takes over 3 minutes to retract when it should take around 120sec (from TV) or 150sec (from LCC): and the extend should take 15sec (TV) or 20sec (LCC) (at least an emergency extend). Anybody want to take this, or shall I correct it?
 
Just commited code that added OAA extend in case of abort, and noticed that both OAA retract and extend are too slow: it takes over 3 minutes to retract when it should take around 120sec (from TV) or 150sec (from LCC): and the extend should take 15sec (TV) or 20sec (LCC) (at least an emergency extend). Anybody want to take this, or shall I correct it?

Forget it, just commited the necessary changes.
 
Can Edwards be added as an available landing site in SSU? I have a working Edwards base with Landsat imagery which I can check in if there's interest:

SSU_EDW_RWY22_WIP.jpg
 
looks awefully blue-ish.
 
Can Edwards be added as an available landing site in SSU? I have a working Edwards base with Landsat imagery which I can check in if there's interest:
Yes. I think the only change needed will be to add Edwards to the list of available landing sites in the AerojetDAP code. At some point we should start reading this from a config/mission file instead of hard coding the list of landing sites.
 
Status
Not open for further replies.
Back
Top