# IdeaShuttle Fleet recompile for Orbiter 2016

#### gattispilot

More views Sts41B

#### asbjos

##### tuanibrO
...
A code issue though.
so the RCS thrusters are created.

Code:
th_rcs[0] = CreateThruster(_V(6, 0, 10), _V(0, -1, 0), JET_THRUST, main_tank, JET_ISP);
So I want the thrust amount to be 1/2 when in rotation mode. So in the poststep.
Code:
if (GetAttitudeMode() == RCS_ROT) JET_THRUST = .4;
if (GetAttitudeMode() == RCS_LIN) JET_THRUST = .8;
But it remains the same. Not sure if I need to clear the values and reload?
Orbiter doesn't monitor the JET_THRUST value after the creation of th_rcs. So you have to redefine the thruster. See SetThrusterMax0 in API reference.

#### gattispilot

Thanks fixed the MMU thrust.

Thinking about doing it like the eva guy by using attachments. Easy to control the MMU.

#### gattispilot

So I am stumped. Trying to set up sts41b. They had 2 satellites. Following sts 5 for example.
Code:
PAM-1:STS_PAYLOADS\PAM
STATUS Orbiting Earth
ATTACHED 0:0,STS-5
PRPLEVEL 0:1.000
END
STATUS Orbiting Earth
ATTACHED 0:0,PAM-1
END
STATUS Orbiting Earth
ATTACHED 0:0,STAR-48B1
END
STATUS Orbiting Earth
ATTACHED 0:0,STAR-30B1
PRPLEVEL 0:1.000
CONFIGURATION 1
END
so looking at the cfg for HS-376
Code:
; === Configuration file for vessel class NASA ASE PAM ===
ClassName = HS-376
Module = Spacecraft3

; === Attachment specs ===
BEGIN_ATTACHMENT
P 0 0 -2.28  0 0 -1  0 1 0 XS ; TO PAM EQUIPMENT
P 0 0 -1.13  0 0 1  0 1 0 XS ; TO STINGER
C 0 0 1.13  0 0 1  0 1 0 XS ; TO A-FRAME
C 0 0.17 -2.95  0 0 1  0 1 0 XS ; TO STINGER
END_ATTACHMENT
So I expected to find in spacecraft hs-376. But nothing.
The Westar-IV and Palaya b2 ini are there but no attachment value.

---------- Post added 04-21-20 at 06:11 AM ---------- Previous post was 04-20-20 at 02:54 PM ----------

Fixed. I modified the satellites cfg/ini to add attachment points.

Sts 41B cargobay. 2 MMUs,.......

#### moonheart

##### Member
Looks amazing - great work! Will you be releasing a version soon? It maybe worth having a "final" release and then periodic updates so folks can enjoy all your hard work.

Thanks again.

#### gattispilot

So I can put together a zip or 2 of what we have. For the most part we are good.
Still working on STS41b and MMU,....

I added 5 generic shuttles. So if you want repaint of the shuttles you can repaint the texture and there you gSo here are the cfg,meshes, modules,:

And here are the scn and textures.

And then this will update the meshes and dll for the new hatch:

Last edited:

#### gattispilot

sts41B with 2 MMU,.... Pappy2 and I have been working out details,....

#### pappy2

##### Member
And the work of "Gattispilot" is EXTRAORDINARY

#### gattispilot

So I hope someone has tried the zips.

So one thing we have been looking at is the eva guys. Then found out basically 2 types one earlier eva and then a later with the safer system on.

and no SAFER

the big differences are the bottom of the pack and numbers and no nasa meatball
Any thoughts ideas,......
So sure I can make new meshes with both. But how to tell the shuttle which guy you want.
https://en.wikipedia.org/wiki/Simplified_Aid_For_EVA_Rescue

---------- Post added 05-01-20 at 06:32 AM ---------- Previous post was 04-30-20 at 04:44 PM ----------

So been watching videos of eva and I notice something wrong with the shuttle model.

So I have the eva hatch open into the payload bay. But it looks like it there is a white cover with no window that opens into the payload bay. The hatch open in?

So it is a thermal blanket. I guess I will need to redo the mesh.

Last edited:

