Programming Question Removing bases

[Stripe]

Well the search function didn't seem to find what I was after... so here's your chance to make me look foolish :lol:

I would like to have a 'more realistic' install (ie, more like current times) where I don't have Brighton Beach or Olympus base appearing (either on the Moon/Mars) or appearing on the various Com/Nav screens for V/STOL landings.

I figured I could just 'remove' the base cfg file from the relevant folder but this causes Orbiter to crash to desktop.

I find it hard to believe that Brighton Beach and Olympus have been 'hard coded' into the orbiter executable, so these files are being 'parsed' from somewhere else. I however, couldn't seem to track it down, any pointers ?

Thanks

 

[Scarecrow]

I can't remember how, since I don't have easy access to Orbiter right now, but this is definately possible. Brighton Beach and Olympus are no different from any other base. I suggest getting a base addon from orbit hangar (Niven should probably work, and is quite nice anyway, should you go for a more futuristic setup later: [ame="http://www.orbithangar.com/searchid.php?ID=3646"]Lunar Base Niven v2.0[/ame]) and reading the installation instructions, pawing through the files that come with it, and basically doing the reverse of installing Niven on Brighton Beach and Olympus.

 

[martins]

Bases are referenced in the corresponding planet's config file, within the BEGIN_SURFBASE/END_SURFBASE block.

Also have a look in Orbiter.pdf regarding selective base loading (pg. 106)

 

[fort]

Stripe,

A model for Brighton.cfg :

BASE-V2.0
Name = Brighton Beach
Location = -33.4375 +41.125
Size = 500

BEGIN_NAVBEACON
VOR LBB -33.4375 +41.125 116.30 500
END_NAVBEACON

Delete the OBJECTLIST in the .cfg starting from : ; === List of visuals ===

 

[NukeET]

Also have a look in Orbiter.pdf regarding selective base loading (pg. 106)

@Stripe: For a good example of selective base loading, download the "Unofficial" LazyD Tribute, [ame="http://www.orbithangar.com/searchid.php?ID=3232"]“Unofficial” LazyD Tribute[/ame]

I suggest getting a base addon from orbit hangar (Niven should probably work, and is quite nice anyway, should you go for a more futuristic setup later: http://www.orbithangar.com/searchid.php?ID=3646) and reading the installation instructions, pawing through the files that come with it, and basically doing the reverse of installing Niven on Brighton Beach and Olympus.

@Scarecrow: Thanks for the reference and kind words.

 

[C3PO]

I figured I could just 'remove' the base cfg file from the relevant folder but this causes Orbiter to crash to desktop.

If the bases are V2 you can just delete the cfg file. The old type has to be removed in <planet>.cfg too.
Be sure that the scenario file doesn't refer to the deleted base.

[FONT=Lucida Console]BEGIN_MFD Right[/FONT]
[FONT=Lucida Console]  TYPE Map[/FONT]
[FONT=Lucida Console]  REF Moon[/FONT]
[FONT=Lucida Console]  BTARGET [B]Brighton Beach[/B][/FONT]
[FONT=Lucida Console]END_MFD

[/FONT]
or:

[FONT=Lucida Console]PB-01:ShuttlePB[/FONT]
[FONT=Lucida Console]  STATUS Landed Moon[/FONT]
[FONT=Lucida Console]  BASE [B]Brighton Beach[/B]:2[/FONT]
[FONT=Lucida Console]  HEADING 220.00[/FONT]
[FONT=Lucida Console]  FUEL 1.000[/FONT]
[FONT=Lucida Console]  NAVFREQ 484 124[/FONT]
[FONT=Lucida Console]END[/FONT]

 

[Stripe]

Hi,

Thanks everyone for your input, it's been a great help - the selective base loading will be useful!

I think C3PO read my mind, as after posting this, I wondered if the scenario made reference to the base and if that might be causing an issue.

Turns out (I think anyway) that if you're set up on a runway take off you're ok to remove the base (you are just positioned on the ground where the runway used to be), however if the scenario has you on a VTOL pad, Orbiter will crash to desktop (because a reference to a non existent base has been made).