OHM LC39A SpaceX

OrbitHangar

Addon Comments
Joined
Apr 9, 2008
Messages
3,832
Reaction score
18
Points
0

Author: brianj

A new mesh for Cape Canaveral LC39A launch pad, featuring modifications made by SpaceX to accomodate their Falcon9 and FalconHeavy launchers.

Installation requires editing your Config/Earth.cfg file.

Scenarios require "CONTEXT SpaceX" line in Environment section.

See Doc/LC39A SpaceX/lc39a_spacex_readme for full details.


Big Thanks to DaveS for the LC39A hardstand mesh, Kyle for reference images.



DOWNLOAD
 
Thank you Brian. :cheers:
 
Brian,

This is beyond fantastic!! Thank you so much.
 
FORMIDABLE

82249220170705174710.jpg


45870520170705174750.jpg


188378420170704221414.jpg
 
Keep Default Base

Hi Brian,

Isn't Orbiter the best community! Thank you for all you do.:tiphat:

I'm a newbie (relatively) and would like to launch the Falcon using your mesh, but also still launch the Shuttle from LC39A.

Could you hint at how I could manage the files/rename and tag them in scenarios so they don't override the default files/keep both sets? Is that possible?
 
Hi fatcat,
the simplest way to do it is to have two Orbiter installations - one for Shuttle launches from LC39A and one for SpaceX operations.

But if you don't have the space on your PC, you could create two new folders in your Config/Earth/Base/ folder, call them "Canaveral Shuttle" and "Canaveral SpaceX". Keep a copy of the default Canaveral.cfg in "Canaveral Shuttle" and a copy of my modified Canaveral.cfg in "Canaveral SpaceX".

When you want to do Shuttle launches, copy-and-paste the one from "Canaveral Shuttle" into the main Config/Earth/Base folder.

Likewise, for SpaceX launches, copy-and-paste the one from "Canaveral SpaceX" into the main Config/Earth/Base folder.

Can't think of a simpler way to do it.

Orbiter does have a facility for loading Surface Bases according to a CONTEXT line in the scenario file, but as far as I know that can only add bases, not remove default ones (so you would have the Shuttle and SpaceX pads on top of each other).

As a side note, I hadn't realised DaveS had not yet released his LC39A pad, so extra big thanks to him for his generosity in donating the concrete hard-stand from his add-on to help me out.

Cheers,
Brian
 
Selective loading of bases is one of the most overlooked features here. I'm aware that editing text is soooo last century but it works.

Have a look in .../Doc/OrbiterConfig.pdf p.14 for the correct syntax.
 
Selective loading of bases is one of the most overlooked features here. I'm aware that editing text is soooo last century but it works.

Have a look in .../Doc/OrbiterConfig.pdf p.14 for the correct syntax.
Yes, SSU uses it to load its bases instead of the default ones. The one we use is the CONTEXT parameter which only requires a minimum of two edits, one of Earth.cfg to add the CONTEXT parameter to load the desired folder and one to added the CONTEXT parameter to the desired scenario file(s). That's it, works wonders.
 
Ah! Thanks guys. I'll take another look at the CONTEXT method.
 
I didn't realise that duplicate bases are disregarded (depending on the surface base list order) when using the CONTEXT tag. Works fine. Updates for LC39A SpaceX, Falcon 9 and Dragon soon.
Thanks,
Brian
 
Hi Barry,
thanks, yes, should be interesting!
 
Update 170811 on OH:
Now requires "CONTEXT SpaceX" line in scenario Environment section to define SpaceX configuration launch pad.
Installation requires editing Config/Earth.cfg file.
See the readme.txt for full details.
 
Update 180930 on OH:
Removed last trace of RSS.
Moved FSS tower to accomodate new Crew Access Arm
 
Does your access arm roll back and forth to the rocket. Thank you so much for your work:thumbup:
 
Back
Top