SSU Launch Complex 39 development

Have a question: How detailed do you want the FSS? Should I add the handrails on each FSS level? If not, then I can move on to the Emergency Escape System on the west side of the 195' level.
 
Have a question: How detailed do you want the FSS? Should I add the handrails on each FSS level? If not, then I can move on to the Emergency Escape System on the west side of the 195' level.

I think only the level of the crew access arm needs to be made really detailled, the rest can be made at lower details.
 
I think only the level of the crew access arm needs to be made really detailled, the rest can be made at lower details.
OK. So will skip the handrails and just go for general exterior detail.


-----Posted Added-----


OK, the EES structure is nearly completed. Donamy: do you think you could come up with some nice baskets?
 
Pretty much done with the EES structure. Screenshot have been attached:
 

Attachments

  • SSU_FSS_19A.jpg
    SSU_FSS_19A.jpg
    134 KB · Views: 670
Looks fantastic. Can't wait to see it in action. :)
 
Maybe you could then add the ROFIs on the MLP? They fire at T-10 and lasts for 10 seconds.
I'm working on the ROFIs at the moment. Should they be triggered by the LCC or the RSLS?
 
I'm working on the ROFIs at the moment. Should they be triggered by the LCC or the RSLS?
RSLS. RSLS Main Engine start sequence is 3, 2 and 1. For a lift-off to occur SSME Pc must be >90% in 4.6 seconds of engine start command.


-----Posted Added-----


And there's a total of 6 ROFIs mounted on the TSMs, 3 on each TSM. One on the forward side of the TSMs and two on the backside of the TSMs.
 
New check-ins:
-Canaveral.cfg: Adjusted the Y-offset for the water tower to correct the height.
-LC39A_hardstand.msh: Lots of fixes and additions! Mainly of the GH2 vent pipe that runs along the south face of the FSS, rounds the north side of the MLP and down into the hardstand. Also added the MLP LH2 fill/drain pipes.
 
Hi, I hope this is in the right place but I was reading talk of GLS in this thread. Would it be possible to have some manual control over the GLS, so you can call a hold and then resume or cutoff and recycle to T-20 minutes? I think in the long term there could be potential for a CGLS console that could be controlled by another person, in effect a virtual launch control. Please note that this is just a question and I understand that you are busy working on Space Shuttle Ultra and may not have time from this.
 
Now that STS-126/ISS ULF2 is over, I have returned to finish up LC-39. Just need to know just how detailed you want the RSS. I have redone the RSS truss structure and so far it's shaping up to be really nice and alot more accurate.
 
Now that STS-126/ISS ULF2 is over, I have returned to finish up LC-39. Just need to know just how detailed you want the RSS. I have redone the RSS truss structure and so far it's shaping up to be really nice and alot more accurate.

For the beginning, not too detailled. We will add more stuff quickly, but I hope we can manage it a bit better as on the Shuttle, for improving our framerates.
 
For the beginning, not too detailled. We will add more stuff quickly, but I hope we can manage it a bit better as on the Shuttle, for improving our framerates.
OK, so I'll just keep the animated parts(mostly the OWPs) and simplify the rest. No handrails or anything.
 
OK, so I'll just keep the animated parts(mostly the OWPs) and simplify the rest. No handrails or anything.

Yes. Maybe we can add them later to the visual, but disable them when the viewing distance is too large.
 
I'm just about done with the RSS, anyone up to the task of animating it and the FSS/RSS OWPs?


-----Post Added-----


New RSS have been checked in.


-----Post Added-----


Just some timings for the RSS/FSS OWPs. Do note that each is separate from the other.

-RSS
Lower panel translation: ~5 minutes
Upper panel rotation: ~2 minutes

-FSS:
OWP part 1 extension: ~10 minutes
OWP part 2 extension: ~3 minutes
 
Just thought that I would inform you that the source GMAX file for the RSS has been lost. Was working on an updated RSS to go with my updated FSS, but this is obviously been dealt a serious blow. Neither back-up files nor the main source file are OK.

So, I'm assessing the situation right now, obviously rebuilding the RSS will take some time and effort and animations probably will have to be redone.

So, the OCO launch is not the only major disappointment this morning.
 
Would it help you putting also the source files into a folder of the subversion repository? This way you could have a backup quickly.
 
Would it help you putting also the source files into a folder of the subversion repository? This way you could have a backup quickly.
Possibly. That way if my HDD would suffer some sort of glitch and corrupt the files, I would have back-ups not local and it would take multiple failures to corrupt the files.
 
Possibly. That way if my HDD would suffer some sort of glitch and corrupt the files, I would have back-ups not local and it would take multiple failures to corrupt the files.

Exactly. Also it would maybe be cheaper and less a strain on your workflow, than installing your own backup policy at home.
 
Just to add: The new FSS source file is still OK, along with the MLP and concrete hardstand. So it appears that whatever caused the corruption is local to the RSS source file.


-----Post Added-----


Managed to find an older back-up. I'll see if I can't transplate some of the missing items from the version we have in the repository.

If that's doable, this is not a total loss. Then I just have to redo the new elements and changes. The objective of this latest RSS update was to add the necessary changes for it to be able to support payload loading/unloading operations.
 
Back
Top