SSU Development Thread (2.0 to 3.0)

Status
Not open for further replies.
BTW Urwumpe, most of your "GPC lecture" I already had an idea. The problem tends to be translating the idea intro practice...:blush:

With the limitations on DPS work I need to know if I can fix 2 small bugs I just found in the DPS:
1) class MM801 prevents any DISP/SPEC from running - fixed waiting clearance to commit
2) Key index has FAULTSUMM as "0", which causes the IDP to think the scratch line is complete - I think changing the numbering of the keys will fix it.

On #2, I did the necessary changes and it works. Can I commit?
 
BTW Urwumpe, most of your "GPC lecture" I already had an idea. The problem tends to be translating the idea intro practice...:blush:



On #2, I did the necessary changes and it works. Can I commit?

I have some ideas there... can you read UML2?

And yes, you can. When its bad, I will rant about it and make a youtube video telling the world how bad you are doing this.
 
I have some ideas there... can you read UML2?

Errmm, I'll say yes... as I played with UML diagrams on a class some time ago... but I don't have fond memories of that class... :dry: I'll know when I see it.

And yes, you can. When its bad, I will rant about it and make a youtube video telling the world how bad you are doing this.
I'm asking because you said you were making changes on the DPS, and I don't want to disrupt your work.
 
I'm asking because you said you were making changes on the DPS, and I don't want to disrupt your work.

I try to not change anything here, before I have a plan that I like. :lol: I just don't want to disrupt too much after the release.
 
So, ticket cleanup time: 38, 41, 105 and 109 should be fixed. Creators please confirm the fix and close them, or say what's still missing.
A clean ticket list is a happy ticket list. :lol:
 
Found a small glitch while testing: The virtual runway on the HUD is also drawn at "negative altitude" and looks strange then. The altitude of the runway is possible calculated wrong relative to the shuttle, since it was slightly above the cockpit windows after landing in EDW. Possibly related to the shape of Earth.
 
So, after a crash course on how to "program" a report instead of writing it, and countless errors later, I finally got to insert the Mission File stuff into the manual.
While "I have my hands on the dough", I could also change the version number of the manual... but for that I need to know what will be the version number of this release, and we haven't settled that yet. I vote for 3.0 (thus the manual name would change from "SSU Ops Manual V1.XX Rev. B" to "SSU Ops Manual V3.0").
 
I may not have a vote, but my 2 cents...

All version numbers should match, I find it easier to keep track of anything and it's manual if they are the same.
 
I may not have a vote, but my 2 cents...

All version numbers should match, I find it easier to keep track of anything and it's manual if they are the same.

Yes, rest assured that all numbers will match. We just haven't decided on what that number will be. :lol:
 
The ODS in SSU is way too small. I resized it to the correct size, if anyone wants to commit it. I imagine the animations will have to change.
 
The ODS in SSU is way too small. I resized it to the correct size, if anyone wants to commit it. I imagine the animations will have to change.
Send it along and I'll make the necessary corrections.
 
Under the banner A clean ticket list is a happy ticket list, let's try (again) to clean it up.
Tickets 38, 41 and 109: AFAIK they are done, so respective creators either close them or please tell what is missing.
Tickets 107 and 111: for me to at least try to do something about those, more info is required.
 
The ODS in SSU is way too small. I resized it to the correct size, if anyone wants to commit it. I imagine the animations will have to change.
So I got and I checked it and it is now too big. According to my information the black section of the ODS is 1.552 m in diameter, yours is 1.6595 m.

I have prepared an ODS reference package which includes a very detailed document on the ODS which does include detailed schematics with measurements: ODS Reference Package (82 MB, zip)
 
So I got and I checked it and it is now too big. According to my information the black section of the ODS is 1.552 m in diameter, yours is 1.6595 m.

I have prepared an ODS reference package which includes a very detailed document on the ODS which does include detailed schematics with measurements: ODS Reference Package (82 MB, zip)

Does your reference also include thermal blankets?
 
Does your reference also include thermal blankets?
Yes. And even if they didn't, I seriously doubt that they would explain the 10 cm difference!
 
Yes. And even if they didn't, I seriously doubt that they would explain the 10 cm difference!

Oh, those can easily explain such a difference, 5-10 cm more in diameter is no surprise.
 
It matches the sizing for the shuttle we have perfectly. Plus it lines up very closely with the ISS AtoZ PMAs. Now should we talk about your mishapen ET ?
 
It matches the sizing for the shuttle we have perfectly. Plus it lines up very closely with the ISS AtoZ PMAs. Now should we talk about your mishapen ET ?
I got new ones in the works. As it is the wrong size we decided not to mess with it for now as everything pad-wise would have to be redone. That would have to wait until the next major version.
 
I got new ones in the works. As it is the wrong size we decided not to mess with it for now as everything pad-wise would have to be redone. That would have to wait until the next major version.

Then leave the ODS alone. It's more than fine.
 
I'm missing data on a few screens from the landing part of the flight:
Deorbit
CDR1
CDR2 AE PFD
CRT1 DEORB MNVR EXEC
CRT2 DEORB MNVR EXEC
CRT3 BFS GNC SYS SUMM 2
MFD1
MFD2
PLT1 AE PFD
PLT2 APU/HYD

Entry
CDR1
CDR2 AE PFD
CRT1 ENTRY TRAJ 1
CRT2 HORIZ SIT
CRT3 (BFS) ENTRY TRAJ
MFD1
MFD2
PLT1 AE PFD
PLT2 APU/HYD

TAEM
CDR1
CDR2 AE PFD
CRT1 HORIZ SIT
CRT2
CRT3
MFD1
MFD2 SPI
PLT1 AE PFD
PLT2 APU/HYD
 
Status
Not open for further replies.
Back
Top