Difference between revisions of "Creating a simple base"
(Added category.) |
(Editing content.) |
||
Line 1: | Line 1: | ||
+ | A '''base''' is used in Orbiter to describe a spaceport to be located on a planet, minor planet, or moon by creating a base configuration file, which is used to describe the name, location, and other need information to describe the base. | ||
+ | |||
+ | == Base config file == | ||
+ | The configuration file to describe a base is located in the directory Orbiter\Config\<planet>\Base, for example, when Orbiter launches, it will use Orbiter\Config\Earth\Base\Canaveral.cfg to build the Cape Canaveral spaceport, and will contain certain information to build that base. Information contained in a base configuration file include the name of the base, its location, size, whether the objects described by the file conform to the texture of the planet's surface, any navigation beacons, and a list of objects in the base such as runways, pads, buildings, etc. | ||
+ | |||
+ | So let's build a base and see what it looks like as we build it. For this, select a location for the base. For this, I selected a location on the Bonneville Salt Flats figuring it should be pretty flat to build stuff. Looking up the coordinates of the Flat in Wikipedia, sent a ship there and found what looks like water covering much of the area, so I moved the ship a bit until I found dry land that looked reasonably flat for my base. | ||
+ | |||
+ | So, let's open Notepad or your favorite text editor. On the first line type in BASE-V2.0. This identifies the file to Orbiter that it is a base. Save the file in the directory Orbiter\Config\Earth\Base\ with the filename Bonneville.cfg. Now, Orbiter will build the base. All base configuration files must contain that as the first line. | ||
+ | |||
+ | The next line, name the base, in this case Name = Bonneville. It does not need to be the same name as the filename, for example, in the Canaveral.cfg file, the Name = Cape Canaveral. This way you can use a simple filename for a base with a more complex name. | ||
+ | |||
+ | The next line contains the location, so type in Location = <longitude> <latitude>, in the case of Bonneville, Location = -80.65165 +28.58438. The + for positive coordinates is likely not required, but, it may be best to include it to make it less confusing to the reader. This will be the center of the base, and where the yellow square appears when flying nearby the base. | ||
+ | |||
+ | The next line is the size of the base. Size = 1000 for example. This defines the radius of the base in meters. It seems to be arbitrary as there are objects listed in some bases that came with the stock Orbiter 2016 with buildings and other objects that are located inside and outside of this radius. | ||
+ | |||
+ | The next line is OBJECTSIZE which defines the size, in meters, of a typical object on the base. This allows Orbiter to determine the distance that base objects will be rendered on the screen during runtime. Default is 100, objects whose rendered size is less than one pixel will not be rendered. | ||
+ | |||
+ | The next line contains MAPOBJECTSTOSHPERE = TRUE or FALSE. If this parameter is TRUE, the objects listed for this base will be mapped to the surface of the planet, if it is FALSE, objects will be place on a flat plane from the elevation of the center of the base. | ||
+ | |||
+ | The remainder of the file contains the NAV list, objects such as runways, pads, buildings, etc. and Surface tile list. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
==Creating a landing pad== | ==Creating a landing pad== | ||
− | [[Orbiter]] | + | [[Orbiter]] comes with a number of configuration files in the CONFIG directory. Those files describe the properties of objects. |
Each [[planet]] has a CFG file. For example, for planet [[Earth]] there is an Earth.cfg file. In each planet CFG file there is a list of bases, and each base has a CFG file too. | Each [[planet]] has a CFG file. For example, for planet [[Earth]] there is an Earth.cfg file. In each planet CFG file there is a list of bases, and each base has a CFG file too. |
Revision as of 13:20, 7 November 2023
A base is used in Orbiter to describe a spaceport to be located on a planet, minor planet, or moon by creating a base configuration file, which is used to describe the name, location, and other need information to describe the base.
Base config file
The configuration file to describe a base is located in the directory Orbiter\Config\<planet>\Base, for example, when Orbiter launches, it will use Orbiter\Config\Earth\Base\Canaveral.cfg to build the Cape Canaveral spaceport, and will contain certain information to build that base. Information contained in a base configuration file include the name of the base, its location, size, whether the objects described by the file conform to the texture of the planet's surface, any navigation beacons, and a list of objects in the base such as runways, pads, buildings, etc.
So let's build a base and see what it looks like as we build it. For this, select a location for the base. For this, I selected a location on the Bonneville Salt Flats figuring it should be pretty flat to build stuff. Looking up the coordinates of the Flat in Wikipedia, sent a ship there and found what looks like water covering much of the area, so I moved the ship a bit until I found dry land that looked reasonably flat for my base.
So, let's open Notepad or your favorite text editor. On the first line type in BASE-V2.0. This identifies the file to Orbiter that it is a base. Save the file in the directory Orbiter\Config\Earth\Base\ with the filename Bonneville.cfg. Now, Orbiter will build the base. All base configuration files must contain that as the first line.
The next line, name the base, in this case Name = Bonneville. It does not need to be the same name as the filename, for example, in the Canaveral.cfg file, the Name = Cape Canaveral. This way you can use a simple filename for a base with a more complex name.
The next line contains the location, so type in Location = <longitude> <latitude>, in the case of Bonneville, Location = -80.65165 +28.58438. The + for positive coordinates is likely not required, but, it may be best to include it to make it less confusing to the reader. This will be the center of the base, and where the yellow square appears when flying nearby the base.
The next line is the size of the base. Size = 1000 for example. This defines the radius of the base in meters. It seems to be arbitrary as there are objects listed in some bases that came with the stock Orbiter 2016 with buildings and other objects that are located inside and outside of this radius.
The next line is OBJECTSIZE which defines the size, in meters, of a typical object on the base. This allows Orbiter to determine the distance that base objects will be rendered on the screen during runtime. Default is 100, objects whose rendered size is less than one pixel will not be rendered.
The next line contains MAPOBJECTSTOSHPERE = TRUE or FALSE. If this parameter is TRUE, the objects listed for this base will be mapped to the surface of the planet, if it is FALSE, objects will be place on a flat plane from the elevation of the center of the base.
The remainder of the file contains the NAV list, objects such as runways, pads, buildings, etc. and Surface tile list.
Creating a landing pad
Orbiter comes with a number of configuration files in the CONFIG directory. Those files describe the properties of objects.
Each planet has a CFG file. For example, for planet Earth there is an Earth.cfg file. In each planet CFG file there is a list of bases, and each base has a CFG file too.
Finding a location for your base
The first step to create a base is to find out the coordinates of our base.
Let's open orbiter and load a scenario. Any scenario is good.
As the mission is loaded, make sure it is not paused. Now press CTRL-F1. Now you see the "orbiter: camera" window.
There is a "+" in the left of the word "Sun" in that window. Click it. Now click on "Earth" (we are going to place a new base on Earth.
Now push the "apply" button. Use your mouse wheel to zoom in/out. Press right click and move your mouse until the place where you want your base is right in the center of the screen. You may want to zoom in once you have located the location.
Now press the "Ground button" and then the "Current" button. As you see, 3 numbers wil appear in one field in that window. We need to copy and paste the first 2 numbers.
So select the first 2 numbers and copy them to the clipboard. Now we have the latitude and longitude of the base.
Adding a base to the planet
Now close the Orbiter camera window. Now press CTRL-Q to exit Orbiter.
Open Notepad. Open the Orbiter directory, and then open the Config directory. Drag the Earth.cfg file to the Notepad window.
Scroll down until you find
; === Surface Bases === BEGIN_SURFACE
As you see, there is a list of bases right after that. Each base has a CFG file.
Let's guess we want to create a base called "Rincon de la Vieja" and let's guess your coordinates are -84.989845 +10.739155, and the base properties will be placed in a file called Rincon.cfg.
Between BEGIN_SURFACE and END_SURFACE add a line that reads:
Rincon: -84.989845 +10.739155
Notice that instead of those numbers I used, you should paste the numbers that you just had in your clipboard.
Save and exit Notepad. Now you have added your base to the planet.
Creating the landing pad
Now open Notepad. Copy the following text and paste in Notepad.
; === Surface Base === Name = Rincon de la vieja Size = 2000 ObjectSize = 2000 BEGIN_OBJECTLIST LPAD2 POS 0 0 SCALE 5 0.15 0 TEX Lpad02 NAV 128.05 END END_OBJECTLIST
Now save this as Rincon.cfg
in the CONFIG directory, and then exit Notepad.
Congratulations!! You have created a base with a landing pad.
Viewing your base
You now can open orbiter and load a scenario. If you press CTRL-F1 and you click on the "+" that is next to "Spaceports".
Scroll down until you find your base. Click on the name of your base and press the "Apply" button.
Press the "Track" button and then press the "Movable target relative" button.
You should see your base now.