Space Shuttle Ultra 1.25 Revision B development

What are the clips? I don't think its a good idea to play any mission-specific sounds.
 
What are the clips? I don't think its a good idea to play any mission-specific sounds.
They're actually pretty generic and only use "CDR", "OTC", "PLT", "NTD", "GLS" and "Flight Crew". Nothing else that would lock them to a specific mission or Orbiter.
 
What are the sounds for? If they're tied to events we already simulate (like SSME start) or a specific time in the countdown it should be possible, but otherwise things might be messy.
 
What are the sounds for? If they're tied to events we already simulate (like SSME start) or a specific time in the countdown it should be possible, but otherwise things might be messy.
They're of Terminal Count(T-9 minutes to lift-off).
 
I think that we have another initialization bug. This time it concerns PLB light switches on A7U. They exhibit the same behavior as the A8U EE TBs before they got fixed (on at scenario exit, off at scenario start again). Also, I think that the FWD bulkhead light and docking light have been forgotten.

Here's the positions for them:
Code:
FWD bulkhead: 0.0, 3.05, 11.98
Docking light: 0.0, 3.33, 11.98
 
Also, I think that the FWD bulkhead light and docking light have been forgotten.

Here's the positions for them:
Code:
FWD bulkhead: 0.0, 3.05, 11.98
Docking light: 0.0, 3.33, 11.98
According to the SCOM:
These two lights are
present only on OV-104, and have been removed
from OV-103 and OV-105 due to issues with the
water loop cold plate.
This will probably require a scenario file entry.

---------- Post added at 10:00 PM ---------- Previous post was at 09:20 PM ----------

I think that we have another initialization bug. This time it concerns PLB light switches on A7U. They exhibit the same behavior as the A8U EE TBs before they got fixed (on at scenario exit, off at scenario start again).
Should be fixed now.
 
I'm working on some more changes to the orbiter. Here's a list of what has been incorporated so far:

Code:
Orbiter mesh changes:

-Corrected the positions of the ET umbilical door and MLG doors relative to the texture
-Corrected aft engine compartment/body flap interace, no longer a gap between the body flap and the aft
-New Payload Bay Door (PLBD) Center-line (C/L) latches. Passive half now features the back plates while the active half 

features the forks and torque shafts for the latch hooks
-Corrected the gap width between the inboard/outboard elevons
-Corrected the gap between the forward PLB Radiator panels and the PLBD ribs
-Corrected locations of the PLB Radiatior panel Freon-21 supply tubes
-Corrected port/starboard Active Vent System (AVS) door textures
-Corrected PLB Cameras B/C locations and stand-offs

Orbiter texture changes:
-New WLE RCC panel textures, thanks to Zsolt33
-New early Discovery, Endeavour and Atlantis upper wing surface textures, thanks to xmariox
-Improved OMS pod "tile pad" texture
-Moved the aft T0 umbilicals further aft
-Added MPS LH2 dump port 
-Added FES#2 and 3 vents
-Added AVS door#9

One question though: Should I go ahead and add the removable Midbody Payload Umbilical Access Panels and cavities for the Centaur?
 
IOne question though: Should I go ahead and add the removable Midbody Payload Umbilical Access Panels and cavities for the Centaur?

Are those used in all Orbiters or did they only exist temporarily?
 
Are those used in all Orbiters or did they only exist temporarily?
Still exist as they're a baseline part of the midbody. Here's a photo of OV-105's midbody before assembly began. The red circle shows the umbilical cavity on the starboard side.

OV-105_midbody_umbilical.jpg
 
Then yes, makes sense.
 
Here's some screenshots from the current orbiter work:

C/L latches, passive half backing plates, with accurate markings:
SSU_New_PLBD_CL_backplates.jpg


C/L latches, active half showing complete latch gang:
SSU_New_PLBD_CL_latches.jpg


PLB/Midbody umbilical cavity, starboard side shown. Port side identical:
SSU_New_PLB_Umbilical.jpg


New WLE RCC panel textures:
SSU_new_WLE_tex.jpg
 
Now this is the kind of detail level I like. :) :thumbup:
 
Now this is the kind of detail level I like. :) :thumbup:


I am a bit concerned about the poly count there, but since I am only weeks away from getting my new development PC acquired, I should better shut up and code...
 
