SSU Development Thread (2.0 to 3.0)

[Donamy]

It only works from one direction, because of the transparency issues. Could it be made to change with the view, like orbiter does with the exhaust textures now ?

 

[Urwumpe]

It only works from one direction, because of the transparency issues. Could it be made to change with the view, like orbiter does with the exhaust textures now ?

Not that simple, Orbiter has some advantages there since it can use "billboards" for rendering. Maybe it looks better in DX9, but the DX7 reference remains.


I added some stub files for the MDMs and finished a file parser for them in the MDM class. Removes the annoying error message about the MDM PROM files and adds something that actually has a purpose. Now the IO modules of the MDMs can be defined in such a file and can also be changed for special orbiter configurations. Right now, we make no use of the MDMs AFAIR, but after the release, there might be time for looking at this again.

C++ programming is no longer required there, so anybody could dig into the NASA DPS documents about the MDM configuration and write the configuration files for the SSU MDMs.

 

[Donamy]

Should the 2 tails, be put in the same mesh file ?

 

[Urwumpe]

@Donamy: The Caution and Warning lights on panel F9 are separate mesh groups now, right? Could enable them.

 

[DaveS]

@Donamy: The Caution and Warning lights on panel F9 are separate mesh groups now, right? Could enable them.

Yes they are. I did that on your request.

 

[Urwumpe]

Yes they are. I did that on your request.

OK, will test. :thumbup:

 

[Wolf]

Which OPS 1? There is no simple OPS1 in the Space Shuttle.

Do you mean PASS OPS G1? So the component software of it:

OPS 1011 "XXXXXX TRAJ" - partially implemented, not every feature
OPS 1041 "XXXXXX MNVR" - implemented

DISP 18 "GNC SYS SUMM 1" - partially implemented
SPEC 23 "RCS" - not implemented
SPEC 50 "HORIZ SIT" - not implemented
SPEC 51 "OVERRIDE" - not implemented
SPEC 53 "CONTROLS" - not implemented

Also OPS 0 is completely missing.

