Idea Shuttle Fleet recompile for Orbiter 2016

[Marg]

Yes. I used 2016ShuttleDeva.dll

P.S. I noticed, shuttle's umbilical doors do not work when pressing Ctrl-J.

 

[gattispilot]

Try this:
slowed IUS by 2. added external hatch also
https://drive.google.com/open?id=1k7mEl0nMPBSPduJt7Hdbe7P3ZdH1gWQy

---------- Post added at 02:57 PM ---------- Previous post was at 02:16 PM ----------

I keep looking at the ase for sts 61c.
We know it is different.
but look at these images:
https://forum.nasaspaceflight.com/index.php?action=dlattach;topic=28160.0;attach=376466;image
notice the doors are open and the curved ring in the middle
https://forum.nasaspaceflight.com/index.php?action=dlattach;topic=28160.0;attach=376466;image notice something else on the left door
https://forum.nasaspaceflight.com/index.php?action=dlattach;topic=28160.0;attach=376458;image

 

[Marg]

Maybe slow a bit more IUS predeployment for ~30% longer, and it will be OK. Now its 23 secs 0-59 degrees.

Umbilical doors are a bit off after opened:
I looked in MeshWizard and it seems that rotation point coordinates for them

could be:
-1.341984, -2.855289, -7.251037

1.341984, -2.855289, -7.251037

 

[DaveS]

Nominal IUS ASE drive time from 0-29° was 3:38, 29-58° was 3:25.

 

[Marg]

Isn't this IUS ASE movement FPS dependant? Because in Orbit I get 3-4 times faster times. (~ 10 secs!). On launch pad (I know it seems strange and unrealistic to do it there), it's 25 s (I use HD launch pads, so some FPS difference can explain this?).

 

[gattispilot]

Isn't this IUS ASE movement FPS dependant? Because in Orbit I get 3-4 times faster times. (~ 10 secs!). On launch pad (I know it seems strange and unrealistic to do it there), it's 25 s (I use HD launch pads, so some FPS difference can explain this?).

maybe so that is why if D3D9 it runs faster?


Sounds like I need to make it slower to match real time?


New sts61C ASE;

---------- Post added at 05:48 PM ---------- Previous post was at 03:56 PM ----------

---------- Post added at 06:12 PM ---------- Previous post was at 05:48 PM ----------

fix the external hatch. In d3d9 I get about 1 minute to get to 29 degrees.
https://drive.google.com/open?id=1jAYSURxo__MWWVipJ5aahYhBPE5FQU4n

 

[Marg]

I forgot to add that "exttank hatches" - umbilical doors also should have rotation axis defined a bit under angle, should be these values:
ROT_AXIS=(0,-0.0523,0.9986)


P.S. IUS ASE still rotates quite fast in orbit.

 

[gattispilot]

Try this dll:
https://drive.google.com/open?id=1COclXNg47bY72kqsL-Z8e04TVY3xbc55

should fix the ext hatch. not sure about IUS. Might need to re think it.

---------- Post added at 05:54 AM ---------- Previous post was at 04:35 AM ----------

So can an animation work without mesh parts?

anim_ius = CreateAnimation(0.0);

	ius_anim[0] = new MGROUP_ROTATE(LOCALVERTEXLIST, MAKEGROUPARRAY(arm_ius), 3, pl1_ofs, _V(1, 0, 0), (float)(-59.0));

	AddAnimationComponent(anim_ius, 0, 1, ius_anim[0]);

So now it does move but shouldn't just move 59 degrees? it is only at .03 ius_proc

what the arm1_tip to be the ius tilt.

