Project Orion MPCV

[PhantomCruiser]

Why does the SLS and Orion always break my game? Can you fix the issue?

You will need to be a lot more specific before anyone can help you. What version of Orbiter, external graphics/in-line graphics. Plus post your log file.

Then we can have an idea of what is broken.

 

[francisdrake]

Thanks for the feedback! Ok, that's really interesting. I assume your are using Orbiter 2016. As Gattispilot said, can you post a scenario?

I tried to jettison the Orion from the built-in SLS, and voila: It kept being attached to the upper stage. And the LES was slightly offset to one side. Pretty strange.

When I tried the experimental scenario with BrianJ's Flacon Heavy, it worked as it should, with a clear separation and flight.

So it seems not Multistage is the problem, but the Orion.
It could have to do with how the attachment points are managed, or how the vessel is created after separation. I will have a look into that, but it may take a while.

 

[gattispilot]

The scenario and log would be a first step in help

 

[Longjap]

BEGIN_DESC

END_DESC

BEGIN_ENVIRONMENT
  System Sol_SLS
  Date MJD 58382.5417593334
  Help CurrentState_img
END_ENVIRONMENT

BEGIN_FOCUS
  Ship SLS
END_FOCUS

BEGIN_CAMERA
  TARGET SLS
  MODE Extern
  POS 11.101930 -0.286479 -92.246205
  TRACKMODE Ground Earth
  GROUNDLOCATION -80.60401 28.60269 102.00
  GROUNDDIRECTION 90.01 -4.10
  FOV 50.00
END_CAMERA

BEGIN_MFD Left
END_MFD

BEGIN_MFD Right
END_MFD

BEGIN_SHIPS
SLS:Multistage2015
  STATUS Landed Earth
  POS -80.6040070 28.6083600
  HEADING 0.00
  ALT 56.860
  AROT 151.065 -8.240 4.530
  ATTACHED 0:0,MS_LaunchPad_SLS
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000 2:1.000000 3:1.000000 4:1.000000
  NAVFREQ 0 0 0 0
  XPDR 0
  CONFIG_FILE Config\Multistage2015\SLS_BLOCKIAORION_day.ini
  GUIDANCE_FILE Config\Multistage2015\Guidance\SLS_EM1_Orion_GNC.txt
  CONFIGURATION 0
  COMPLEX 
  CURRENT_BOOSTER 1
  CURRENT_STAGE 1
  CURRENT_INTERSTAGE 1
  CURRENT_PAYLOAD 1
  FAIRING 1
  MET -10.000
  BATTERY 5400.000000
  GROWING_PARTICLES 
  STAGE_IGNITION_TIME 0.000000
  STAGE_STATE 1
  TELEMETRY_FILE Config\Multistage2015\Telemetry\SLS_EM1_Orion_GNC.txt
  ALT_STEPS 200.0,350.0,1400.0,35000.0
  PEG_PITCH_LIMIT 35.000
  PEG_MC_INTERVAL 0.100
  CAMERA
END
SLSTOWER2:SLS\SLSTOWER2
  ARM_STATUS 0.7191 0.0000 0.0000 1.0000 0.0000 0.5705 0.0000 0.0000 0.0000 0.9815 0.0000 0.0000 0.0830 0.0000 0.0000 0.0000 0.0000 0.4759
  ARM2_STATUS 0.0034 0.0000 0.1682 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 
  POST 1 
  TOUCH -74.0430 
  STATUS Landed Earth
  POS -80.6040070 28.6084440
  HEADING 180.57
  ALT 73.857
  AROT -118.018 -3.869 171.717
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
WATERTOWER:SLS\WATERTOWER
  STATUS Landed Earth
  POS -80.6025360 28.6096140
  HEADING 0.00
  ALT 2.000
  AROT 61.715 4.484 8.267
  AFCMODE 7
  NAVFREQ 0 0