#### Donamy

Donator
Beta Tester
Correct. Look at the Quest in my ISS model.

#### gattispilot

Correct. Look at the Quest in my ISS model.
Thanks. So back to the drawing board. I will make the thermal cover. So to EVA the thermal cover will move into the Payload and the main hatch will move move into the shuttle. So may I reuse your hatch texture?

---------- Post added at 09:39 AM ---------- Previous post was at 08:50 AM ----------

So Donamy if I may resuse your texture we will get this:

Last edited:

#### gattispilot

So we will get this. I might make the cylinder in the center whole rather than have an inside wall

Been rethinking the whole eva process

#### DaveS

##### Space Shuttle Ultra Project co-developer
Donator
Beta Tester
If you want a good close up of the aft hatch of the shuttle airlock, look here: [ame]https://youtu.be/KkxdV1cT_D4?t=2205[/ame]

This is from STS-80 when the gear mechanism for the aft hatch broke and prevented the planned EVA by Tom Jones and Tammy Jernigan had to be cancelled as they couldn't unlatch it and get it swung open.

#### gattispilot

Thanks
Now we get:

and this:

Not sure if I should animate that real outer hatch or leave as is?

#### Donamy

Donator
Beta Tester
Thanks. So back to the drawing board. I will make the thermal cover. So to EVA the thermal cover will move into the Payload and the main hatch will move move into the shuttle. So may I reuse your hatch texture?

---------- Post added at 09:39 AM ---------- Previous post was at 08:50 AM ----------

So Donamy if I may resuse your texture we will get this:

Why don't you take the whole Hatch and animate it, like the quest ?

#### gattispilot

I am not sure what you are saying?

So have the cloth cover animate and the hatch also? That is doable

---------- Post added 05-04-20 at 06:52 AM ---------- Previous post was 05-03-20 at 01:12 PM ----------

So we get this:

#### pappy2

##### Member
I am not sure what you are saying?

So have the cloth cover animate and the hatch also? That is doable

---------- Post added 05-04-20 at 06:52 AM ---------- Previous post was 05-03-20 at 01:12 PM ----------

So we get this:

Last edited:

#### gattispilot

So the next thing I want to do is make eva more universal. Still will have 4 eva guys. But basically 2 styles with SAFER and no SAFER system. EV! will be red stripe, ev2 no stripe, 3 candycane and 4 solid blue.

On the code part I want to be able to read from the scn which eva guys and name and cfg.
So now I get a ctd when I spawn the guy.
H:
Code:
//eva
char crew1_name[256];
char crew2_name[256];
char crew3_name[256];
char crew4_name[256];
char crew1_cfg[256];
char crew2_cfg[256];
char crew3_cfg[256];
char crew4_cfg[256];
then read the info on the crew1 name and cfg:
Code:
if (!strnicmp(line, "CREW1", 5)) {
sscanf(line + 5, "%s%s", &crew1_name, &crew1_cfg);
}
and here I spawn the read crew1 info.
Code:
void Atlantis::SpawnEVA(void)
{
if (EVA1 == 0){
//if (EXT_status == HATCH_DOWN){
{
if ((ODS == 1) || (EXTAIRLOCK == 1))ft_pad_att_pos = _V(0, 0.3, 8.5);

//OBJHANDLE hVessel;
VESSELSTATUS vs;
GetStatus(vs);
hMMU = oapiCreateVessel(crew1_name, crew1_cfg, vs);

VESSEL *v = oapiGetVesselInterface(hMMU);
ATTACHMENTHANDLE hAttWFC = v->GetAttachmentHandle(true, 0);
oapiSetFocusObject(hMMU);
EVA1 = 1;
//}
}
}
}
I get a CTD now with this issue.
Code:
000016.284: >>> ERROR: No vessel class configuration file found for:
============================ ERROR: ===========================

[Vessel::OpenConfigFile | .\Vessel.cpp | 243]
===============================================================
000016.284: >>> TERMINATING <<<
and the scn:
CREW1 JOHN SHUTTLEEVA1

#### Donamy

Donator
Beta Tester
Maybe you could have a Crew.cfg, with the names of the rlf astronauts who did the EVA.