Space Shuttle Ultra development thread

[Urwumpe]

I just tried out the prototype of the MLP. Just have one slight problem: as soon as I start up a scenario, smoke and steam begins to appear.

Any way of disabling this until SSME start and SRB ignition?

I thought I had it fixed already, I had the same problem caused by uninitialized variables in the beginning.

There should be no smoke and steam before you activated the sound suppression system - and that only for 20 seconds until it runs out of water. And currently, the only thing which can activate the SSS is the Shuttle itself - when you start the main engines, it automatically triggers the SSS. There is no manual test - yet. :dry:

I want to copy some code from another project soon and generate the small water spray nozzles around the MPS hole as particle effect. Then you should be able to see if the SSS is activated.

After running out of water, my plan is to automatically refuel the water tank.

 

[DaveS]

Any updates on the MLP bug?

 

[Urwumpe]

Any updates on the MLP bug?

I just committed a version with a more clean initialization, I can't replicate the bug on my PC, maybe you are now without it.

 

[DaveS]

I just committed a version with a more clean initialization, I can't replicate the bug on my PC, maybe you are now without it.

Didn't fix it.

Here's the scenario I'm testing it with:

BEGIN_DESC
Launch Space Shuttle Atlantis from Launch Complex 39B at the Kennedy Space Center for mission STS-106. T0 is set for 1245:47 UTC.
END_DESC
BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51795.528322
END_ENVIRONMENT
BEGIN_FOCUS
  Ship STS-106
END_FOCUS
BEGIN_CAMERA
  TARGET STS-106
  MODE Extern
  POS 2.89 -0.51 -70.39
  TRACKMODE TargetRelative
  FOV 50.00
  BEGIN_PRESET
    Track:STS-106:50.00:GLOBAL 6.339 2.651 1.373
    Ground:STS-106:50.00:Earth -80.62110 28.61957 68.08 3.07 -0.05
  END_PRESET
END_CAMERA
BEGIN_HUD
  TYPE Surface
END_HUD
BEGIN_MFD Left
  TYPE Surface
END_MFD
BEGIN_MFD Right
  TYPE Orbit
  PROJ Ship
  REF Earth
END_MFD
BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS -3833430.64 5480334.56 -803952.35
  RVEL 6169.424 3967.476 -2315.171
  AROT 110.00 -10.00 80.00
  PRPLEVEL 0:1.000
  IDS 0:1 10 1:2 10 2:3 10 3:4 10 4:5 10
  NAVFREQ 0 0
  XPDR 466
END
Mir
  STATUS Orbiting Earth
  ELEMENTS 6671000.0 0.00060 3.50000 360.00000 0.05110 157.31997 51982.90674797
  AROT 5.00 10.00 15.00
END
STS-106:Atlantis
  STATUS Landed Earth
  ;BASE Cape Canaveral:11
  POS -80.6232502 28.6197342
  ATTACHED 0:0,MLP
  HEADING 2.00
  PRPLEVEL 0:1.000 1:1.000 2:1.000 3:1.000 4:1.000 5:1.000 6:1.000 7:1.000 8:1.000
  NAVFREQ 0 0
  CONFIGURATION 0
  CARGODOOR 0 0.0000
  GEAR 0 0.0000
  OPS 101
  WING_NAME Atlantis
  USE_MLP
  KUBAND 0 0.0000
  AUTOPILOT 51.60 80.5 105000 7607.601 0.73
  RMS
  ROLLOUT 0 0.00000
  ARM_STATUS 0.5000 0.0136 0.014688 0.5000 0.5000 0.5000
  HEADS_UP 12966.67
  THROTTLE_BUCKET 1399.67 1670.67
  LOMS 1
  ROMS 1
  BOILERN2SPLY0 0
  BOILERN2SPLY1 0
  BOILERN2SPLY2 0
  BOILERCNTLR0 0
  BOILERCNTLR1 0
  BOILERCNTLR2 0
  BOILERHTR0 0
  BOILERHTR1 0
  BOILERHTR2 0
  APUFUTKVLV0 1
  APUFUTKVLV1 1
  APUFUTKVLV2 1
  APUCNTLRPWR0 1
  APUCNTLRPWR1 1
  APUCNTLRPWR2 1
  HYDCIRCPUMP0 1
  HYDCIRCPUMP1 1
  HYDCIRCPUMP2 1
  APUAUTOSHTDN 0
  APUSPDSEL0 1
  APUSPDSEL1 1
  APUSPDSEL2 1
  APUCNTRL0 1
  APUCNTRL1 1
  APUCNTRL2 1
  HYDMNPMPPRESS0 0
  HYDMNPMPPRESS1 0
  HYDMNPMPPRESS2 0
  MPSENGPWR00 0
  MPSENGPWR01 0
  MPSENGPWR02 0
  MPSENGPWR10 0
  MPSENGPWR11 0
  MPSENGPWR12 0
  HEISOLA0 0
  HEISOLA1 0
  HEISOLA2 0
  HEISOLB0 0
  HEISOLB1 0
  HEISOLB2 0
  APU0 0
  APU1 0
  APU2 0
  MPS0 1
  MPS1 1
  MPS2 1
  L_ET_UMB_DOOR 1.000
  R_ET_UMB_DOOR 1.000
  ET_DOOR_LATCHES 0.000000 1.000000 1.000000
