Vessel Default LC39 Launch Pad...

[Zach121k]

I Am Making A Custom Base And Have Hit A Bit Of A Snag... Is There An Addon Out There That Is The Default LC39 Launchpad That Is Compatible With UCGO/Scenario Editor?

 

[Trainguy]

No

The pad is a custom mesh and part of the base itself - it is never, and to my knowledge, has never, been rendered as a ship. This means it is not UCGO/scenario editor compatible.

To add/move it, you must find:

MESH ; Pad 39B tower
FILE KSC_3
POS -11830 0 5280
ROT 178
TEX Cape18
SHADOW
PRELOAD
END
MESH ; Pad 39B base
FILE KSC_4
POS -11830 0 5280
ROT 178
TEX Cape19
SHADOW
PRELOAD
END

in the KSC scenario file. These are the two parts of the pad. The POS numbers are the position, and (I think!) this can be duplicated as many times as necessary.

If you want the pad to be scenario editor compatible, it would have tro be rendered as a ship, and if you want UCGO capabilities, the aformentioned ship will need a custom DLL.

I hope this helps!

P.S.: what exactly are you trying to do?

:hail:

EDIT: the pad has never been released as it either has just been duplicated, then moved, or a custom pad has been developed instead.

 

[Zach121k]

No

The pad is a custom mesh and part of the base itself - it is never, and to my knowledge, has never, been rendered as a ship. This means it is not UCGO/scenario editor compatible.

To add/move it, you must find:

MESH ; Pad 39B tower
FILE KSC_3
POS -11830 0 5280
ROT 178
TEX Cape18
SHADOW
PRELOAD
END
MESH ; Pad 39B base
FILE KSC_4
POS -11830 0 5280
ROT 178
TEX Cape19
SHADOW
PRELOAD
END

in the KSC scenario file. These are the two parts of the pad. The POS numbers are the position, and (I think!) this can be duplicated as many times as necessary.

If you want the pad to be scenario editor compatible, it would have tro be rendered as a ship, and if you want UCGO capabilities, the aformentioned ship will need a custom DLL.

I hope this helps!

P.S.: what exactly are you trying to do?

:hail:

EDIT: the pad has never been released as it either has just been duplicated, then moved, or a custom pad has been developed instead.

Sorry For The Late Reply... Just As A Ship... No UCGO

 

[Trainguy]

Please answer my question: what do you want it to do?

It is possible that a workaround exists, as it as a ship has not been modeled yet.

:hail:

 

[Zach121k]

being able to have ksc pads anywhere i need them. or more than there already is.

 

[Trainguy]

being able to have ksc pads anywhere i need them. or more than there already is.

Am I right in thinking that what you want is simple flexibility, and so the ability to move pads easily?

By the way, the code on my first post is the position of the pad. A quick fix is to simply place a delta glider or another spacecraft of your choice where you want the pad, then copy the pad information either from canaveral.cfg or from my post, but replace the postion lines with that from the spacecraft, to your base.cfg. You will need a base.cfg for this to work. You can set one up by finding the location of your base that you want (by DG if necessary) then name it. An example of the necessary code is:

BASE-V2.0
Name = Cape Canaveral
Location = -80.675 +28.5208
Size = 1000
MapObjectsToSphere = TRUE

In order to place the pad a

BEGIN_OBJECTLIST
place code here
END_OBJECTLIST

A sample base with just the parameters and the pad (at 0 degrees latitude and longitude of just the pad as an example):

BASE-V2.0
Name = sample base
Location = +0 +0
Size = 1000
MapObjectsToSphere = TRUE
 
BEGIN_NAVBEACON
VOR KSCX 0 0 100.00 500
END_NAVBEACON
 
 
BEGIN_OBJECTLIST
MESH ; Pad 39B tower
 FILE KSC_3
 POS 0 0 0
 ROT 0
 TEX Cape18
 SHADOW
 PRELOAD
END
MESH ; Pad 39B base
 FILE KSC_4
 POS 0 0 0
 ROT 0
 TEX Cape19
 SHADOW
 PRELOAD
END
END_OBJECTLIST

Does any of this make sense? The nav beacon just allows the base to be found from a distance

If anyone else finds a mistake in my code, please let me know

I hope this helps. It seems to be the only way round your problem. By the way, this post, including the code, only took me three minutes to make, even through the code was edited from canaveral.cfg

:hail: