Project CST-100 Starliner

[francisdrake]

The CST-100 Starliner over Floridas east coast

With the commercial crew program approaching its first launches I think Boeing's CST-100 Starliner shall be in Orbiter as well. This is an early version. Code and everything are a little rough and need improvement over time.

Reliable data on the CST-100 are difficult to find. This is what I estimated:
CM mass 4400 kg (including a crew of 5)
SM mass 5100 kg dry + 3100 kg fuel
Nose covers and aerodynamic skirt 400 kg (these are jettisoned during ascent)

The vessel can either be launched on an

• Atlas V using Multistage2015 by fred18, or
• Falcon9 for Orbiter 2016 by BrianJ

Keys:
A ... Abort engines manually, deliver 5-6 g for a few seconds
K ... Hatch open/close, animation needs improvement
J ... Abort when on Atlas V (press multiple times)
ctrl-Arrow up, down ... switch virtual cockpit eyepoint
ctrl-J ... Jettison service module
----
Update 06:
Switch virtual cockpit eyepoint with ctrl-arrow up, down.
Note: This version is somewhat unstable because of mesh bugs.

 

[Kyle]

Looks fantastic!

Re: launch vehicle, BrianJ also made an Atlas V but I'm not sure if it works for Orbiter 2016.

 

[Jeremyxxx]

It's nice to have the CST-100 Starliner around as an Orbiter addon, but there's a problem: There is no Crew access structure for LC-41 (Atlas V) and BrianJ's Atlas V needs to be included somehow in the future version of the CST-100 Starliner addon.

The Starliner can also be launched on a Delta IV.

 

[francisdrake]

Could you point me to an Atlas V addon working in Orbiter 2016?
I tried the Atlas V Beta files ver. 0.3 by Jim Clem, with the Multistage update for 2016.
Due to the payload attachment system the Starliner module is not active during launch. It would need an assembly mesh and will not jettison aerodynamic covers and skirts. I would prefer a modern system using an attachment point for the payload.

 

[Kyle]

Could you point me to an Atlas V addon working in Orbiter 2016?
I tried the Atlas V Beta files ver. 0.3 by Jim Clem, with the Multistage update for 2016.
Due to the payload attachment system the Starliner module is not active during launch. It would need an assembly mesh and will not jettison aerodynamic covers and skirts. I would prefer a modern system using an attachment point for the payload.

BrianJ made a MS2015 compatible Atlas V as a part of his InSight release:

https://www.orbithangar.com/searchid.php?ID=7175

This release by boogabooga also updates the Atlas V to MS2015 for Cygnus launches, which again works with 2016.

https://www.orbithangar.com/searchid.php?ID=6872

You'll need to add 2 SRBs though in the config files, like this using the SRBs found in the recent Solar Probe release:

[BOOSTER_1]
N=1
MeshName="SolarProbe2005/av501_srb1"
Height=20
Diameter=1.6
EmptyMass=5740
FuelMass=40957
Thrust=1688400 ; 1270000
angle=0
off=(-2.8, 0, -10.77)
rot_speed=(0,1.5,0)
speed=(-7.5,0,0)
BurnTime=84.00
ENG_TEX=Exhaust2
eng_1=(0,0,-8.4)
eng_diameter=0.75
ENG_PSTREAM1=SRBsmoke
ENG_PSTREAM2=SRBflame
CURVE_1=(0,80)
CURVE_2=(94,100)


[BOOSTER_2]
N=1
MeshName="SolarProbe/av501_srb2"
Height=20
Diameter=1.6
EmptyMass=5740
FuelMass=40957
Thrust=1688400
angle=200
off=(-2.8, 0, -10.77)
rot_speed=(0,1.5,0)
speed=(-7.5,0,0)
BurnTime=84.00
ENG_TEX=Exhaust2
eng_1=(0,0,-8.4)
eng_diameter=0.75
ENG_PSTREAM1=SRBsmoke
ENG_PSTREAM2=SRBflame
CURVE_1=(0,80)
CURVE_2=(94,100)

With regards to the 2 engine Centaur, I recall M_Molson making one a few years back. You could ask him if you could use the meshes. Also, with MS2015 you have the option to define any payload as a live, active vessel as opposed to a render. This will allow any config of the CST-100 to appear on top of a vehicle. Ex:

[PAYLOAD_1]
off=(0.0, 0.0, 29.5)
Meshname="CST-100\CST-100-cm"
Module=CST-100
Name=Starliner
Diameter=3.07
Mass=13000
Speed=(0,0,1)
LIVE=1

And the result:

 

[BrianJ]

Hi,
had to give this a go! Nice work :thumbup:
Launch to ISS on the Falcon9 works fine - nose cone and fairings auto jettison OK. Handles fine on orbit.

