Question Stevcast's A Different Brighton

Mauler85

Traveler out of time
Joined
Aug 29, 2010
Messages
60
Reaction score
0
Points
0
I need some help adding the Mass driver on that he says what to replace but I cant find where to put it It says to put it in the moon configuration file after BEGIN_SURFACEBASE But there is no BEGIN_SURFACEBASE in the Moon/Base/Brighton.cfg file so do i add it? If thats the case can someone post exactly what i need to add that so i can cut and paste?
 
Just as Mauler85 said, add it in Moon.cfg, which should be in your Config folder. If there's no BEGIN_SURFBASE or END_SURFBASE, add it between 'Visualization Parameters' and 'Fixed surface observation points' like this:
Code:
; === Surface Bases ===
; place additional bases or
; base directories in this list
BEGIN_SURFBASE
DIR Moon\Base                          ;surface base directory you can add more 
XYZ:     longitude   	latitude       ;the big spaces are tabs
END_SURFBASE

(XYZ is what you're supposed to add)

Hope this helped!

P.S.: Just remembered, ; is used before text in a config file to stop Orbiter from understanding it, so you can add comments.
 
It also says to add this somewhere

MassDriver:Massdriver
STATUS Landed Moon
POS -33.348500 41.107993
HEADING 359.000
 
It also says to add this somewhere

MassDriver:Massdriver
STATUS Landed Moon
POS -33.348500 41.107993
HEADING 359.000
That's a scenario entry. You have to add it to whatever scenario you're using with this base, between BEGIN_SHIPS and END_SHIPS. It should also read:
Code:
MassDriver:Massdriver
   STATUS Landed Moon
   POS -33.348500  41.107993
   HEADING 359.000
END
 
I need some help adding the Mass driver on that he says what to replace but I cant find where to put it It says to put it in the moon configuration file after BEGIN_SURFACEBASE But there is no BEGIN_SURFACEBASE in the Moon/Base/Brighton.cfg file so do i add it?

The Moon.cfg should not need to be edited for this. This add-on replaces the Brightonbeach.cfg, and there are no textures to add for the Mass Driver or LunaCity, or this config. You will need to edit Config/Base.cfg when installing the Brighton Base Enhancement package, instructions are in it's "readme"

Part of the Mass Driver add-on, the Mass Driver itself, is not a Base element, but a vessel. For this to be present, it must be in the scenario file. There are good examples of the format in earlier posts.
 
All of the addons mentioned above need to be installed in Orbiter. I came about this configuration pretty much
by accident. I was trying to install Kulch's Mass Driver3, but for some reason it wouldn't show up in the
scenario. So I placed another Luna City on the pad for the Mass Driver, and moved the positon of the Mass Driver
in the respective scenario.

If you do install Kulch's Mass Driver, change the position of the Driver from:

MassDriver:Massdriver MassDriver:Massdriver
STATUS Landed Moon to STATUS Landed Moon
BASE Brighton Beach:7 POS -33.348500 41.107993
HEADING 0.00 HEADING 359.000


Paste Brighton in your configuration file, and add: Brighton: -33.3945 41.0914
to your moon configuration file, under the BEGIN_SURFBASE heading (For some reason, my computer wouldn't read the Brighton
file from the Moon/Base folder;Your computer may be more agreeable than mine-at least I hope so!!).



Am I reading it wrong then????
 
I'm guessing that Stevecast isn't fully aware of how bases are defined in Orbiter. MassDriver is built for Orbiter 2005, and bases are handled differently starting with Orbiter 2006.

Prior to 2006, for a base to be recognized by the core, it needed to be listed (along with it's location) in the surfbase section of the planet (or moon's) config. Editing your Moon.cfg was required to add a new base. None of these add-ons actually add a new base, they replace an existing one. No new entry on the surfbase list would be required. It's important to note that the bases location is defined in Moon.cfg, not Brighton.cfg.

Further, starting with Orbiter 2006 bases no longer need be defined in the planet or moon's config. The bases location is now defined in the base config. Installing MassDriver overwrites the stock Brighton.cfg with one designed for Orbiter 2005. It does not contain the base location. It won't "show up" because Orbiter doesn't know where to put it. Specifying the location in the surfbase section of the moon.cfg may solve this - if you wanted to install the MassDriver in it's original form.

The only file you should need to edit is Base.cfg to add the textures as instructed by the Brighton Base Enhancement. Also, the last thing you will do is place the Brighton.cfg supplied by Stevecast into the Orbiter/Config/Moon/Base folder, overwriting the one that's there already. Unless you've altered your Moon.cfg and changed the base directory paths, this should take care of everything except the MassDriver itself, which is a vessel and must be included in the scenario file.
 
Last edited:
Back
Top