SSU Development Thread (2.0 to 3.0)

[DaveS]

What's a sill gusset ?

They're the small structures that connects the sill longerons with the Xo576 bulkhead.

---------- Post added at 08:34 PM ---------- Previous post was at 08:12 PM ----------

This EVA photo from STS-125 shows the starboard sill gusset plate:

 

[Urwumpe]

Please... say "gusset plate"... that makes it easier to find it in the picture. :rofl: There are also textile gussets which Google likes to find easier...

 

[Donamy]

Should have said, "...the thing the little handles are attached too."

Anyway, it's fixed.

 

[DaveS]

I have discovered a texturing bo-bo. It's on the top of the aft engine compartment where the vertical stabilizer attaches to it. It seems like the two sides are mirrored which they shouldn't be. They are different. This is where the exhaust ports for the APUs and WSBs live.

This photo from STS-135 shows it:

Also note how the OMS pod overlaps the Xo1307 bulkhead with a set of carrier panels. This photo from pre-RSS retract prior to the July 13 2005 launch attempt of STS-114 shows the LOMS pod carrier panel inside the red border:

 

[Donamy]

Will have to wait for post-release.

 

[DaveS]

Will have to wait for post-release.

Copy that. What else is on the post-release wait list? Just so that I don't report something that is already known and on hold.

 

[SiameseCat]

Is anyone working on updating the various textures to work with the new mesh? As thing stand, only the default Orbiter_blank.dds works.

 

[DaveS]

Is anyone working on updating the various textures to work with the new mesh? As thing stand, only the default Orbiter_blank.dds works.

Would love to but I don't have the master source texture. I just have the one I made for my mesh.

 

[Donamy]

I'll upload it to Orbithangar fro a bit.

[ame="http://www.orbithangar.com/searchid.php?ID=6677"]Orbiter blank psd[/ame]

 

[DaveS]

What's remaining for us to get ready to release v3.0 of SSU?

 

[SiameseCat]

Is there anything that still needs to be fixed regarding the new mesh? If not, I'll merge the new mesh branch into the trunk tomorrow.

 

[DaveS]

Is there anything that still needs to be fixed regarding the new mesh? If not, I'll merge the new mesh branch into the trunk tomorrow.

There's the ones that I pointed out in the screenshot New_Orbiter3.jpg as well as some visible gaps on the wings, more specifically the elevon seal panels and the ET umbilical well doors. I would also like request a new texture for the EDO pallet and some general SSUbay.dds texture clean-up(mainly removing stuff that used by just textures and are now actual meshes). Beyond that, the orbiter is done. I have a new ET in the works, but it can wait as it will require new pad meshes.

 

[Urwumpe]

I don't like the current DPS, but that can wait. I only know of few glitches, that don't require a massive change to conform to the FDF. We should just plan to include a partition-oriented PASS-DPS in a next minor release.

the scenarios should get checked before release again. Also we should disable DebugString outputs. Otherwise I feel like Go.

 

[GLS]

Until the end of next Sunday (the deadline for the last project this semester) I can't check anything, so right now the only input I can give is that it looks very good in the screenshots.:thumbup:
I have 2 "debug outputs" in the mps stuff: one prints messages about some constructors to the log, and the other prints main engine controller data to 3 text files. Both outputs are enabled by #defines, the first in the mps.h file (I think) and the main engine data is in the EIU.h. I think the main engine data could be turned off, as file size growns quite fast and without a converter (that I still have to finish) is useless. About the messages in the log, I also don't think they are needed, but it's not a big thing so they could be left active.

 

[Urwumpe]

I have 2 "debug outputs" in the mps stuff: one prints messages about some constructors to the log, and the other prints main engine controller data to 3 text files. Both outputs are enabled by #defines, the first in the mps.h file (I think) and the main engine data is in the EIU.h. I think the main engine data could be turned off, as file size growns quite fast and without a converter (that I still have to finish) is useless. About the messages in the log, I also don't think they are needed, but it's not a big thing so they could be left active.

We can maybe enable your additional log files by configuration file options, so that these additional log files can be created without the need to recompile things.

After all, the real one also produces that data and stores it on magnetic tape, for sending the data to the ground after reaching orbit.

 

[GLS]

We can maybe enable your additional log files by configuration file options, so that these additional log files can be created without the need to recompile things.

After all, the real one also produces that data and stores it on magnetic tape, for sending the data to the ground after reaching orbit.

OK, I'll try to look at it next week.

 

[SiameseCat]

The D3D9 config file (Config/GC/SpaceShuttleUltra.cfg) needs to be updated to work with the new mesh. At the moment, the exterior of the shuttle is reflective, which looks really weird.

 

[DaveS]

The D3D9 config file (Config/GC/SpaceShuttleUltra.cfg) needs to be updated to work with the new mesh. At the moment, the exterior of the shuttle is reflective, which looks really weird.

Updated version has now been checked in.

 

[SiameseCat]

I've merged the new mesh branch into the trunk.

 

[Donamy]

How is the release coming ? I mean could we get a release on OH ?