END
MLP:Atlantis_MLP
  STATUS Landed Earth
  POS -80.6232502 28.6197342
  HEADING 2.00
END
END_SHIPS

 

[DaveS]

Here's an update on the MLP mesh. Now all the Side 1 stairs and decks are in place. Just need to add the handrails.

 

[dbeachy1]

Hey Donamy... are you an addon developer? Let me know if so and I'll move you to that forum usergroup.

Yes, Don is definitely an add-on developer -- he developed the Resolve as well as much of the mesh in David413's Shuttle Fleet (soon to be replaced by the Shuttle Ultra, I hope!) Don also developed much of the VC in the default Atlantis and also worked on the XR1's mesh as well as developing early prototype meshes for the XR5 Vanguard. :speakcool:

 

[myles]

Urg, another issue. When in "glass cockpit" view, I get the normal 150ish FPS. When I switch to the VC or external view, I get 60-70ish FPS, which is fine with me. But, when I time warp with external view or VC, I get 14ish FPS, which must be a problem somewhere.

EDIT: Forgot to mention, during ascent, if you turn autopilot off, and dont press any controls, the shuttle wants to pitch "down" (head towards vertical again)

 

[DaveS]

Urwumpe, I just wondered: how do you plan to deal with the various cameras on the MLP? There's at least 10 OTV cameras and at least 20 engineering cameras on each MLP.

 

[Urwumpe]

Daves: Sorry, still no change. Using your scenario, I get the same effect as before. No smoke before I activate the main engines

About the Cameras: My idea was making a pseudo VC on the MLP, allowing you to switch through all cameras like in the Shuttle Payload bay. An annotation should get used for displaying which camera you use for a few seconds after each switch.

 

[DaveS]

Daves: Sorry, still no change. Using your scenario, I get the same effect as before. No smoke before I activate the main engines

Any way to troubleshoot? I could try to remove the shuttle from the scenario and see if it makes a difference.

About the Cameras: My idea was making a pseudo VC on the MLP, allowing you to switch through all cameras like in the Shuttle Payload bay. An annotation should get used for displaying which camera you use for a few seconds after each switch.

Hmm, that would be nice! Well, technically, you could keep the annotation on forever as they're not ever removed on the real camera feeds.

Take it from somone who has been wathcing the OTVs for many, many hours throughout the years.

 

[Urwumpe]

Any way to troubleshoot? I could try to remove the shuttle from the scenario and see if it makes a difference.

I could print the status variables of the MLP into the Debug String and write events into the log file. Removing the shuttle would at least help limiting the cause of the bug.

Did you try deleting the MLP module and make a clean new compilation?

 

[DaveS]

I could print the status variables of the MLP into the Debug String and write events into the log file. Removing the shuttle would at least help limiting the cause of the bug.

Do that and I'll remove the shuttle.

Did you try deleting the MLP module and make a clean new compilation?

Yes. Made no change. How about upload your module here and see if it might be me who has screwed up the compilation.

 

[DaveS]

Just did a MLP stand-alone test: No change.

 

[zerofay32]

Hey guys. I'm still having trouble getting all the new stuff to work. I was wondering if you were going to post an update to OrbitHanger.

Thanks,

Zerofay32

 

[DaveS]

Hey guys. I'm still having trouble getting all the new stuff to work. I was wondering if you were going to post an update to OrbitHanger.

Thanks,

Zerofay32

We'll work out the bugs first.

 

[zerofay32]

Understood.

Great work so far.

zerofay32

 

[Urwumpe]

Yes. Made no change. How about upload your module here and see if it might be me who has screwed up the compilation.

Here it comes. I included a cryptic debug string output, which is active all the time.

 

[DaveS]

Here it comes. I included a cryptic debug string output, which is active all the time.

That cured it! MLP is in-active now on scenario start-up.

Edit:
Now, there's anothe problem: the SSWS doesn't activate anymore. Fired up the SSMEs and lifted-off, no steam or smoke.

 

[Urwumpe]

Now, there's anothe problem: the SSWS doesn't activate anymore. Fired up the SSMEs and lifted-off, no steam or smoke.

Strange. The same modules produced smoke here. Can you get me the state?

 

[DaveS]

Strange. The same modules produced smoke here. Can you get me the state?

You mean what the devug string outputs?