SSU Development Thread (2.0 to 3.0)

[DaveS]

Q: How accurate are the thrust figures for the various MPS dump outlets? I have found these charts in the SOBD and they don't quite match up to the ones we have currently.

Nominal:

RTLS:

TAL:

 

[GLS]

Q: How accurate are the thrust figures for the various MPS dump outlets? I have found these charts in the SOBD and they don't quite match up to the ones we have currently.

Probably not much, since the thrust and ISP are pretty much guess work. The SSME LOX dump dV is +/- correct (although the thrust might be wrong), but since I had very little data about the rest, I had to "improvise".:lol:
I'll check the charts later this week and try to correct the errors. Thanks!

 

[DaveS]

This is a question that has been on my mind for a while now: In the Crawler we have a feature that allows the saving/loading of the actual VC position used at the time of scenario exit.
Could this feature be implemented into the main shuttle code? I think that this could potentially save some time setting things up when testing visual stuff, mainly VC changes/additions.

 

[GLS]

I updated most scenarios to show a +/- correct configuration of the displays, but in the default graphics client it gets painful to have all 9 MDUs up, especially now with the ADI and HSI (that are still missing lots of things). In D3D9 it's still very smooth. If the performance is too bad, I can change the scenarios so only 4 MDUs on the CDR side are on, or if it's really bad we can leave the ADI and/or HSI out for the time being.

I'm getting these warnings during compilation for some time now:

trunk\orbitersdk\space shuttle ultra\crawler\meshres_drivetruck.h(66): warning C4005: 'GRP_InnerShoe_43_TRUCK' : macro redefinition
	trunk\orbitersdk\space shuttle ultra\crawler\meshres_drivetruck.h(65) : see previous definition of 'GRP_InnerShoe_43_TRUCK'

trunk\orbitersdk\space shuttle ultra\crawler\meshres_drivetruck.h(140): warning C4005: 'GRP_OuterShoe_58_TRUCK' : macro redefinition
	trunk\orbitersdk\space shuttle ultra\crawler\meshres_drivetruck.h(139) : see previous definition of 'GRP_OuterShoe_58_TRUCK'

trunk\orbitersdk\space shuttle ultra\crawler\meshres_crawler_vc.h(43): warning C4005: 'GRP_Group_VC' : macro redefinition
	trunk\orbitersdk\space shuttle ultra\crawler\meshres_crawler_vc.h(20) : see previous definition of 'GRP_Group_VC'

Also, in D3D9 only: during the twang, when inside the VC the view shakes... is it our problem or D3D9?

 

[Urwumpe]

I'm getting these warnings during compilation for some time now:

Could be fixed by using ssumeshc instead of the vanilla meshc.

The warning is created because the groups in the mesh have the same name.

 

[GLS]

Q: How accurate are the thrust figures for the various MPS dump outlets? I have found these charts in the SOBD and they don't quite match up to the ones we have currently.
(images)

Where there any manifold pressure traces next to those charts? As I suspected, the LOX was +/- correct, but it looks like there was a big underestimation of (peak) vent force on the LH2 side, so a pressure chart would help things.

