# ProjectSpace Transportation System 2016

#### Marg

##### Active member
Aah, I just did not see it. Then it's OK.

#### gattispilot

I thinkit it is more like this. The pallet part is now seen

Working on the camera to be animated. The 2 GAS clinders are now.

#### gattispilot

Now the cameras work

#### gattispilot

Here is the view from the pallet

Tether set up. For some reason it will show the tss grap point.

Here is attached.

The tss has RCS
View of the TSS

#### gattispilot

Now the cameras in the HAB pod work. Like the shuttle it can do eva

Now we have the pieces to put together STS46 and STS 57. Want I need is a person to put them together and make the scenarios.

#### Jeremyxxx

##### Active member
I have found one of the Shuttle concept variants with an modified external tank equipped with a cargo fairing.

#### gattispilot

Redid the Eucera. I added a hatch that open to expose test equipment

I have found one of the Shuttle concept variants with an modified external tank equipped with a cargo fairing.

So that can be done. But it would just be a mesh. To make it into a vessel and hold cargo would take some coding,....

#### gattispilot

redid the sts46 mesh to have the 4 GAS in the aft section. Here CONCAP II is open. I think on the tether. I am thinking of just make the TSS move up and scale the tether?

#### gattispilot

Redid the TSS structure.

With this it makes sts 75 easy. But still how to do the tether? I think the way to go is just scale the tether and move the attachment. The Sat will just go straight up.

#### gattispilot

I am going to try to scale the tether. This is where I will need help.

the tether is going thru the sat

The final distance was 850 feet or 256.08 meters. 2 factors are involved. 1 scaling and 2 moving the attachment point.
Animation proc goes from 0-1. So at 1 the attachment needs to move 256.08 meters

 if (TETHER_out == 1) {// extends sat by scaling TETHER_proc = TETHER_proc + 0.000390625;//1/256.08 if (TETHER_proc >= 1)TETHER_proc = 1; } if (TETHER_in == 1) {// retract sat by scaling TETHER_proc = TETHER_proc - 0.000390625; if (TETHER_proc <= 0)TETHER_proc = 0; } SetAnimation(anim_TETHER, TETHER_proc); if (TETHER_proc == 0) { boom_y = int_boom + (BOOM_proc * 12); SetAttachmentParams(BOOM, _V(0, boom_y, 4.288), _V(0, 1, 0), _V(0, 0, -1)); } if (TETHER_proc > 0) { boom_y = int_boom + (TETHER_proc*256.08)+(BOOM_proc * 12); // move attachment for tether and boom SetAttachmentParams(BOOM, _V(0, boom_y, 4.288), _V(0, 1, 0), _V(0, 0, -1)); } 

 static UINT SGrpANTTETHER[1] = { GRP_BOOM1E };//TETHER static MGROUP_SCALE ANTTETHER(0, SGrpANTTETHER, 1, _V(0, -.753, 0), _V(1, 256.08, 1));//256.08METERS TO 850 FEET AddAnimationComponent(anim_TETHER, 0, 1, &ANTTETHER, BOOMparent); 

#### gattispilot

Got it to work. For some reason the tether is being seen in the camera though?

STS 46 released the 800 feet. STS 75 released the sat 12 miles.

#### gattispilot

STS46 launch into orbit:

cargo bay:

So the SAt was to be deployed 12 miles. But there was an issue so only 860 ft. I may make it go 12miles but stop at 860 ft.

#### gattispilot

I am able to get the sat and attachment/tether to 12 miles.
The one thing I can get to work is the time advance.
 double dtE = simdt * 0.0000005; if (TETHER_out == 1) {// extends sat by scaling TETHER_proc = ((TETHER_proc + 0.0000005));//1/256.08 if (TETHER_proc >= 1)TETHER_proc = 1; } if (TETHER_in == 1) {// retract sat by scaling TETHER_proc = ((TETHER_proc - 0.0000005) ); if (TETHER_proc <= 0)TETHER_proc = 0; } SetAnimation(anim_TETHER, TETHER_proc); 

if I do this:
 TETHER_proc = ((TETHER_proc +dtE));//1/256.08
it does nothing

#### gattispilot

Not sure if me or orbiter. I am setting up scenarios for sts 46. I launch and then accelerate time to the correct time. With 1 hour of the launch the shuttle reentering the atmosphere

This is the guidance I have:
 -30.000 =orbit(425,437,28.45,-1) -6.0 =engine(0,100,6) 3.0 =engine(100,104.5,1.00) 30.0 =engine(104.5,72.00,5.00) 55.0 =engine(72.0,104.5,5.00) 512.0 =jettison() 

This is what I get for the orbit mfd.

I saw where the orbit may have issues in mfd2015 and the newest d3d9. I have r4.11

#### Gargantua2024

##### The Desktop Orbinaut
Not sure if me or orbiter. I am setting up scenarios for sts 46. I launch and then accelerate time to the correct time. With 1 hour of the launch the shuttle reentering the atmosphere

This is the guidance I have:
 -30.000 =orbit(425,437,28.45,-1) -6.0 =engine(0,100,6) 3.0 =engine(100,104.5,1.00) 30.0 =engine(104.5,72.00,5.00) 55.0 =engine(72.0,104.5,5.00) 512.0 =jettison() 
The orbit value is too high and too circular for the Shuttle's launch profile, that's why the resulting orbit does not match the specified values....usually the initial perigee is only about ~100 km to allow the external tank to reenter the atmosphere quickly while the initial apogee is around 200-300 km. The orbiter's OMS engines then circularize itself to its desired orbit once it reaches the said initial apogee

#### gattispilot

Thanks
From the sts 46 press kit:
Altitude: 230 n.m. x 230 n.m. (EURECA deploy) 160 n.m. x 160 n.m. (TSS operations) 128 n.m. x 128 n.m. (EOIM operations) Inclination: 28.5 degrees

230 nm =425.96km

So what should the orbit be? I wonder why the difference between d3d9 and default? I wonder if there is away to set the scenario with the different orbits?

#### Gargantua2024

##### The Desktop Orbinaut
At launch, the normal altitude of the shuttle's initial orbit is always 100-300 km regardless of mission type and orbital inclination. The crew manually take the shuttle to its desired altitude as stated in various press kits

#### Gargantua2024

##### The Desktop Orbinaut
So what should the orbit be?
All orbital values in the press kit are valid. You can make three separate scenarios out of it if you want to, or just simply pick one.

Last edited:

#### Marg

##### Active member
My guidance typically is like -31.000 =orbit(117,296,28.45,-1), usually MECO is at 117 km. And after a half-orbit I manually fire OMS, to circularize at 296 km.
But for some reason when MECO happens orbit is like -55 km x 450km.. too elliptic, I cannot figure out why.