if (USEIUS == 1){
			
				if (ius_status >= HATCH_RAISING) {
					double da = simdt * .1;
					if (ius_status == HATCH_RAISING) {
						if (ius_proc > 0.0) EXT_proc = max(0.0, ius_proc - da);
						else ius_status = HATCH_UP;
					}
					else {
						if (ius_proc < 1.0) ius_proc = min(1.0, ius_proc + da);
						else ius_status = HATCH_DOWN;
					}
					SetAnimation(anim_ius, ius_proc);
					sprintf(oapiDebugString(), "armtip3x  %2.2f ", ius_proc);
					xp1 = arm1_tip[1] - arm1_tip[0]; normalise(xp1);
					xr1 = arm1_tip[2] - arm1_tip[0]; normalise(xr1);
					SetAttachmentParams(sat_attach4, pl4_ofs, xp1, xr1);//ase
					SetAttachmentParams(sat_attach, pl1_ofs, xp1, xr1);

but even though the ius_proc is changing the attachment point is moving

---------- Post added at 07:03 AM ---------- Previous post was at 05:54 AM ----------

So what is the releationship to this:

ius_anim[0] = new MGROUP_ROTATE(LOCALVERTEXLIST, MAKEGROUPARRAY(arm_ius), 3, pl1_ofs, _V(1, 0, 0), (float)(-1));

	AddAnimationComponent(anim_ius, 0, 1, ius_anim[0]);

I would think at Proc=1 then it would 1 degree. But this is almost right. But need to know how to get 29 and 59 degrees?

 

[barrygolden]

Gattis not to change the subject but how did using your Eagle VC turn out in the Orion

 

[Marg]

I am still looking on umbilical hatches animation, maybe in meantime update Y coordinates of rotation points to: -2.849617 value. I think it is more accurate, so it should be:

-1.341984, -2.849617, -7.251037

1.341984, -2.849617, -7.251037

 

[gattispilot]

anim_ius = CreateAnimation(0.0);

	ius_anim[0] = new MGROUP_ROTATE(LOCALVERTEXLIST, MAKEGROUPARRAY(arm_ius), 3, pl1_ofs, _V(1, 0, 0), (float)(-1.03));

	AddAnimationComponent(anim_ius, 0, 1, ius_anim[0]);

when proc=1 then the angle is 59. Not sure why though. I like this better as you can save the ius angle

 

[Marg]

I like IUS as it is. Maybe let's keep it as it is. I noticed in orbit, that OMS burn looks odd some particles are there, but they are kinda white squares, and generating source is lower than OMS nozzles. But overall my impression is very good. I adapted Leasat, and PAM-D+HS-376 sats even faster, almost no troubles.

 

[gattispilot]

Oh. I think you will not notice the change. But it is better code. Getting the rotation spin table will be the next change

---------- Post added 12-02-19 at 04:08 AM ---------- Previous post was 12-01-19 at 09:08 AM ----------

so try this dll. new IUS code and new external hatch:
https://drive.google.com/open?id=1CLz1NC_ClvMZfmmXJV9B2FaL7kTgy_Gc

So on the Satellite spin tables.
So the final rotation speed for sts-5 is 50. And it took about 10 secs to get that rate, right

So not sure if we need to see the rpm? Just know when the desired speed is reached?

Haven't found any panels images with the satellite spin controls,.....

 

[Marg]

OK, that's it! Now it's OK - slow (< 1 min) - the same on launch pad and in orbit!

But about PAM-D comsats, I press to begin RPM, it rotates immediately fast (400rpm?) around the same correct shuttle Y axis, then after 3-4 seconds, it suddenly begins to spin normally with 50rpm. From this moment everything (deplyment etc.) is OK.

 

[gattispilot]

Yes. I have new code that I should be able to get out today or so. Will put out the new ase for sts 61c also.

On the IUS code you can speed it up by time acceleration.

 

[Marg]

Wait, I tried again and PAM-D button RPM+ worked normally, everything was OK! Hm, maybe your last change affected that too?

 

[gattispilot]

https://drive.google.com/open?id=1b4wzdT60dpGAFV07ZYfv1P7ZVcKUZ2eQ

This seems to work tested with 2 SPIN1 and SPIN2. SPIN1,SPIN2,SPIN4,AND SPIN 5 ARE ALL 50 RPM
SPIN0 there is no spin until released. Not sure if that is true of if it should rotate
SPIN3 no spin til released

---------- Post added 12-03-19 at 05:11 AM ---------- Previous post was 12-02-19 at 06:50 PM ----------

sts 61c update:
https://drive.google.com/open?id=1zMm22zHR1qLMUpEkWNi_eyye6bzZRItv

I wonder if a new spin may need to made? where the user can adjust the spin rate from the scn. We have 50rpm, 30 rpm.

so k1- satcom does spin:
https://space.nss.org/space-shuttle-flight-24-sts-61c-post-flight-press-conference-video/


"Intelsat VI will be ejected by the springs at about 0.6 feet per second and with a slight rotation of about 0.7 revolutions per minute."

 

[Marg]

Everything is OK. When I started STS-61C orbit scenario, the same problem appeared, but I replaced scenario entry "Shuttle2016B" with "Shuttle2016Deva", and everything worked flawlessly.

 

[gattispilot]

Thanks. I think the way is just to change the cfg of Shuttle2016B to show the Shuttle2016Deva module

 

[Marg]

BTW I noticed mistyped word "ORGINIAL" instead of "ORIGINAL" in some scenarios.