SSU Development Thread (2.0 to 3.0)

Status
Not open for further replies.
STS057-28-013.jpg


Like this?

Yes that would be the TAA aft hatch, but not one on the spacehab.
 
Not working right now, because the distance at which Orbiter automatically snaps the spacecraft together, is closer than the 45 cm to which the ring can be extended.
Well, this can be fixed by us not having a docking port unless the docking ring is fully retracted.
 
Here is the TAA for STS-97, showing no hatches.

Not working right now, because the distance at which Orbiter automatically snaps the spacecraft together, is closer than the 45 cm to which the ring can be extended.

I'm moving code from Atlantis to the ODS and it seems like it doesn't. I'll try to fix it.
 
So what will we assume for the SSU airlock and TAA ?

---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------

Did you remove the circuit protection first?

I don't remember, but I'll try it.
 
Well, this can be fixed by us not having a docking port unless the docking ring is fully retracted.

Loading and saving the state is then a lot more tricky, but possible, yes. :thumbup:
 
Loading and saving the state is then a lot more tricky, but possible, yes. :thumbup:
We attach for contact and capture. Only when we have fully retracted the docking ring is the docking port actually created/enabled. So we do place some responsibility on the docking object creator to make things SSU compatible.
 
We attach for contact and capture. Only when we have fully retracted the docking ring is the docking port actually created/enabled. So we do place some responsibility on the docking object creator to make things SSU compatible.

Yes, since the DOCKHANDLE is an orbiter resource, it would have to be responsibility of the Atlantis class to manage it.

Not sure if we need an additional flag in the scenario file there to the status of the ODS ring or latches, maybe the ODS can signal the Atlantis class that docking was possible in its current stage after loading or can request a state change during runtime, which would be again sanity-checked by the Atlantis class.
 
Another question: Is the Mir docking adapter, roughly the same size as the MRM1
(Rasvet) ?
 
Another question: Is the Mir docking adapter, roughly the same size as the MRM1
(Rasvet) ?
According to the STS-74 presskit the Docking Module is 4.69392 m (15.4') long and has diameter of 2.19456 m (7.2') and a mass of 4081.983 kg (9,011 lbm).
 
Another question: Is the Mir docking adapter, roughly the same size as the MRM1
(Rasvet) ?

Not sure. In my opinion, MRM1 is a similar design, but stretched and the external support systems on the primary hull are placed differently.

Also, both have different kinds of passive TCS.

---------- Post added at 11:14 PM ---------- Previous post was at 11:08 PM ----------

According to the STS-74 presskit the Docking Module is 4.69392 m (15.4') long and has diameter of 2.19456 m (7.2') and a mass of 4081.983 kg (9,011 lbm).

Fits to my observation then. The MRM1 is about 6 meters between the docking ports.
 
Last edited:
How about having a seperate EVA hatch mesh, that can be placed at attachment points, of the different modules, that will have their own animations and be able to have better detail.

---------- Post added at 09:29 PM ---------- Previous post was at 09:24 PM ----------


Are the measurements with or without the docking probe ?
 
How about having a seperate EVA hatch mesh, that can be placed at attachment points, of the different modules, that will have their own animations and be able to have better detail.

---------- Post added at 09:29 PM ---------- Previous post was at 09:24 PM ----------



Are the measurements with or without the docking probe ?
DM or MRM-1?
 
The diagram I have shows the DM not having the probe.
That's because both docking systems on the DM was APAS. The Kristall module only had APAS ports, no probe&drogue.
 
I was refering to the difference in length, being due the probe on the Rassvet.
 
So, looking at the attachment search code, there's an offset in the attachment that I still need to solve and is still missing the "attach the target" part and then testing, so IMO if we want to get this working well and also to release this Tuesday this should be delayed to the next version. We put a big warning in the manual stating that from next version on, SSU requires such and such docking mechanism, and this way both us and the addon devs get time to work this out.

---------- Post added 08-16-15 at 12:00 AM ---------- Previous post was 08-15-15 at 11:23 PM ----------

Another thing: payload bay floodlights, are on or off during launch and landing? From videos it seems they are on for launch and off for landing, but the launch part doesn't make much sense to me...
 
So, looking at the attachment search code, there's an offset in the attachment that I still need to solve and is still missing the "attach the target" part and then testing, so IMO if we want to get this working well and also to release this Tuesday this should be delayed to the next version. We put a big warning in the manual stating that from next version on, SSU requires such and such docking mechanism, and this way both us and the addon devs get time to work this out.

---------- Post added 08-16-15 at 12:00 AM ---------- Previous post was 08-15-15 at 11:23 PM ----------

Another thing: payload bay floodlights, are on or off during launch and landing? From videos it seems they are on for launch and off for landing, but the launch part doesn't make much sense to me...
The lights are off when not needed to conserve reactants for the fuel cells.
 
Status
Not open for further replies.
Back
Top