END
LIGHTNING1:SLS\LIGHTNINGTOWER
  STATUS Landed Earth
  POS -80.6029860 28.6086140
  HEADING 0.00
  ALT -0.194
  AROT 61.328 4.540 8.236
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
LIGHTNING2:SLS\LIGHTNINGTOWER
  STATUS Landed Earth
  POS -80.6050760 28.6098640
  HEADING 0.00
  ALT -0.194
  AROT 61.326 4.539 8.234
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
LIGHTNING3:SLS\LIGHTNINGTOWER
  STATUS Landed Earth
  POS -80.6052660 28.6076340
  HEADING 0.00
  ALT -0.194
  AROT 61.329 4.539 8.234
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
LP39:SLS\LP39PAD
  STATUS Landed Earth
  POS -80.6035360 28.6080240
  HEADING 0.00
  ALT 2.000
  AROT 61.716 4.484 8.266
  AFCMODE 7
  NAVFREQ 0 0
END
SPOTLIGHT1:spotlight2
  STATUS Landed Earth
  POS -29.1959147 2.4561787
  HEADING 66.68
  ALT 0.186
  AROT 25.070 -22.265 75.772
  ATTACHED 0:0,LP39
  AFCMODE 7
  NAVFREQ 0 0
  SPT 0 300.0000 1.0472
  PAT 2.0000 36.5000 95.2500 0.0000 1.0000 0.0000 0.0000 0.0000 1.0000
  GBL 0.47846 0.60696
END
SPOTLIGHT2:spotlight2
  STATUS Landed Earth
  POS -29.3783550 2.4074486
  HEADING 66.68
  ALT 0.186
  AROT 25.110 -22.449 75.730
  ATTACHED 0:1,LP39
  AFCMODE 7
  NAVFREQ 0 0
  SPT 0 300.0000 1.0472
  PAT 3.2000 37.5000 -6.1000 0.0000 1.0000 0.0000 0.0000 0.0000 1.0000
  GBL 0.70929 0.86793
END
SPOTLIGHT3:spotlight2
  STATUS Landed Earth
  POS -29.8439529 2.2257810
  HEADING 66.66
  ALT 0.186
  AROT 25.244 -22.932 75.661
  ATTACHED 0:2,LP39
  AFCMODE 7
  NAVFREQ 0 0
  SPT 0 300.0000 1.5708
  PAT -111.0000 38.0000 -7.0000 0.0000 1.0000 0.0000 0.0000 0.0000 1.0000
  GBL 0.61562 0.15286
END
SPOTLIGHT4:spotlight2
  STATUS Landed Earth
  POS -30.5357169 1.9577504
  HEADING 66.64
  ALT 0.186
  AROT 25.437 -23.652 75.557
  ATTACHED 0:3,LP39
  AFCMODE 7
  NAVFREQ 0 0
  SPT 0 300.0000 1.0472
  PAT -104.0000 38.5000 95.0000 0.0000 1.0000 0.0000 0.0000 0.0000 1.0000
  GBL 0.60889 0.37186
END
SPOTLIGHT5:spotlight2
  STATUS Landed Earth
  POS -35.1000667 0.9537060
  HEADING 66.58
  ALT 0.186
  AROT 26.650 -28.108 74.141
  ATTACHED 0:4,LP39
  AFCMODE 7
  NAVFREQ 0 0
  SPT 0 300.0000 0.3491
  PAT -101.5000 23.0000 29.7000 0.0000 1.0000 0.0000 0.0000 0.0000 1.0000
  GBL 0.82165 0.23533
END
SPOTLIGHT6:spotlight2
  STATUS Landed Earth
  POS -36.6896990 0.5215900
  HEADING 66.57
  ALT 0.186
  AROT 27.139 -29.681 73.670
  ATTACHED 0:5,LP39
  AFCMODE 7
  NAVFREQ 0 0
  SPT 0 300.0000 1.0472
  PAT 2.5000 23.0000 57.0000 0.0000 1.0000 0.0000 0.0000 0.0000 1.0000
  GBL 0.82956 0.68404
END
Orion:Orion-MPCV\Orion-MPCV
  STATUS Landed Earth
  POS -80.6040070 28.6083600
  HEADING 0.00
  ALT 104.960
  AROT 6.296 14.888 -171.528
  ATTACHED 1:0,SLS
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  XPDR 468
  MODE 10
  WATER 0
END
END_SHIPS

If using the config of SLS from my add-on remove the LES in the DMD. Basically I've made the MPCV "live" and added mode 10 to the scenario file to add the working LAS to the MPCV.

