Editing Building structures
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | + | A '''Block''' is an object that can be used to create structures on bases. It is a cube or rectangle consisting of three dimensions, length, width, and height, and it can use any of the textures that are listed in the base.cfg file (Orbiter\Config\base.cfg), although some may not be appropriate for a block. | |
− | |||
− | |||
− | A ''' | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
If you have not read the article [[Creating a simple base]] for information on how to build a base, I suggest you do so. Orbiter's description for how to build objects is located in Orbiter\Doc\OrbiterConfig.pdf. | If you have not read the article [[Creating a simple base]] for information on how to build a base, I suggest you do so. Orbiter's description for how to build objects is located in Orbiter\Doc\OrbiterConfig.pdf. | ||
Line 18: | Line 7: | ||
== Textures == | == Textures == | ||
− | Textures used for building | + | Textures used for building a block are found in the directory Orbiter\Textures and are listed in the file Orbiter\Config\Base.cfg. Note that there are a number of textures in the \Textures directory that are not listed in the Base.cfg file that could be used, so, if you like type in the filename without the extension into the Base.cfg file so you can use them in building structures, such as Door01, but, not, let's say, Runway01. |
Open the Bonneville.cfg file (Orbiter\Config\Earth\Base\) that we created in the article [[Creating a simple base]] in your favorite text editor such as Notepad or Notepad+. Place your cursor at the end of the line BEGIN_OBJECTLIST and press {{Key|Enter}}. That provides a line to type in an object. | Open the Bonneville.cfg file (Orbiter\Config\Earth\Base\) that we created in the article [[Creating a simple base]] in your favorite text editor such as Notepad or Notepad+. Place your cursor at the end of the line BEGIN_OBJECTLIST and press {{Key|Enter}}. That provides a line to type in an object. | ||
Line 33: | Line 22: | ||
</code> | </code> | ||
− | Save the file, you can keep the file open as we will be editing this | + | Save the file, you can keep the file open as we will be editing this block. Exit the scenario, then re-launch it. Now, you will see a small cube sitting on the ground about 50 meters in front of you. In the scenario editor, change the time to about 16:00 hours, that puts the Sun behind you so you can see what effect shadows have. |
− | Now note | + | Now note the block is white on the side facing you. If you moved your ship so you could see one of the sides, you will note that it is gray. Orbiter applies shading for shadows. |
− | The | + | The block should look something like this: |
[[Image:Block_0_01.png|200px|thumb|center|Image of a BLOCK with no texture.]] | [[Image:Block_0_01.png|200px|thumb|center|Image of a BLOCK with no texture.]] | ||
− | This | + | This block is a cube 1 meter cubed. Now, let's edit the block in Bonneville.cfg as follows: |
<code> | <code> | ||
Line 53: | Line 42: | ||
</code> | </code> | ||
− | Again, save the scenario, exit to the Launchpad and re-launch. Now, your | + | Again, save the scenario, exit to the Launchpad and re-launch. Now, your block should look like something like this. |
[[Image:Block_Fcd01_01.png|200px|thumb|center|Image of the same block with Fcd01 on the front and back, Fcd03 on the sides, Roof01 on the top, 1 meter per side.]] | [[Image:Block_Fcd01_01.png|200px|thumb|center|Image of the same block with Fcd01 on the front and back, Fcd03 on the sides, Roof01 on the top, 1 meter per side.]] | ||
Fcd01 produces a wall with four windows wide and four windows tall all into that one meter square side, and Fcd03 produces a wall with three sets of windows wide and three tall. The number of items produced on a face vary from one to another Fcd. | Fcd01 produces a wall with four windows wide and four windows tall all into that one meter square side, and Fcd03 produces a wall with three sets of windows wide and three tall. The number of items produced on a face vary from one to another Fcd. | ||
− | == Components of a | + | == Components of a block == |
− | When building a | + | When building a block, the first line must be '''BLOCK'''. |
− | The next line describes the position of the | + | The next line describes the position of the block in relation to the center of the base. If you type '''POS 0 0 0''', the center of the block will sit right on the center of the base. |
For the position parameter, '''POS''' must be the first part of the line. | For the position parameter, '''POS''' must be the first part of the line. | ||
Line 67: | Line 56: | ||
The first number '''X''' is the distance north or south of center of the base (north is -, south us +) in meters. | The first number '''X''' is the distance north or south of center of the base (north is -, south us +) in meters. | ||
− | The second number '''Y''' is the elevation above the terrain or base plane the bottom of the | + | The second number '''Y''' is the elevation above the terrain or base plane the bottom of the block sits, above is +, below is -. This can be useful if you need to put one block on top of another to build a complex structure. |
The third number '''Z''' is the position in meters east +, or west - of the center of the base. | The third number '''Z''' is the position in meters east +, or west - of the center of the base. | ||
− | The next line starts with '''SCALE'''. This indicates the size of the | + | The next line starts with '''SCALE'''. This indicates the size of the block in the X, Y, and Z axis. So, if you type in SCALE 1 2 3, that makes the block 1 meter wide, 2 meters tall, and 3 meters front to back. Orbiter will stretch the texture to fill the dimensions called out. |
The next line is '''ROT'''. At ROT 0, the front of the building is facing East, positive ROT is clockwise in degrees, range is 0-360. | The next line is '''ROT'''. At ROT 0, the front of the building is facing East, positive ROT is clockwise in degrees, range is 0-360. | ||
− | The next line is '''TEX1'''followed by three parameters, the first 0 or which texture is called out from Base.cfg, the first number is how many iterations of the texture is squeezed into the width, and the third number is how many iterations is squeezed into the height. This applies to the front face and the back face of the | + | The next line is '''TEX1'''followed by three parameters, the first 0 or which texture is called out from Base.cfg, the first number is how many iterations of the texture is squeezed into the width, and the third number is how many iterations is squeezed into the height. This applies to the front face and the back face of the block. |
− | The next line is '''TEX2''' followed by three parameters, the same as TEX1, but applies to the left and right faces of the | + | The next line is '''TEX2''' followed by three parameters, the same as TEX1, but applies to the left and right faces of the block. |
− | The next line is '''TEX3''' followed by three parameters, the same as TEX1 and TEX2, but applies to the top, or roof of the | + | The next line is '''TEX3''' followed by three parameters, the same as TEX1 and TEX2, but applies to the top, or roof of the block. |
The first term of each '''TEX''' callout is the name of a texture from Base.cfg. Any one can be used in each, but, using Runway1 or Lpad02 would probably not be appropriate. | The first term of each '''TEX''' callout is the name of a texture from Base.cfg. Any one can be used in each, but, using Runway1 or Lpad02 would probably not be appropriate. | ||
− | Now, let's build two | + | Now, let's build two blocks each with different parameters and compare. |
− | Replace the existing | + | Replace the existing block with the following: |
<code> | <code> | ||
Line 106: | Line 95: | ||
</code> | </code> | ||
− | After launching Orbiter, you will see two | + | After launching Orbiter, you will see two blocks, the same size, both use Fcd01 for all sides, but the windows are different. |
− | For the left | + | For the left block, SCALE 1 2 3 creates a block 1 meter wide, 2 meters tall, 3 meters deep. TEX1 Fcd01 1 1 creates one Fcd01 wide, 1 Fcd01 tall stretching the Fcd to fit the height. The same with TEX2 and TEX3, TEX3 calling out a Roof design. |
For the right block, SCALE 1 2 3 does the same, but TEX1 Fcd01 1 2 creates one Fcd01 wide and two Fcd01 tall making twice as many windows. TEX2 2 1 creates four windows high and eight windows wide on the side faces. TEX3 2 2 creates a roof with twice as many seams. | For the right block, SCALE 1 2 3 does the same, but TEX1 Fcd01 1 2 creates one Fcd01 wide and two Fcd01 tall making twice as many windows. TEX2 2 1 creates four windows high and eight windows wide on the side faces. TEX3 2 2 creates a roof with twice as many seams. | ||
Line 115: | Line 104: | ||
Also, note that many of the textures, particularly Fcd ones will have a texture for daytime and another for nighttime, showing some lights through the windows. You can see this by changing your time of day in the scenario to nightime, let's say 04:00. | Also, note that many of the textures, particularly Fcd ones will have a texture for daytime and another for nighttime, showing some lights through the windows. You can see this by changing your time of day in the scenario to nightime, let's say 04:00. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Gallery == | == Gallery == |