Space Shuttle Ultra development thread

What's the latest on the stuff that remains to be implemented before the 1.26 release?
 
What's the latest on the stuff that remains to be implemented before the 1.26 release?

From what I remember, needed:
Wheel spin
ODS capture
Payload latches
RSS

Would be nice if we could also move and format the GPC software into the GPC class before the release.
 
Thanks to Daves, I now have the newest SSU working, great work coders, however I see it uses the old ODSVC again, when I replace it with the good one the animations on the A6L panel are messed up. When DaveS tried to do a meshc on it, he had no luck. Can anyone else take a look at this, because the newer ODS panels look much nicer.
 
Thanks to Daves, I now have the newest SSU working, great work coders, however I see it uses the old ODSVC again, when I replace it with the good one the animations on the A6L panel are messed up. When DaveS tried to do a meshc on it, he had no luck. Can anyone else take a look at this, because the newer ODS panels look much nicer.
If you have been added as an official developer you can check in the new mesh+textures yourself by simply selecting the new mesh and right-clicking on it and selecting SVN Commit.
 
Thanks to Daves, I now have the newest SSU working, great work coders, however I see it uses the old ODSVC again, when I replace it with the good one the animations on the A6L panel are messed up. When DaveS tried to do a meshc on it, he had no luck. Can anyone else take a look at this, because the newer ODS panels look much nicer.

Just like DaveS said, it would be good if you directly commit it.

It would also be nice if you can do the meshc run when you commit something, but I think we will find out when something is wrong.

DaveS: What was wrong with the meshc run?
 
DaveS: What was wrong with the meshc run?
Nothing. Problems is with building the new module. It seems some groups have changed names so the compiler balks on that and spits out undeclared identifier errors as it can't find the old group names in the meshres file.
 
Nothing. Problems is with building the new module. It seems some groups have changed names so the compiler balks on that and spits out undeclared identifier errors as it can't find the old group names in the meshres file.

Yes - i prefer capital constants, so I usually change the constant names into upper case. Also I edit the constants as they often contain illegal characters like "&".
 
Check-in ODSVC.msh and panelA7A8.dds
 
From what I remember, needed:
Wheel spin
ODS capture
Payload latches
RSS

Would be nice if we could also move and format the GPC software into the GPC class before the release.
I can do the RSS animation coding. What exactly needs to be done for the payload latches?
 
Seems like there's a problem with the ODS code. Even with the line ODS removed from the scenario, the External Airlock/ODS won't go away.

Another thing: I was reviewing some old discussions of ours and would it be possible to implement OV-102 as an available vehicle? Relevant discussion here: http://orbiter-forum.com/showpost.php?p=33706&postcount=116

Let's just skip the whole EDO/non-EDO orbiter stuff for now and just bring in OV-102 visually. Prior to her loss, she had been scheduled for a flight to ISS in November 2003 after the STS-107 mission. During the turnaround downtime between 107 and 118 she was going to be outfitted with External Airlock/ODS for the ISS mission.
 
Also, she was/is the most popular Orbiter.
 
I can do the RSS animation coding.
I can supply a sound for the RSS Rotation.


-----Post Added-----


Also, she was/is the most popular Orbiter.
Nope! Discovery was.

Number of flights as of Feb 1. 2003:
Columbia: 28 flights(lost on flight 28)
Discovery 30 flights(35 as of Dec. 08 2008)
Atlantis: 26 flights(29 as of Dec. 08 2008)
Endeavour: 19 flights(22 as of Dec. 08 2008)
 
I didn't mean most flown, I meant most loved.
 
I didn't mean most flown, I meant most loved.
Maybe. But there's no change that after 107, the need for her would be greatly reduced with her only having three more flights after 107. They were:

STS-118, Nov., 2003(ISS mission)
STS-122, April 2004(HST SM4)
STS-131, mid-2013(HST retrieval)

So just 3 missions in 10 years. Two if they decided not to persue the HST retrieval mission.


-----Post Added-----


Checked in two new sound files. One is for the RCS jets when they fire(note code needs a change here, currently it plays the attsustain.wav file, which is not correct. The RCS jets are quiet once they have reached steady burn. They do however make quite a noticeable noise when they first fire before reaching stable burn.)

The second one is one for the RSS Rotation.
 
I can do the RSS animation coding. What exactly needs to be done for the payload latches?

Mostly implementing the system to install and release payloads from the payload bay. Like for example defining the active latch positions for both SSU and payload, so we can install payloads (like the MPLM) again into the SSU, together with the "ready to latch" indications.
 
Hi guys.

Two quick questions:

1. When you talk about payload latches, are you talking about having actual payload latch meshes (line Donamy's)? or just attachment points?

2. For the ODS capture, which PMA are you currently planning to use?

Thanks - looking forward to this:)
 
1. When you talk about payload latches, are you talking about having actual payload latch meshes (line Donamy's)? or just attachment points?

Just attachment points - all beauty can come later or when we have more time.

2. For the ODS capture, which PMA are you currently planning to use?

No PMA ... we currently use a modified version of ProjectAlphaISS.cfg.
 
No PMA ... we currently use a modified version of ProjectAlphaISS.cfg.
Although very easily added. It's a special attachment point which can be added to any vessel.
 
Although very easily added. It's a special attachment point which can be added to any vessel.

Exactly, but I doubt we can support a modular ISS. It would have to be a single vessel, otherwise we would get too many special cases to deal with.
 
OK. The latest on the ISSU project is that I have now teamed up with Thorton (as he can now do C++ coding) and so me, Thorton, Xmariox & The Aviator are now working on it (although it is no longer actually called ISSU, it will be re-named).

I sent everyone a PM about it, but I don't think it worked as during the time when I was sending it, I lost my connection. I will re-send.

Anyway, the general plan is to release in stages - first stage release coming soon, as soon as we fix issues. It will be all missions up to and including STS-92 (Z1 truss & PMA-3).

All it will be is exteriors & some systems (like sun-tracking arrays, power & remote vessel control when docked). Interiors + more systems will come later once we have all exteriors done & released.

At the moment we are doing scenarios for SSU & SF.

The current problem is that Thorton's vessels don't work with Vista. The meshes + systems are not visible.

But as soon as we fix it I think it would be OK for you guys to use our PMA for SSU ODS.
 
Back
Top