On station at ISS also OK - I docked pretty easy

I get a CTD with the Landing at Edwards scenario though, just after capsule breaks through the cloud layer. Here's my orbiter.log, fatal error at the end, but I also get the "missing mesh errors" for the other scenarios too.
Should I have your "Orion" capsule installed as well?

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 3.31087e-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 ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: Module InterMFD57.dll ........ [Build 161216, API 160910]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module transx.dll ............ [Build 160216, API 160214]
============================ ERROR: ===========================
Failed loading module Modules\Plugin\DX9ExtMFD.dll (code 126)
[Orbiter::LoadModule | .\Orbiter.cpp | 600]
===============================================================
000000.000: Module RendezvousMFD.dll ..... [Build ******, API 050206]
000000.000: 
000000.000: **** Creating simulation session
000000.000: DirectDraw interface OK
000000.000: Direct3D interface OK
000000.000: Graphics: Viewport: Window 1594 x 860 x 32
000000.000: Graphics: Hardware T&L capability: Yes
000000.000: Graphics: Z-buffer depth: 32 bit
000000.000: Graphics: Stencil buffer depth: 8 bit
000000.000: Graphics: Active lights supported: 8
000000.000: Loading 15382 records from star database
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
--------------------------- WARNING: --------------------------
>>> Texture not found: exhaust_crcs.dds
Skipping.
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 1040]
---------------------------------------------------------------
--------------------------- WARNING: --------------------------
>>> Texture not found: exhaust_crcs.dds
Skipping.
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 1040]
---------------------------------------------------------------
============================ ERROR: ===========================
Mesh not found: .\Meshes\Orion-MPCV\orion-cockpit.msh
[MeshManager::LoadMesh | .\Mesh.cpp | 1238]
===============================================================
============================ ERROR: ===========================
Mesh not found: .\Meshes\Orion-MPCV\orion-panel.msh
[MeshManager::LoadMesh | .\Mesh.cpp | 1238]
===============================================================
============================ ERROR: ===========================
Mesh not found: .\Meshes\Orion-MPCV\orion-astro.msh
[MeshManager::LoadMesh | .\Mesh.cpp | 1238]
===============================================================
============================ ERROR: ===========================
Mesh not found: .\Meshes\CST-100\CST-100-cover.msh
[MeshManager::LoadMesh | .\Mesh.cpp | 1238]
===============================================================
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: Finished initialising panels
000017.596: >>> ERROR: No vessel class configuration file found for:
============================ ERROR: ===========================
Orion-MPCV\Orion-MPCV-cover
[Vessel::OpenConfigFile | .\Vessel.cpp | 243]
===============================================================
000017.596: >>> TERMINATING <<<

P.S. very welcome to use any of my AtlasV meshes etc. Between SolarProbe2005 and InSight(or Maven) you should have all the parts needed.

Cheers,
BrianJ

 

[francisdrake]

Thanks Brian for the feedback.
Ahh, I overlooked this! Thats the chute compartment cover after separation. For now it will help to install the Orion as well. But I will clean that out and post an update soon.

---------- Post added at 11:13 ---------- Previous post was at 07:35 ----------

Updated. New zip-file 01 in the thread header to download.
Remark to self: Always remove other addons before final testing ... :dry:

 

[BrianJ]

Cool. Landing at Edwards scenario works fine with version 01. Thanks!
Drogue and chute deployment all good, chutes self delete ok. Looks great.


Still get one error message in orbiter.log, scenarios work fine though:

============================ ERROR: ===========================
Mesh not found: .\Meshes\CST-100\CST-100-cover.msh
[MeshManager::LoadMesh | .\Mesh.cpp | 1238]
===============================================================

Many thanks,
Brian

 

[spacman]

Will you be releasing an update with the Atlas v. Great job thank you very much for your work.

 

[francisdrake]

Thanks for the thorough testing!
The '-cover' is a leftover after renaming meshes. It is not displayed, I will delete the line.

Interestingly, the chutes are not self deleting, they are catapulted into space at phenomenal speed! This is also the reason why I switch to 1x time acceleration before deploying the main chute, as this soothes the effect.

I get a short stutter before the drogues and chutes are displayed. and this probably sums up all forces in the timeframes in between and kicks the freshly-generated vessels out. I did not experience this behaviour before. It is less of an issue, if you run the same scenario twice. Probably the mesh is then still in the cache memory and the loading time is shorter. I have to take a closer look into (pre-)loading meshes.

On the Atlas V:
I would love to have a working Atlas V in Orbiter 2016, as I am a big fan of this old workhorse! Especially the Centaur upper stage and its RL-10 engines are designs from the late 1950s, still working and performing at its best.

However, time is limited. The CST-100 here is the result of 3 rainy days during my vacation. For now I will rather improve it to become publish-able. I may start working on an Atlas V later this year, but not right away.

 

