SSU V1.25 Release

Status
Not open for further replies.
What needs to be done before release? The only bug I'm aware of is the saving of the ODS state.
 
What needs to be done before release? The only bug I'm aware of is the saving of the ODS state.


  • ODS state
  • Star Tracker Door animation
  • General saving of state
  • Using mission files for launch autopilot and ODS configuration
 
Maybe here is the right place to ask that.
Where can I get the SSU 1.25 pre release version?
 
Over the subversion and by compiling it yourself - you can always get the latest version that way.
 
It's funny how you intended for this to be released in October, and here we are in May.

I don't see you do any work on SSU, so please, stick your "funny" where the sun does not see it.
 
It's funny how you intended for this to be released in October, and here we are in May.

I don't see you do any work on SSU, so please, stick your "funny" where the sun does not see it.

Woah, hang on people:)

I don't think Pilot7893's comment was intended to be "abrasive".
I think he was simply trying to make a humorous observation regarding the length of time SSU has been in the works. I don't think he was intending to make a complaint.;)

Just my opinion:cheers:
 
no wonder about 90% of all registered forum members are "lurkers" and their average post count is 5....
The smarter they are... the harder they fall... on you!
On the flip side, I can only imagine the work that has gone into this release... and I know the last knots are the harder to tie...
I just appreciate the talent and amazing work done in the name of the probe?; Nay, I say in the name of... darn... name of what... Gotta check my notes...
 
Does not change my opinion - for any funny comments on the release dates, be part of the team and influence the date yourself, or shut up and wait, while we do the work.

There is absolutely no justification for such comments.

---------- Post added at 09:32 PM ---------- Previous post was at 07:14 PM ----------

Ok, code upgrade - the AC Motor code still requires a lot of work, loading and saving of the ODS is tackled, ported the scenario state format of the Panels&Switches to Subsystems, to allow more complexity.

The block for a subsystems looks now like that, will need to control the compatibility of all subsystems, but I aim at keeping it compatible to the old save-games.

Code:
@SUBSYSTEM APU2
  APU2_State 0
  APU2_FuelPress 0.000
  APU2_HydPress 0.000
  APU2_Speed 0.000
@ENDSUBSYSTEM        ;APU2

There is also some small stuff in the GPC code, but will have no effect as we still don't use the GPC simulation. Want to get to having the GPCIPL MENU in effect soon after 1.25, together with the IDPs working as graphical terminal.

---------- Post added at 10:33 PM ---------- Previous post was at 09:32 PM ----------

Now we can also define the positions of the passive payload attachments over the mission file. The active latches have to be excluded, the code needs a major overhaul for reacting on the mission file.
 
I'll try to update the ActiveLatch code to read data from the mission file.
 
take what-ever time you need... Good things are worth waiting for.
And trust me, your team SSU is the elite... But where is Greg Brurch... he is conspicuously absent. Any way you don't want us gumming up the works.
 
Now we can also define the positions of the passive payload attachments over the mission file. The active latches have to be excluded, the code needs a major overhaul for reacting on the mission file.

Active latch data can be loaded from mission file now.
OK, can anyone check in a mission file with examples of this? And I guess the External Airlock/ODS configuration is still to come?

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

Done some research into the various External Airlock/ODS configurations there have been since STS-71 and I have found that there have been three distinct configurations flown as listed below.

Configuration 1: Tunnel Adapter Assembly(TAA)/External Airlock/ODS: http://science.ksc.nasa.gov/shuttle/missions/sts-74/images/medium/KSC-95EC-1615.jpg

Configuration 2: External Airlock/ODS: http://spaceflight.nasa.gov/gallery/images/shuttle/sts-124/lores/iss017e008532.jpg

Configuration 3: External Airlock only: http://www-pao.ksc.nasa.gov/kscpao/images/large/2009-3013.jpg
 
I have meshes done for all three of those configs.
 
I have meshes done for all three of those configs.
So do I. Well, I'm supposed to as I'm the author of the External Airlock/ODS we're currently using. The TAA comes from my SpaceHAB RDM mesh.
 
So do I. Well, I'm supposed to as I'm the author of the External Airlock/ODS we're currently using. The TAA comes from my SpaceHAB RDM mesh.

And I would like to have a SpaceHab with interior in the Shuttle simulation (not as attached payload)...

But IMHO we should release 1.25 first and then do the external airlock details.
 

So, what about some bug reports... I have a few internal ones, which I am fixing this night, afterwards, I would say it is time to update the documentation, unless there are severe bugs left.

And how are we calling the following Version of SSU? :lol:
 
Status
Not open for further replies.
Back
Top