As you press "J" to activate it, the Orion will seperate from the service module correctly which will suffice in other cases but multistage2015 will instantly attach the Orion capsule to the SLS again so it remains stuck. Fred told me it's hard to adjust Multistage for this and it is probably more handy to adjust the code of the Orion. It might be because when activating the LAS it will only detach from the service module and not all vehicles or every attachment which is probably needed in this particular case.

 

[Loopos]

You will need to be a lot more specific before anyone can help you. What version of Orbiter, external graphics/in-line graphics. Plus post your log file.

Then we can have an idea of what is broken.

Thx but the Orbiter version is v.160828 (aka Orbiter 2016) and what i mean is when I open a scenario with the Orion MPCV (only) it works but when it is with the SLS it always says "orbiter.exe has stopped working" and when I check the Orbiter.log everything looks fine.

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 4.72614e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Devices enumerated: 6
000000.000: Devices accepted: 5
000000.000: [ ] RGB Emulation (SW)
000000.000: [ ] Direct3D HAL (HW)
000000.000: [x] Direct3D T&L HAL (HW)
000000.000: [ ] Direct3D HAL (Intel(R) HD Graphics) (HW)
000000.000: [x] Direct3D T&L HAL (Intel(R) HD Graphics) (HW)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000: Module OrbiterSound.dll ...... [Build 121120, API 100830]
000000.000: Module Multistage2015_MFD.dll [Build 161006, API 160828]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000:
000000.000: **** Creating simulation session
000000.000: DirectDraw interface OK
000000.000: Direct3D interface OK
000000.000: Graphics: Viewport: Window 1360 x 739 x 32
000000.000: Graphics: Hardware T&L capability: Yes
000000.000: Graphics: Z-buffer depth: 32 bit
000000.000: Graphics: Active lights supported: 8
============================ ERROR: ===========================
Inconsistent magnitude limits for background star brightness. Disabling background stars.
[Scene::LoadStars | .\Scene.cpp | 591]
===============================================================
000000.000: ---------------------------------------------------------------
000000.000: >>> ERROR: DDraw error DDERR_BLTFASTCANTCLIP
000000.000: >>> [OrbiterGraphics::clbkBlt | .\OGraphics.cpp | 1633]
000000.000: ---------------------------------------------------------------
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world

 

[francisdrake]

Hm, I am not sure if the DDERR brings Orbiter down, or if there are other effects to it.

My first suspect would be an incompatibility between addons. I see from the log for example Multistage enabled (although this should usually be no problem).
My suggestion would be to remove all other addons and modules, and then try it again.
If you use "Jonesoft Generic Mod Enabler" (JSGME) then simply deactivate the other addons. Also uncheck unused modules in the Launchpad Dialog - Modules.

If you don't yet use JSGME, please consider using it. Its free, and makes it very easy to use different addons without cluttering the orbiter installation with lots of module-specific files.
_______

I could trigger Orbiter crashing with the SLS-scenario, but don't know why.
On contrast the "Orion to the Moon" works fine with me. The only difference is the ISS not in this scenario.
Could be a memory leak. This will need some closer investigation later on.

 

[pclaurent]

francisdrake: any news on Orion-MPCV development? Can't wait for an autopilot for Orange-SLS and a EUS stage for designing missions to moon and beyond (ICPS is a bit too light)... An alternate launcher could be the Interstage-2015 SLS which has its own autopilot, if someone could make the config for attaching Orion as its payload (I tried to but still have issues with it).

 

[francisdrake]

Sorry, no news, no new features. I will make a last bug-fix release for Orbiter 2010 and then port everything to the new 2016 SDK. Still, this may take a while.
I agree, an Exploration Upper Stage is needed.

For an autopilot of the SLS: You could try the Launch MFD (2016 compatible).
Or have a look at the "Updated SLS for Orbiter 2016" which is very promising.

 

[francisdrake]

After a long time, just published on the front page the update (12) to make the Orion-MPCV fully compatible with Orbiter 2016. It is linked to the new libraries, so it will no longer work in 2010.

This is a compatibility update, so no new features. The new touchdown points allow dipping and bobbing up and down in the water after splashdown. The ocean is obviously not of the same depth everywhere, so the capsule can ride a litte higher or lower in the water.

Fixed an occasional crash with the Orange-SLS scenarios, the attachment point was not properly initialized.

 

[CurlSnout]

Many thanks. Great to be flying this program in Orbiter 2016.

Peace,

cs

 

[IronRain]