I am referring to MM 101-102-103: if I am not mistaking in the pre-launch sequence (around T-30') in order to load OPS1 we are supposed to enter "OPS 101 PRO". I have tried that but the CRT remains blank (except for the OPS 101 PRO string).

 

[Urwumpe]

I am referring to MM 101-102-103: if I am not mistaking in the pre-launch sequence (around T-30') in order to load OPS1 we are supposed to enter "OPS 101 PRO". I have tried that but the CRT remains blank (except for the OPS 101 PRO string).

Was working once... will check this. CONFIRMED - the display is gone, OPS 101 PRO has no effect at all.


How about making an early release candidate of SSU 2.1? The scenarios seem to work fine here, the number of glitches low, but noticable. Maybe it is a good time to do so

---------- Post added at 11:05 AM ---------- Previous post was at 10:29 AM ----------

GNC MM 102 ASCENT TRAJ display appears after lift-off, before the screen is blank.

---------- Post added at 11:15 AM ---------- Previous post was at 11:05 AM ----------

Can somebody confirm that the Aft RCS propellants are always indicated as zero in the display above the pilots seat?

I think this should get fixed before final release, if confirmed.

 

[GLS]

Was working once... will check this. CONFIRMED - the display is gone, OPS 101 PRO has no effect at all.


How about making an early release candidate of SSU 2.1? The scenarios seem to work fine here, the number of glitches low, but noticable. Maybe it is a good time to do so

---------- Post added at 11:05 AM ---------- Previous post was at 10:29 AM ----------

GNC MM 102 ASCENT TRAJ display appears after lift-off, before the screen is blank.

---------- Post added at 11:15 AM ---------- Previous post was at 11:05 AM ----------

Can somebody confirm that the Aft RCS propellants are always indicated as zero in the display above the pilots seat?

I think this should get fixed before final release, if confirmed.

Currently there's no need for MM101 PRO as all prelaunch scenarios start in OPS1 already. When we get a better prelaunch sim, then we'll need those key strokes at T-20mins I think.

There's no ASCENT TRAJ showing in MM101 because that display is currently in AscentGuidance and that only runs from MM102 onwards. So the display is in the wrong place or AscentGuidance should run in MM101.

AFAIK the aft RCS tanks don't exist, and the RCS is fed from the OMS tanks which have OMS+RCS prop mass. A better OMS/RCS implementation is 2º on my todo list (mission planner is 1º).

 

[Urwumpe]

Before we collide there - are you making a mission planner or do I ? :lol:

We should then just display the same quantity values for OMS and RCS ... just for being on the safe side.

 

[GLS]

Before we collide there - are you making a mission planner or do I ? :lol:

We should then just display the same quantity values for OMS and RCS ... just for being on the safe side.

I'm not doing anything SSU related ATM. I would like to, but there's little time. If you have time please start it, and when I can I'll join in.

 

[Urwumpe]

I'm not doing anything SSU related ATM. I would like to, but there's little time. If you have time please start it, and when I can I'll join in.

Well, I would do something with JavaFx... I am still pretty inept in C#, that is why I would call it preliminary.

 

[SiameseCat]

Not that simple, Orbiter has some advantages there since it can use "billboards" for rendering. Maybe it looks better in DX9, but the DX7 reference remains.


I added some stub files for the MDMs and finished a file parser for them in the MDM class. Removes the annoying error message about the MDM PROM files and adds something that actually has a purpose. Now the IO modules of the MDMs can be defined in such a file and can also be changed for special orbiter configurations. Right now, we make no use of the MDMs AFAIR, but after the release, there might be time for looking at this again.

C++ programming is no longer required there, so anybody could dig into the NASA DPS documents about the MDM configuration and write the configuration files for the SSU MDMs.

Orbitersim crashes when loading any SSU scenario. I think it's related to the MDM code; everything works if I use the previous revision.

 

[Urwumpe]

Orbitersim crashes when loading any SSU scenario. I think it's related to the MDM code; everything works if I use the previous revision.

Will look at it, but I doubt its the new code, since the simulation crashes a bit late here in a short test.

Some scenarios work here, it isn't the MDM code, which is executed everytime.

Since the crashes can't be located that easily, I now placed some try-catch blocks around the important call backs of Orbiter, so no exception leaves SSU uncaught.

---------- Post added at 04:45 PM ---------- Previous post was at 03:56 PM ----------

Can't confirm this anymore... had some crash directly after getting back from shopping, but now everything works fine. I tried to provoke an error, but no chance.

Did you do a full recompilation? I added a "GetVisual()" function to Atlantis, so VC components can access the Visual, if available.

 

[DaveS]

I too get a CTD upon loading any SSU scenario, just like SC. And I did a full rebuild of everything. Revision built was 1829.

 

[Urwumpe]

I too get a CTD upon loading any SSU scenario, just like SC. And I did a full rebuild of everything. Revision built was 1829.

Strange. Have committed everything, everything works here... Do you have any strange log message?

Does somebody know how to get from MM 105/106 to MM 201?

 

[DaveS]

Strange. Have committed everything, everything works here... Do you have any strange log message?

No, nothing.

Does somebody know how to get from MM 105/106 to MM 201?

Have you checked the Post-Insertion FDF? http://www.nasa.gov/centers/johnson/news/flightdatafiles/foia_archive.html

 

[Donamy]

Just about complete. Just need to know the order of the parts for animations.

Also, it seems the tail no-chute is 4 in. longer than the tail with the chute. At least in the drawings I have. Right now I split the difference.

 

[Urwumpe]

No, nothing.


Have you checked the Post-Insertion FDF? http://www.nasa.gov/centers/johnson/news/flightdatafiles/foia_archive.html

Hahahahaha... good joke. :rofl::facepalm:


Which scenario does not work for example?

 

[Donamy]

DaveS, should I use the OMSpods you have or make new ones ?