SSU Development Thread (2.0 to 3.0)

Status
Not open for further replies.
For the centaur Branch: Do we have a Galileo mesh that we can use in SSU as proper stand-in? The Carina looks a bit misplaced.
No.
 
Can't commit, there is a bug in the sourceforge server it seems, regarding large files. Orbiter.msh results in Problems during the transaction.
 
For the centaur Branch: Do we have a Galileo mesh that we can use in SSU as proper stand-in? The Carina looks a bit misplaced.

No, we don't have Galileo or any other probe (I added the SSUGenericPayload, a.k.a. Carina, so we had a payload on the Centaur and we could test/showcase it). The Galileo addons out there, that I know of, all have the shades that were added to allow it to be launched by the IUS towards Venus, so we "can't" even use any of them.
IMHO, I think we should devote ourselves to developing the shuttle, with all its capabilities and "extras", and leave the payloads for other people. We should start advertising SSU to get users to create payloads for us. :lol:

---------- Post added at 10:21 PM ---------- Previous post was at 10:12 PM ----------

Hopefully this isn't too agressive :rofl:
gLBnyu9.jpg
 
Make sure you use "svn+ssh" as protocol for Subversion, the https: access to Sourceforge seems to be broken for large files and the "svn+ssh" connection is also way faster.
 
I've updated the SSU manual to include the MEDS displays and images of the displays.
 
Revision 2104 doesn't compile:
atlantis.cpp(6142): error C2065: 'GRP_DEA_MOUNT_KU' : undeclared identifier
 
Revision 2104 doesn't compile:
atlantis.cpp(6142): error C2065: 'GRP_DEA_MOUNT_KU' : undeclared identifier
I forgot to check in the updated meshres files for the orbiter and Ku band DA. Try it now and it should build just fine.
 
Guys, don't mean to bother you but I just noticed no one has popped up in this thread since more than a month now..
Is this project on stand by or did NASA cut its funds for SSU? (starting to get worried :hmm:)
 
Guys, don't mean to bother you but I just noticed no one has popped up in this thread since more than a month now..
Is this project on stand by or did NASA cut its funds for SSU? (starting to get worried :hmm:)
Most of us are just too busy to work on SSU.
 
Guys, don't mean to bother you but I just noticed no one has popped up in this thread since more than a month now..
Is this project on stand by or did NASA cut its funds for SSU? (starting to get worried :hmm:)

I am just sick with the [ame="http://bar.wikipedia.org/wiki/Oachkatzl"]Oachkatzl [/ame]flu right now and a bit too crazy for coding something that would not make Lovecraft proud.

:facepalm:
 
SSU !! What's that ?
 
I'm finishing the "class part" of the semester, and about to start the "exam part". :(
Just over a month to go before I get back and start work on the mission planner/creator/whatever the name is...
 
No, we don't have Galileo or any other probe (I added the SSUGenericPayload, a.k.a. Carina, so we had a payload on the Centaur and we could test/showcase it). The Galileo addons out there, that I know of, all have the shades that were added to allow it to be launched by the IUS towards Venus, so we "can't" even use any of them.
IMHO, I think we should devote ourselves to developing the shuttle, with all its capabilities and "extras", and leave the payloads for other people. We should start advertising SSU to get users to create payloads for us. :lol:

---------- Post added at 10:21 PM ---------- Previous post was at 10:12 PM ----------

Hopefully this isn't too agressive :rofl:
gLBnyu9.jpg

I posted a Galileo probe a couple of months ago that I put on your original Centaur it worked fine, but I don't know what you mean by the wrong shader for SSU ? Mine is fully animated and a bit more accurate than the other ones in OH it also has deployable probe with heat shield and top cover
 
I posted a Galileo probe a couple of months ago that I put on your original Centaur it worked fine, but I don't know what you mean by the wrong shader for SSU ? Mine is fully animated and a bit more accurate than the other ones in OH it also has deployable probe with heat shield and top cover
The shade GLS is talking about is the large disc-shaped sun-shade that covers the instruments just below the Hi-Gain Antenna (HGA). Originally that was not in the design. It was added after cancellation of the Shuttle/Centaur program in June 1986. The first VEEGA (Venus-Earth-Earth Gravity Assist) changes including the sun-shade were logged in Feb. 88.

The sun-shade was for protecting the sensitive instruments against the high temperatures that spacecraft would encounter at Venus. With the direct trajectory that the Centaur would have provided, no Venus GA would have been necessary. Another change was the delayed deployment of the HGA to until after the Venus GA instead of shortly after separation from the Centaur.
 
Last edited:
It's just like DaveS said. Here's 2 images showing the "original version" and the "flown version", where the shade (or whatever it's called) is very noticeable.
Galileo_in_1983.jpg

Galileo_Preparations_-_GPN-2000-000672.jpg

The flown version image is missing another shade from the top of the HGA, that would shade it.
 
The Scrub Simulation Unit. It allows you to renact the emotional terror of the Space Shuttle Program.

Guys I have the (bad) feeling something is hiding behind your sarcasm...
Tell me you did not give up:nono:
 
Guys I have the (bad) feeling something is hiding behind your sarcasm...
Tell me you did not give up:nono:

No, giving up inches from the finish line is no option, at least for me. :cheers:

But the real life is really a big annoyance for such projects, like always. We are already seeing the release in front of us, but somehow, we can't yet just simply press to release and get it done.

I would sure love to do a lot of things different in the future, but I know my real-life, I have a really bad negotiation position there.
 
No, giving up inches from the finish line is no option, at least for me. :cheers:

But the real life is really a big annoyance for such projects, like always. We are already seeing the release in front of us, but somehow, we can't yet just simply press to release and get it done.
I think it might have something to do with the experience of the previous release (v1.25). It was really a bad experience, fraught with mistakes. Not only that, I think that as things get more complex with the introduction of more systems, more detailed simulation of the systems we already have, we're going to get flooded with questions like "how do I do this, how do I take off?". This is just going to steal time from genuine bug fixing and development.

This is just my opinion on why we're not doing public releases.
 
Perhaps the release of v1.25 was a headache for you as developers but it wasn't a bad experience for the Orbiteers who used it. It's level of immersion was great :thumbup::thumbup: That's why we're anxious for SSU's rollout.
 
Status
Not open for further replies.
Back
Top