[gattispilot]

On the Atlas V:
I would love to have a working Atlas V in Orbiter 2016, as I am a big fan of this old workhorse! Especially the Centaur upper stage and its RL-10 engines are designs from the late 1950s, still working and performing at its best.

However, time is limited. The CST-100 here is the result of 3 rainy days during my vacation. For now I will rather improve it to become publish-able. I may start working on an Atlas V later this year, but not right away.

Isn't there a working Atlas V?
https://www.orbithangar.com/searchid.php?ID=6872
https://www.orbithangar.com/searchid.php?ID=7148

 

[BrianJ]

Interestingly, the chutes are not self deleting, they are catapulted into space at phenomenal speed!

Ah! The chutes detached from the capsule on landing, floated down and tipped over, started blowing along the ground, all in a quite realistic manner, then suddenly disappeared. The whole drogue/chute deployment was reasonably smooth for me, didn't notice any stutters.

 

[francisdrake]

Isn't there a working Atlas V?

You are correct, this is a working version of the Atlas V.
But with my limited (=non-existent) knowledge of the Spacecraft config files I could not get the Starliner active on top (only a dummy mesh file). The scenarios CTD without any indication of what might be wrong and finally I gave up.

Modified scenario file of Atlas 522:

BEGIN_SHIPS
AtlasV:Multistage2015
  STATUS Landed Earth
  POS -80.5828310 28.5834560
  HEADING 90.00
  FUEL 1.000
  CONFIG_FILE Config\Multistage2015\Config\500_Series\Dual_Engine_Centaur\Short_Fairing\av522-CST.ini
  GUIDANCE_FILE Config\Multistage2015\Guidance\AtlasV\av522.txt
  CONFIGURATION 0
  CURRENT_BOOSTER 1
  CURRENT_STAGE 1
  CURRENT_PAYLOAD 1
  FAIRING 1
END
END_SHIPS

and the modified part of the .ini file:

[PAYLOAD_1]
off=(0.0, 0.0, 29.5)
Meshname="CST-100\CST-100-cm"
Module=CST-100
Name=Starliner
Diameter=3.07
Mass=13000
Speed=(0,0,1)
LIVE=1

---------- Post added at 23:42 ---------- Previous post was at 21:38 ----------

CST-100 Starliner on an Atlas V 522

Ok folks, you got me! I could make it fly on Jim Clems Atlas V. It looks very much like Kyle's solution. Just had to understand that 'module' in Multistage points to the cfg-file ("CST-100\CST-100"), not to the dll in the Modules-folder.

Have to make a cradle-mesh for the vessel as a second payload,
and to understand how to modify the guidance file to fly to an ISS-inclined orbit. Will include it in the next update.

 

[Kyle]

Re: module location, yea, I had the exact same mix up working on the Delta IV Heavy MS2015 I released a few days ago.

You can modify the guidance to something like this to get to an ISS orbit:

-30.000 =orbit(230.00,230.00,[B]51.64[/B],-1.00,85.00,0.00)
-2.7=engine(0,100,2.7)
20=pitch(89,25,110)
170=Glimit(5)

The first two parameters in the orbit line are your apogee/perigee, and the third is your orbital inclination.

 

[fred18]

Hi francisdrake, I understand that you successfully put a live capsule on top of the rocket is that right?

if that is correct remember that with MS2015 MFD you can comand the rocket from within the cockpit of the capsule. If you need help, just let me know. Keep up the great work!

 

[francisdrake]

The CST on an Atlas V

You convinced me an Atlas V launcher can easily be done with Multistage.
Ok, here is the result. The config-files are from Jim Clem's original Atlas V, the meshes are from Brian's LRO mission (I like the frosty white look of the tank ). Named the launcher Atlas V N22 (N for No fairing).
The only slight drawback is the Centaur mesh shows only a single engine, but 2 flames. Maybe will give that an overhaul later.

The zip-file has been updated.

Fred: Yes, the CST capsule is live! You can see on the screenshot it just jettisoned its aerodynamic skirts. Thanks for your great work on Multistage2015!

 

[spacman]

Thank you for all you hard work in making it happen. If I may ask of you to release a sen. with the Atlas V . I would greatly appreciate it when you have the time.

 

[francisdrake]

Hi, glad you like it!
In the current version 03 an Atlas V scenario is already included (CST launch on AtlasV.scn). Just download the CST-100-02.zip on the frontpage of this thread.

 

[spacman]

Hi again I finally have the atlas v with cst but pad 39. What am I doing wrong. (on all launch sen.)

 

[francisdrake]

Ah, sorry, I did not modify the pad. I just placed the launcher at pad 39.
Actually I do not know how the access tower will look like, and it is not really in my focus.