Idea Shuttle Fleet recompile for Orbiter 2016

So no need for release key. Makes sense. I will recode it. Might try it in 2010 but may need to add a attachment id?

---------- Post added at 06:12 PM ---------- Previous post was at 01:43 PM ----------

Here is the STS109 scn with working sts109 payload. G rotates FFSS and n/m rotate the ring. Autoattach to HST
https://drive.google.com/open?id=1Qrgo0t4WHkz0ZkUEiFDQjzLaHXQwiqjX

---------- Post added 10-19-19 at 05:54 AM ---------- Previous post was 10-18-19 at 06:12 PM ----------

So the payload works in 2010 also. But which hst should we use?
I have a a mesh name hst109. which seems plain.
Uj4xXlz.jpg

But yoy need to add an attachment point to bottom of the HSt and it needs an id of SCM
 
So no need for release key. Makes sense. I will recode it. Might try it in 2010 but may need to add a attachment id?

---------- Post added at 06:12 PM ---------- Previous post was at 01:43 PM ----------

Here is the STS109 scn with working sts109 payload. G rotates FFSS and n/m rotate the ring. Autoattach to HST
https://drive.google.com/open?id=1Qrgo0t4WHkz0ZkUEiFDQjzLaHXQwiqjX

---------- Post added 10-19-19 at 05:54 AM ---------- Previous post was 10-18-19 at 06:12 PM ----------

So the payload works in 2010 also. But which hst should we use?
I have a a mesh name hst109. which seems plain.
Uj4xXlz.jpg

But yoy need to add an attachment point to bottom of the HSt and it needs an id of SCM

GREAT WORK ! :thumbup: :thumbup:

That's the result for Orbiter2016 :hailprobe:









 
"That's the result for Orbiter2016" - shadows could be enabled as well to make it even more realistic :)
 
Great and Thanks. Working on a sts125. But I think close to a release then can update this make more scns......

---------- Post added at 02:14 PM ---------- Previous post was at 05:15 AM ----------

So what description should we use for this add on?
 
I just noticed, if there is a need to specify some historic cloud cover\amount during historic launch, Solxxx can be specified pointing to a certain Earthxxxx.cfg. There is (as all of you know) cloud altitude, and - the main thing - cloud rotation period in that file.
It's default value is 2e6, but if you change it to, say 2.0001e6, you will get different conditions (clouds). I had ugly seam during STS-109 launch so I changed 1.99999e6, and it moved away (~50-100km?). Value is sensitive, 1.999e6 or 2.001e6 will give significant difference.
 
Where is the OBSS?
Anyone tried a scn with it in it?
Try this code:
Code:
BEGIN_DESC

END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 54962.745093
END_ENVIRONMENT

BEGIN_FOCUS
  Ship ET-125
END_FOCUS

BEGIN_CAMERA
  TARGET ET-125
  MODE Extern
  POS 2.382272 -102.079718 48.976758
  TRACKMODE Ground Earth
  GROUNDLOCATION -80.60370 28.60763 85.00
  FOV 40.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Map
  REF Earth
  BTARGET Cape Canaveral
  OTARGET HST
END_MFD

BEGIN_MFD Right
  TYPE Orbit
  PROJ Ship
  REF Earth
  FRAME Equator
  TARGET HST
  ALT
END_MFD


BEGIN_SHIPS
STS-125:Shuttle2016B
  STATUS Orbiting Earth
  RPOS 3370476.630 997170.515 6015534.471
  RVEL -6366.9909 -1467.2086 3810.5058
  AROT -127.013 -18.177 59.509
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  CONFIGURATION 3
  OV 104
  RMSARM
  OBSS
  CARGODOOR 1 1.0000
  KUBAND 1 1.0000
  POSTLAND 0 0.0000
  SSMES 1 1.0000
  ADTA 0 0.0000
  PETD 0 0.0000
  SETD 0 0.0000
  ARMTILT 0 0.0000 0 0.0000
  PRADIATOR 0 0.0000
  SRADIATOR 0 0.0000
  GEAR 0 0.0000
  PAYLOAD_MASS 0.0000
  ARM_STATUS 0.5000 0.1122 0.0849 0.5000 0.5000 0.5000
  SAT_OFS_X 0.000
  SAT_OFS_Y 0.000
  SAT_OFS_Z 0.000
  PL1_OFS 0.0000 -2.000 0.0000
  PL1_DIR 0.0000 1.0000 0.0000
  PL1_ROT 0.0000 0.0000 1.0000
  PL2_OFS 0.046000 0.280000 -3.000000
  PL2_DIR 0.000000 1.000000 0.000000
  PL2_ROT 0.000000 0.000000 1.000000
  PL3_OFS 0.045000 0.180000 -0.234000
  PL3_DIR 0.000000 1.000000 0.000000
  PL3_ROT 0.000000 0.000000 1.000000
  PL4_OFS 0.0030 -0.260 10.400
  PL4_DIR 0.0000 1.0000 0.0000
  PL4_ROT 0.0000 0.0000 1.0000
  PL5_OFS 0.046000 0.280000 -8.300000
  PL5_DIR 0.000000 1.000000 0.000000
  PL5_ROT 0.000000 0.000000 1.000000
  PL6_OFS 2.128000 0.680000 -5.010000
  PL6_DIR 0.000000 1.000000 0.000000
  PL6_ROT 0.000000 0.000000 -1.000000
  KEEL_CAM 0.145000 -0.500000 -1.356000
  FLOOD1 0 
  FLOOD2 0 
  FLOOD3 0 
  FLOOD4 0 
  FLOOD5 0 
  FLOOD6 0 
  DOCK_LIGHT 0 
  AFT_LIGHT 0 
  RMSLIGHT 0 