After a long time, just published on the front page the update (12) to make the Orion-MPCV fully compatible with Orbiter 2016. It is linked to the new libraries, so it will no longer work in 2010.

This is a compatibility update, so no new features. The new touchdown points allow dipping and bobbing up and down in the water after splashdown. The ocean is obviously not of the same depth everywhere, so the capsule can ride a litte higher or lower in the water.

Fixed an occasional crash with the Orange-SLS scenarios, the attachment point was not properly initialized.

Awesome, thanks!

 

[francisdrake]

Have fun trying it!

I would be glad if someone could give me a hint how to make simple touchdown points for the chutes. They are purely config-file vessels. After falling down they dance a little on the ground and are then catapulted into outer space.

Tried to the old 3-point definitons, none at all (relying on the size-sphere), and a syntax I found in the forum, but that did not make any difference:

  BEGIN_TD
  0   -1 -10 1e5 1e2 3
  23  23 73 1e5 1e2 3
  ... etc.
  END_TD

 

[gattispilot]

I can try. Is there a way to make a scenario where the chute are just deployed? For testing. So right before they hit the surface?

 

[francisdrake]

There is a scenario included for this testing:
Scenarios/Orion-MPCV/eXperimental/Orion splashdown.scn.
The status is just before drogue chute opening. Time compression can be speeded up 10x until touchdown.
This gives also a nice view on the capsule dancing in the water, made by softening the touchdown points' spring stiffness and reduing their damping factor.

 

[gattispilot]

Ok. I load the mpc-12 into 2016. And ran the splashdown. I see the chutes disappear.

-Chute:Orion-MPCV\Orion-MPCV-Chute
STATUS Orbiting Earth
RPOS -240123576.321 15024089.322 -237294266.188
RVEL -8375576.8351 524047.3401 -8276901.6313
AROT 47.306 -37.872 -29.935
VROT 794.6471 -176.5560 -74.7008
AFCMODE 7
NAVFREQ 0 0
END


Could you just make a new mesh of the chute floating on the surface. And if landed then show that mesh and delete the chutes?

 

[francisdrake]

I was considering flat chute meshes when on the ground, but then I'd need to control the chutes after separation. Right now they are dumb config-file defined vessels after seaparation. I'd either need to write a dll for all of them (drogues + chutes), or store their handles in the main vessel dll and include them in the prestep-loop.

I was hoping just for a simple a tochdown point definition that avoids them being shot into space after some time.

 

[barrygolden]

This is a super addon and could evolve into the shuttle fleet for 2016. gattis really set me up this weekend by taking his time to make the SLS work.

You should look to adding a HGA and docking lights to this. If you look at AMSO you can track the LM for the moon's surface to the docking point, really cool to watch

 

[gattispilot]

I didn't see where the touchdown point were defined in the chute.cfg?

; === Configuration file for vessel class  ===
; === to handle the chute after separation

ClassName = Orion-MPCV-Chute
MeshName =  Orion-MPCV\Orion-Chute

Mass = 200
Size = 20
CW = 3 3 0.1 0.1
RotResistance = 1 1 1

 

[francisdrake]

Barry, thanks for your kind words! Still I'd say the Suttle Fleet is really a class of its own, with an enormous amount of coding and modelling gone into it.

Docking lights may be an option, but I have not seen a high gain antenna yet on the ESA service module. Will keep looking for that.

John, on the touchdown points: As no method helped to avoid the space-catapult effect, I deleted them and rely on the size sphere alone. This is as good or bad as having defined points. Still, it may be worth to play around with td-points definitions in the cfg files.

---------- Post added at 09:20 PM ---------- Previous post was at 08:35 PM ----------

Speaking of touchdown points:
I played around with 4-point definitions in the cfg-files, and see: It works!
Or seems to. Could you please try it, by adding this line to the cfg files of chute and drogue:

TouchdownPoints = 0 1 0 40 20 50 -40 20 50 0 60 50

 

[gattispilot]

I have this:

; === Configuration file for vessel class  ===
; === to handle the chute after separation

ClassName = Orion-MPCV-Chute
MeshName =  Orion-MPCV\Orion-Chute

Mass = 200
Size = 20
CW = 3 3 0.1 0.1
RotResistance = 1 1 1

TouchdownPoints = 0 1 0 40 20 50 -40 20 50 0 60 50

it seems to work