Question: relative velocity vs inertial velocity, what is what? It is my understanding that, in the "shuttle world", Vr was relative to the surface of the Earth, and Vi was relative to the center of the Earth (in Orbiter Vr would be ground speed and Vi orbital speed). But just now looking at the AscentGuidance code for RTHU, I noticed that, what I think is Vi, is being called Vr... am I right? (if so, I messed up the EO VI display in the Ascent Traj by using Vr instead of Vi :facepalm

 

[SiameseCat]

Where there any manifold pressure traces next to those charts? As I suspected, the LOX was +/- correct, but it looks like there was a big underestimation of (peak) vent force on the LH2 side, so a pressure chart would help things.

Question: relative velocity vs inertial velocity, what is what? It is my understanding that, in the "shuttle world", Vr was relative to the surface of the Earth, and Vi was relative to the center of the Earth (in Orbiter Vr would be ground speed and Vi orbital speed). But just now looking at the AscentGuidance code for RTHU, I noticed that, what I think is Vi, is being called Vr... am I right? (if so, I messed up the EO VI display in the Ascent Traj by using Vr instead of Vi :facepalm

I think that's just a confusing variable name. The velocity used in the ascent guidance code is the velocity relative to the center of the Earth, or Vi.

 

[DaveS]

Where there any manifold pressure traces next to those charts? As I suspected, the LOX was +/- correct, but it looks like there was a big underestimation of (peak) vent force on the LH2 side, so a pressure chart would help things.

You can grab the relevant document here: https://dl.dropboxusercontent.com/u/24122088/Shuttle Operational Data Book Vol 1 part 2.pdf

It begins on page 381.

 

[GLS]

I think that's just a confusing variable name. The velocity used in the ascent guidance code is the velocity relative to the center of the Earth, or Vi.

OK, I'll correct the name and fix the RTHU velocity (and EO VI trap as well).

You can grab the relevant document here: https://dl.dropboxusercontent.com/u/24122088/Shuttle Operational Data Book Vol 1 part 2.pdf

It begins on page 381.

As I suspected those charts are from a old dump sequence, but still there's buckets of useful data.
And then there's the rest of the document... HOLY COW, this is a gold mine!!!! Thanks a lot man!
Urwumpe, you may want to take a look starting on page 880... several command word formats... bit... bits everywhere :lol:

 

[Urwumpe]

Urwumpe, you may want to take a look starting on page 880... several command word formats... bit... bits everywhere :lol:

I know, I read the same document from time to time... not sure if it started at 880 or of there had been earlier formats... :lol:

 

[DaveS]

I have checked in updated External Airlock and ODS meshes. Everything should compile, however someone with more knowledge will have to update the ODS docking ring animations.

I believe this takes care of all the meshes for release.

 

[SiameseCat]

You can grab the relevant document here: https://dl.dropboxusercontent.com/u/24122088/Shuttle Operational Data Book Vol 1 part 2.pdf

It begins on page 381.

Wow, I didn't know you had this. Do you have any of the other sections of the SODB?

 

[DaveS]

Wow, I didn't know you had this. Do you have any of the other sections of the SODB?

I do have part 1 of the same volume, I'll upload it in the morning.

---------- Post added at 11:30 AM ---------- Previous post was at 12:01 AM ----------

Here's part part 1 of SODB Vol. 1: https://dl.dropboxusercontent.com/u/24122088/Shuttle Operational Data Book Vol 1 part 1.pdf

 

[GLS]

I do have part 1 of the same volume, I'll upload it in the morning.

---------- Post added at 11:30 AM ---------- Previous post was at 12:01 AM ----------

Here's part part 1 of SODB Vol. 1: https://dl.dropboxusercontent.com/u/24122088/Shuttle Operational Data Book Vol 1 part 1.pdf

Thanks! :thumbup:

Also, could you take a look at ticket 82? I got some last minute doubts about some textures and I would like to know what to do with them, so we can close that one for good.

 

[DaveS]

Thanks! :thumbup:

Also, could you take a look at ticket 82? I got some last minute doubts about some textures and I would like to know what to do with them, so we can close that one for good.

They're GO for deletion.

 

[GLS]

They're GO for deletion.

I was undecided because, for example, we are keeping "Centaur_G_tex", but are deleting "Centaur_G_tex_norm", "Centaur_G_tex_refl" and "Centaur_G_tex_spec".

 

[DaveS]

I was undecided because, for example, we are keeping "Centaur_G_tex", but are deleting "Centaur_G_tex_norm", "Centaur_G_tex_refl" and "Centaur_G_tex_spec".

I'm kinda on the fence about including the Centaur stuff considering how unfinished it currently is in the trunk. For example, the various fluid/gas ducts on the CISS doesn't animate and it is using SC3 which can't even jettison the Centaur itself properly (no motion following detachment).

So I propose deleting the Centaur stuff entirely from the truck (we do have the Centaur dev branch, so nothing critical is lost forever) and when everything is ready on the Centaur side, we can release a patch or upgrade package that adds everything Centaur related.

 

[GLS]

Wasn't a simple version of the Centaur going out in this release, and an updated version with the dumps, panels and stuff would come later? How is it at the moment?
About the current Centaur stuff in the trunk, my idea was when the merge from the ShuttleCentaur branch occurs, we delete the old stuff in the same process.

 

[DaveS]

Wasn't a simple version of the Centaur going out in this release, and an updated version with the dumps, panels and stuff would come later? How is it at the moment?
About the current Centaur stuff in the trunk, my idea was when the merge from the ShuttleCentaur branch occurs, we delete the old stuff in the same process.

Well, it has so many problems, that is just isn't worth including it. What's the use of it when you can't even properly separate the stage from its support structure in the payload bay?

And it's all old stuff any way, not the latest updated versions.

 

[GLS]

Well, it has so many problems, that is just isn't worth including it. What's the use of it when you can't even properly separate the stage from its support structure in the payload bay?

And it's all old stuff any way, not the latest updated versions.

Talking about releasing the stuff in the ShuttleCentaur branch, that has the CISS rotation and Centaur release working. I'm just waiting for the new Centaur mesh so I can update the RCS positions and AFAIK it's good to go.