END
ExtAL:ExtAL-1
  STATUS Orbiting Earth
  RPOS 3370476.630 997170.515 6015534.471
  RVEL -6366.9909 -1467.2086 3810.5058
  AROT -127.013 -18.177 59.509
  ATTACHED 0:4,STS-125
  AFCMODE 7
  NAVFREQ 0 0
END
OBSS:SHUTTLE_OBSS2016
  STATUS Orbiting Earth
  RPOS 3370476.630 997170.515 6015534.471
  RVEL -6366.9909 -1467.2086 3810.5058
  AROT -127.013 -18.177 59.509
  ATTACHED 0:11,STS-125
  AFCMODE 7
  NAVFREQ 0 0
END
END_SHIPS
I added the External Airlock from the [ame="https://www.orbithangar.com/searchid.php?ID=7031"]STS-95[/ame] addon
 
Thanks. But I thought I had it hard coded. So in the scn if you have OBSS it shows it and then you can detach/reattach in the panel.

---------- Post added at 08:32 AM ---------- Previous post was at 07:38 AM ----------

Also do we want 2 rms different arms. I am using Donamy arm. But for early shuttle it may not be correct
 
I just noticed, if there is a need to specify some historic cloud cover\amount during historic launch....

Don't know if they are online, but I'm sure there are global cloud cover images for every day since the 1970's somewhere....
Just for the sake of discussion, since resolution will be too low for our purposes. But in theory there's data (somewhere) to simulate accurate cloud cover.
 
The other thing that might be nice is notation on the screen for which camera? I think i can add that.

On the rms I use my eyesight to align the arm. I guess you are to use the arm end camera. But it clips out when you get to the target.

Not sure if there is a way to graphic display how close/far to the target.
 
Don't know if they are online, but I'm sure there are global cloud cover images for every day since the 1970's somewhere....
Just for the sake of discussion, since resolution will be too low for our purposes. But in theory there's data (somewhere) to simulate accurate cloud cover.
Actually I thought only about cloud cover near KSC :) I did not mean it globally. Because meteorology is noticable during first minute after launch or so... but it also makes sense.
Back to Shuttle2016 topic...

P.S. I always have CTD when trying to switch to cockpit view (Shuttle2016 in Orbiter 2016) ... maybe there is specific shuttle cockpit .msh I missed?
 
Last edited:
Weird. Can you post the log.

I think I am going to try to add on screen notations so in the VC the screen will say RMS elbow,.......

---------- Post added at 06:21 PM ---------- Previous post was at 01:01 PM ----------

So like this:
DsxvLyn.jpg


Still not sure about RMS positioning?


yes this adds the OBSS:
Code:
OBSS:SHUTTLE_OBSS2016
  STATUS Orbiting Earth
  RPOS 3370476.630 997170.515 6015534.471
  RVEL -6366.9909 -1467.2086 3810.5058
  AROT -127.013 -18.177 59.509
  ATTACHED 0:11,STS-125
  AFCMODE 7
  NAVFREQ 0 0
END

What OBSS in the scn does is add the OBSS holder

---------- Post added at 07:21 PM ---------- Previous post was at 06:21 PM ----------

So on the rms not sure how to fix the clipping.
UrRyx9X.jpg

7tHLCfH.jpg

Then I attach
KqfIAes.jpg

vUOaXz8.jpg



So I ran the scn in 2010 and the arm didn't see the CTA
 
DX9 removes clipping.
 
Will I get this in dx9
t1Mgoic.jpg


So for some reason bay lights not coming on. Beacons are seen
I have local light sources check.
tGbnksd.jpg


fixed the tranlsation so the speed can be changed

But do we need a target or something on screen to aim for the target for rms?
 
You can disable near clipping in Dx9
 
Not sure. is it a setting. Not sure why no lights.

I might relook at the payload camera and see about tilt/pan and rms elbow
 
I also do not have PBlights illuminating anything in shuttle bay, only "lamps" shine. But all other lights are working (LP39A, BJones spotlight etc.).
 
I fixed mine. I was running dxd9_flat. Once I switched to dxd9 and reset thing. Selecting local lights.
l6GRxHr.jpg

and selected no clipping.
FFBqLLs.jpg
 
You should label that RMS EE Camera.
 
Thanks. One change I need to make is on the cameras.

I noticed in Sf that in VC or NOT you see the payload bay. In mine you have to be in VC mode.

I think it is just telling how to see the mesh.

That actually will solve an label issue.

Getting sts125 closer.

---------- Post added 10-24-19 at 05:34 AM ---------- Previous post was 10-23-19 at 05:51 AM ----------

So try this out.

https://drive.google.com/open?id=1hFxb_RHfXugaXnFgm3dThb5XQlYQ-pzG

It is a cfg and dll . The cfg will override the shuttle cfg. So back it up. That way the scn will work with the new dll.

So basically with this you can be in cockpit view and see the views. VC or NOt.

The one thing I liked about it was in the arm the hud is present so you get a canter of reference?

But let me know what you think.

In the old version to see the from the payload camera you had to be in VC mode.

also fixed the translation speed.
 
Last edited:
Back
Top