The new KU antenna has quite a bit more polys too.
 
The new orbiter mesh+textures have now been checked in. Let me know if you spot any errors during the build process in case I forgot any files.

---------- Post added at 07:53 PM ---------- Previous post was at 07:43 PM ----------

One thing that I have noticed about the PLBD C/L latches in SSU is that they drive one latch gang at the time. This is not correct. It should be two latch gangs at the time. The correct order is first 5-8 and 9-12 then 1-4 and 13-16.
 
I must say, I was skeptical at first, but eventually I decided to try space shuttle ultra since I am a nut for realism. I've been using shuttle fleet for a long time but this is just a whole different ball game. I cannot express the love I have for this addon.
 
Suggestion for the next development steps (aside of bugfixing-a-lot):

Since GLS is currently contributing to the MPS code, what about improving the other subsystems that are required for the MPS operations?

As such, I identified the following small task items to be done:

  • Implement MPS ENGINE STATUS indicator on Panel C3
  • Engine shutdown buttons on panel C3 (connected to GPC via MDM)
  • MPS TVC actuators and hydraulic valves correctly implemented
    • Basic Hydraulic actuator class
    • MPS Hydraulic valve class
    • Test case: Hydraulic Lock-up possible at low hydraulic pressure
  • Test case: Stowing in Orbit
  • Test case: Nominal ascent
  • Test case: Center engine repositioning for reentry
  • Test case: Rain drain repositioning for post-landing.
  • Test case: Pre-launch Gimbal check


The hydraulic valves in the SSME all operate the same, thus it would make sense implementing them by a single class, and change only the parameters for each valve. They are electrically controlled (valve position = analog input voltage) and return the valve position as analog voltage again. These valves can be closed by pneumatic pressure if the hydraulic fails.



So, the valve needs as interfaces:

  1. Hydraulic power
  2. Hydraulic return
  3. Pneumatic power (for emergency closing)
  4. Control input A
  5. Control input B
  6. Position output

I plan to start at these tasks once the new notebook is there, but feel free to say "I do it" before I do. Every subtask should not take more than a weekend approximately, that should make it easy to plan. Important is test everything on the SCOM level. Not only the nominal "follow the checklist damnit" way.
 
Last edited:
Suggestion for the next development steps (aside of bugfixing-a-lot):

Since GLS is currently contributing to the MPS code, what about improving the other subsystems that are required for the MPS operations?

As such, I identified the following small task items to be done:

  • Implement MPS ENGINE STATUS indicator on Panel C3
  • Engine shutdown buttons on panel C3 (connected to GPC via MDM)
  • MPS TVC actuators and hydraulic valves correctly implemented
    • Basic Hydraulic actuator class
    • MPS Hydraulic valve class
    • Test case: Stowing in Orbit
    • Test case: Nominal ascent
    • Test case: Pre-launch Gimbal check
    • Test case: Hydraulic Lock-up possible at low hydraulic pressure
Another item is nominal case is Center SSME Repo during descent. This is done to provide clearance between the nozzle and the drag-chute during deploy. If this does not happen, drag-chute deploy will be Emergency Only.

Another nominal MPS event during entry and landing is the post-landing SSME Repo to the "rain drain" position. For this we need to wire up the BODY FLAP position indicator on the CRTMFD SPI as SET BODY FLAP is done just prior to SSME REPO. Both can be found on page 5-7 of the Entry FDF.
 
Another item is nominal case is Center SSME Repo during descent. This is done to provide clearance between the nozzle and the drag-chute during deploy. If this does not happen, drag-chute deploy will be Emergency Only.

Another nominal MPS event during entry and landing is the post-landing SSME Repo to the "rain drain" position. For this we need to wire up the BODY FLAP position indicator on the CRTMFD SPI as SET BODY FLAP is done just prior to SSME REPO. Both can be found on page 5-7 of the Entry FDF.

Sounds right, both should be included in the list as well.

EDIT: These require the OPS8 SPEC pages, right?

---------- Post added at 10:15 AM ---------- Previous post was at 09:28 AM ----------

DaveS: Can you add the cover plate for the hole of the midbody payload umbilical well in the Orbiter to the main mesh, so that it is visible by default and can be hidden once we do more work on the Centaur?

I think this the best solution there, since we will less often have missions with centaur than without it.
 
Last edited:
Back
Top