2009-11-24T04:24:01Z

Languard: /* Render Lightmaps */ done

'''In Depth Exterior Level Technical Overview'''

Rough Draft of tutorial that explores in depth the various parts of creating/editing exterior levels. Possibly will break into seperate pages describing the various parts in even more painful detail ;)

== Introduction ==
While good information exists on creating exterior levels, much of it is fragmented. The goal of this article is to provide a very through technical overview of the [[Level_editor|Level Editor]] in exterior mode. Every single button and command that is related to the process of creating an exterior level will be covered. What this article is not is a how-to for creating a level. This is strictly for covering the commands and options. If all you want is a quick-and-dirty guide for making levels, this is not it. For those still reading, let's get to mastering this tool.

== Assumptions ==
I do hold some basic assumptions of knowledge, and wish to get those out in open now. I assume that:

* You know how to [[Creating_a_module|Create a Module]]
* Set the active Module
* Have the correct python version (which is 2.5.4) and have the correct win32 extensions installed. Installation instructions can be found [[http://social.bioware.com/wiki/datoolset/index.php/Installing_the_toolset#Lightmapper|here]]
* Understand the difference between [[User:Languard#Dragon Age Modding Terms|Level, Area, and Map]]

== Creating a Level ==
To create a level, you go to File->New->Level. By default terrain will be selected, so click on Next, and we're at our first important screen. We have two versions to pick from:
{| border="1"
| Basic
|-
| [[File:newLevelBasic.png]]
|-
| Advance
|-
| [[File:newLevelAdvance.png]]
|}
The main difference between the two, other than more options, is that changing a field in the Basic version won't affect the numbers in the other fields. In the Advance version, this can happen depending on what you changed. To change back and forth between the two, click on the Basic/Advanced button. BUG: You must click on the Basic button twice to go back into basic mode.

=== What do the Basic options mean ===
* Desired Width - How wide do you want this area to be in meters?
* Desired Height - How long do you want this area to be in meters?
* Base Mesh Resolution - I believe this measures the base of the mesh triangle. In meters.
* Chunk Size - How large or small do you want your terrain chunks? Chunks are explained later in the article. In Meters.
* Default Water Plane - Do you want a default water plane? I would recommend against this, as it creates the water plane up in the sky, and doesn't even match the terrain size you create. Just as easy to manually add it in when you're ready for water.

=== What do the Advanced options mean ===
Notice that in advanced mode, Chunk Size and Area Size aren't directly editable. Instead you alter the other values, and that determines how big the chunks are and how large the area is.
* Mesh Cells Per Chunk - How many cells or triangles will a chunk contain?
* Base Mesh Resolution - Size of the triangle in meters. Resolution * Cells Per Chunk = Chunk Size
* Blend Texel Resolution - In cm, and I'm not sure what this does yet. Increasing this value reduces file size, so I think this controls how detailed the textures appear. Lower = more detail.
* Number of chunks X - How many chunks long is your area? Chunk Size * This = Area Length
* Number of chunks Y - How many chunks wide is your area? Chunk Size * This = Area Width
* Blend Mask Size - Unsure, controlled by Blend Texel Resolution. Can be changed later.
* Tessellation Level - How many levels of tessellation can be done to the terrain mesh. Max Resolution shows the smallest possible triangle.

== Saving the .lvl file ==
As soon as the level is created, I would recommend saving it out. Levels are not part of the database and must be saved to the file system. I would be a good idea to place them into an easy to find directory. Even better would be to use a cloud storage service like [http://www.getdropbox.com Drop Box] to ensure you always have an archive of your file. Your level files will also appear in the Recent Files option under File.

== Camera Controls ==
A detailed description of controls can be fond here: [[3D controls]]. Keep in mind that the [[Level editor]] only supports the 3dsMax camera and WASD camera.

== The Basic Steps All Levels Need ==
All exterior levels will need to have the following basic steps performed on them if they are to be used. I would recommend going through all of these steps as soon you've done the first save, and then save the level again after you're done.

* Add Export Area
* Add Start Point
* Add Ambient Light
* Render Lightmaps
* Post All Local

=== Export Area ===
{|
|-
|[[File:AreaProperties.png|alt Area Properties|left]]
|Detailed documentation can be found [[Level_editor#Creating_an_Exportable_Area_.28Terrain.29|here]]. What you are doing here is defining the playable area of your level. As stated in the [[Level_editor#Creating_an_Exportable_Area_.28Terrain.29|level editor]] it is possible to create multiple export areas. At this time I haven't experimented with this, and can't write anything on it. For now this will be focused on a single Export Area. To add in an Export Area, you need to click on the purple plus sign [[File:addExport.png]]. This will open a window with a lot of options. There are only two things that you must do, and one thing that you should do.
|}

First, you must set the Layout Name. This can only be seven characters, and the editor will cut-off the name if you enter in more than seven characters so that it is seven characters. This name is what will appear in the Area Layout list when you go to create an area. To this end, I recommend that you come up with a good naming convention. Now if you don't plan on releasing your level as a stand-alone resource for other modders, all you have to worry about is making sure the name doesn't conflict with Bioware's areas. If you are going to release it for others to use, I recommend using the first three letters as a unique code that indicates this belongs to you, the next two letters to indicate the level type (dungeon, plains, mountain, so on) and the last two for variations. For example I might call a level rcfMn1D. rcf = my intiails, Mn = mountain, 1D = 1st variant, day version.

Second, you must click on the Define Area button and set the walkable area of the level. I recommend you zoom out so you can see the whole level before trying to define the area. You will see three colored boxes like this:

[[File:defineArea.png|250px]]

The checkerboard pattern is there because I turned on the display of chunk boundaries [[File:chunkBoundaries.png]] This matters because you can only define the playable area along the chunk boundaries. Use the left mouse button to click and drag the green box around the area you want the play to be able to walk in. The yellow area will be at full detail but unplayable, and the red area is in low detail and considered the vista area.

The one thing you should do is change the Name property. Please do not get the Name and Layout Name properties confused. Layout Name controls what is seen in the Area Layout list, the Name property is just what to call this Export Area in the [[Level editor|level editor]]. You don't have to change it, but I make it a habit to change it to Main.

More detailed information can be found (well no place yet need to write it)

Define mini-map lets you define the area the editor will take for the mini-map snapshot. Exporting the minimap must be done via right-click.

=== Start Point ===
Only thing this is used for is path finding. A start point must be added after the Export Area has been defined. Click on the flag icon [[File:startPointIcon.png]] and then click on your map where you want it. The location doesn't matter as long as it is walkable. What will happen is during path finding, the editor will flood out from this point looking for walkable areas.

=== Ambient Lighting ===
As of build 1.0.982.0, sunlight is broken. That or we are completely misunderstanding what sunlight means in the editor. So for now you must add an ambient baked light. The [[Lighting]] page gives a detailed description of the various kinds of light. To briefly summarize, a baked light only lights the terrain, a static light is expensive and lights both the player and terrain, and I believe animated lights are terrain only, but have animated shadows that get baked into the lightmap. An ambient light is basically a light value that is applied everywhere, and is normally used to ensure shadows aren't pitch black.

There are two ways to add in lights: One is to right-click on the terrain, and the other is to right-click on the Terrain World menu. Select Insert->New Light, and a Point:Baked light will be added in. Leave all the options alone for this light with the exception of Name. I recommend changing the name to ambient so you can find it easily.

=== Render Lightmaps ===
At this time, the difference between Render Lightmaps (cached scene) and Render Lightmaps is not understood. It is recommended that you use Render Lightmaps. Click on the icon [[File:renderLightmap.png]] to start the rendering process. This can potentially take a long time. It is recommended that you turn on the Task Manager so you can see CPU usage. As long as there is high CPU usage, the script should be working. After the render is done you will need to toggle off View Models Fully Lit [[File:viewModelsLit.png]] and toggle on Display Lightmaps [[File:displayLightmaps.png]]. It can be helpful to leave lightmaps off and fully lit on while you are working on terrain and object placement since it makes things easier to see.

=== Post All Local ===
Not sure what exactly this does. I believe it generates and places the .ARL file into a path in My Documents. This path is read by the toolset when selecting area layouts. Doing a Post to Local does not grab trees.

== Terrain Mesh Editing ==
What this covers

=== Icons ===
* Deform
* Plateau
* Smooth
* Tessellate

=== Deform Tool ===
What it does and how options affect it

=== Plateau Tool ===
What it does and how options affect it

=== Smooth Tool ===
What it does and how options affect it

=== Tessellate Tool ===
What it does and how options affect it

== Texture Editing ==
General idea behind textures. You can only have 8. No more than three textures blended together.

=== Adding a Texture to the Pallete ===
Explain how to add a texture to the pallete. Explain the differences between diffuse, normal, and specular

=== Texture Paint Tool ===
What it does and how options affect it

=== Texture Smooth Tool ===
What it does and how options affect it

=== Relax Map Tool ===
What it does and how options affect it

== Water ==
Skip for now

== Model and Vegetation Movement Tools ==

=== Snap ===

=== Move ===

=== Rotate ===

=== Select ===

== Vegetation ==

== Models ==

== Pathfinding ==
Flood-fill algorithm. Rays are cast down, so if you have overhangs only the top is walkable. Terrain can get really steep before the auto-no-walk kicks in, so use the Terrain Collision tools

=== Show Terrain Collision ===
This simply toggles on and of the display of the terrain collisions.

=== Build Terrain Collision ==
Toggles show collisions on, and puts you into build mode for terrain collisions. Clicking the left mouse button anchors the first point of a 'wall'. A second click will anchor the second point, and you now can see a blue wall. The flood-fill pathfinding will not cross this wall. Continue left clicking to place an unbroken wall around the terrain you wish to block off. Right clicking will end the wall chain. If you are not currently building a wall, right clicking will delete a wall segment.

Exterior Level Manual

2009-11-23T04:26:34Z

Languard: Some minor clean up

'''In Depth Exterior Level Technical Overview'''

Rough Draft of tutorial that explores in depth the various parts of creating/editing exterior levels. Possibly will break into seperate pages describing the various parts in even more painful detail ;)

== Introduction ==
While good information exists on creating exterior levels, much of it is fragmented. The goal of this article is to provide a very through technical overview of the [[Level_editor|Level Editor]] in exterior mode. Every single button and command that is related to the process of creating an exterior level will be covered. What this article is not is a how-to for creating a level. This is strictly for covering the commands and options. If all you want is a quick-and-dirty guide for making levels, this is not it. For those still reading, let's get to mastering this tool.

== Assumptions ==
I do hold some basic assumptions of knowledge, and wish to get those out in open now. I assume that:

* You know how to [[Creating_a_module|Create a Module]]
* Set the active Module
* Have the correct python version (which is 2.5.4) and have the correct win32 extensions installed. Installation instructions can be found [[http://social.bioware.com/wiki/datoolset/index.php/Installing_the_toolset#Lightmapper|here]]
* Understand the difference between [[User:Languard#Dragon Age Modding Terms|Level, Area, and Map]]

== Creating a Level ==
To create a level, you go to File->New->Level. By default terrain will be selected, so click on Next, and we're at our first important screen. We have two versions to pick from:
{| border="1"
| Basic
|-
| [[File:newLevelBasic.png]]
|-
| Advance
|-
| [[File:newLevelAdvance.png]]
|}
The main difference between the two, other than more options, is that changing a field in the Basic version won't affect the numbers in the other fields. In the Advance version, this can happen depending on what you changed. To change back and forth between the two, click on the Basic/Advanced button. BUG: You must click on the Basic button twice to go back into basic mode.

=== What do the Basic options mean ===
* Desired Width - How wide do you want this area to be in meters?
* Desired Height - How long do you want this area to be in meters?
* Base Mesh Resolution - I believe this measures the base of the mesh triangle. In meters.
* Chunk Size - How large or small do you want your terrain chunks? Chunks are explained later in the article. In Meters.
* Default Water Plane - Do you want a default water plane? I would recommend against this, as it creates the water plane up in the sky, and doesn't even match the terrain size you create. Just as easy to manually add it in when you're ready for water.

=== What do the Advanced options mean ===
Notice that in advanced mode, Chunk Size and Area Size aren't directly editable. Instead you alter the other values, and that determines how big the chunks are and how large the area is.
* Mesh Cells Per Chunk - How many cells or triangles will a chunk contain?
* Base Mesh Resolution - Size of the triangle in meters. Resolution * Cells Per Chunk = Chunk Size
* Blend Texel Resolution - In cm, and I'm not sure what this does yet. Increasing this value reduces file size, so I think this controls how detailed the textures appear. Lower = more detail.
* Number of chunks X - How many chunks long is your area? Chunk Size * This = Area Length
* Number of chunks Y - How many chunks wide is your area? Chunk Size * This = Area Width
* Blend Mask Size - Unsure, controlled by Blend Texel Resolution. Can be changed later.
* Tessellation Level - How many levels of tessellation can be done to the terrain mesh. Max Resolution shows the smallest possible triangle.

== Saving the .lvl file ==
As soon as the level is created, I would recommend saving it out. Levels are not part of the database and must be saved to the file system. I would be a good idea to place them into an easy to find directory. Even better would be to use a cloud storage service like [http://www.getdropbox.com Drop Box] to ensure you always have an archive of your file. Your level files will also appear in the Recent Files option under File.

== Camera Controls ==
A detailed description of controls can be fond here: [[3D controls]]. Keep in mind that the [[Level editor]] only supports the 3dsMax camera and WASD camera.

== The Basic Steps All Levels Need ==
All exterior levels will need to have the following basic steps performed on them if they are to be used. I would recommend going through all of these steps as soon you've done the first save, and then save the level again after you're done.

* Add Export Area
* Add Start Point
* Add Ambient Light
* Render Lightmaps
* Post All Local

=== Export Area ===
{|
|-
|[[File:AreaProperties.png|alt Area Properties|left]]
|Detailed documentation can be found [[Level_editor#Creating_an_Exportable_Area_.28Terrain.29|here]]. What you are doing here is defining the playable area of your level. As stated in the [[Level_editor#Creating_an_Exportable_Area_.28Terrain.29|level editor]] it is possible to create multiple export areas. At this time I haven't experimented with this, and can't write anything on it. For now this will be focused on a single Export Area. To add in an Export Area, you need to click on the purple plus sign [[File:addExport.png]]. This will open a window with a lot of options. There are only two things that you must do, and one thing that you should do.
|}

First, you must set the Layout Name. This can only be seven characters, and the editor will cut-off the name if you enter in more than seven characters so that it is seven characters. This name is what will appear in the Area Layout list when you go to create an area. To this end, I recommend that you come up with a good naming convention. Now if you don't plan on releasing your level as a stand-alone resource for other modders, all you have to worry about is making sure the name doesn't conflict with Bioware's areas. If you are going to release it for others to use, I recommend using the first three letters as a unique code that indicates this belongs to you, the next two letters to indicate the level type (dungeon, plains, mountain, so on) and the last two for variations. For example I might call a level rcfMn1D. rcf = my intiails, Mn = mountain, 1D = 1st variant, day version.

Second, you must click on the Define Area button and set the walkable area of the level. I recommend you zoom out so you can see the whole level before trying to define the area. You will see three colored boxes like this:

[[File:defineArea.png|250px]]

The checkerboard pattern is there because I turned on the display of chunk boundaries [[File:chunkBoundaries.png]] This matters because you can only define the playable area along the chunk boundaries. Use the left mouse button to click and drag the green box around the area you want the play to be able to walk in. The yellow area will be at full detail but unplayable, and the red area is in low detail and considered the vista area.

The one thing you should do is change the Name property. Please do not get the Name and Layout Name properties confused. Layout Name controls what is seen in the Area Layout list, the Name property is just what to call this Export Area in the [[Level editor|level editor]]. You don't have to change it, but I make it a habit to change it to Main.

More detailed information can be found (well no place yet need to write it)

Define mini-map lets you define the area the editor will take for the mini-map snapshot. Exporting the minimap must be done via right-click.

=== Start Point ===
Only thing this is used for is path finding. A start point must be added after the Export Area has been defined. Click on the flag icon [[File:startPointIcon.png]] and then click on your map where you want it. The location doesn't matter as long as it is walkable. What will happen is during path finding, the editor will flood out from this point looking for walkable areas.

=== Ambient Lighting ===
As of build 1.0.982.0, sunlight is broken. That or we are completely misunderstanding what sunlight means in the editor. So for now you must add an ambient baked light. The [[Lighting]] page gives a detailed description of the various kinds of light. To briefly summarize, a baked light only lights the terrain, a static light is expensive and lights both the player and terrain, and I believe animated lights are terrain only, but have animated shadows that get baked into the lightmap. An ambient light is basically a light value that is applied everywhere, and is normally used to ensure shadows aren't pitch black.

There are two ways to add in lights: One is to right-click on the terrain, and the other is to right-click on the Terrain World menu. Select Insert->New Light, and a Point:Baked light will be added in. Leave all the options alone for this light with the exception of Name. I recommend changing the name to ambient so you can find it easily.

=== Render Lightmaps ===
Basic trouble shooting, describe what to toggle on/off to see true lighting. Mention that it is probably a good idea to work with fully lit on and lightmaps off while building. Personal preference though.

=== Post All Local ===
Not sure what exactly this does. I believe it generates and places the .ARL file into a path in My Documents. This path is read by the toolset when selecting area layouts. Doing a Post to Local does not grab trees.

== Terrain Mesh Editing ==
What this covers

=== Icons ===
* Deform
* Plateau
* Smooth
* Tessellate

=== Deform Tool ===
What it does and how options affect it

=== Plateau Tool ===
What it does and how options affect it

=== Smooth Tool ===
What it does and how options affect it

=== Tessellate Tool ===
What it does and how options affect it

== Texture Editing ==
General idea behind textures. You can only have 8. No more than three textures blended together.

=== Adding a Texture to the Pallete ===
Explain how to add a texture to the pallete. Explain the differences between diffuse, normal, and specular

=== Texture Paint Tool ===
What it does and how options affect it

=== Texture Smooth Tool ===
What it does and how options affect it

=== Relax Map Tool ===
What it does and how options affect it

== Water ==
Skip for now

== Model and Vegetation Movement Tools ==

=== Snap ===

=== Move ===

=== Rotate ===

=== Select ===

== Vegetation ==

== Models ==

== Pathfinding ==
Flood-fill algorithm. Rays are cast down, so if you have overhangs only the top is walkable. Terrain can get really steep before the auto-no-walk kicks in, so use the Terrain Collision tools

=== Show Terrain Collision ===
This simply toggles on and of the display of the terrain collisions.

=== Build Terrain Collision ==
Toggles show collisions on, and puts you into build mode for terrain collisions. Clicking the left mouse button anchors the first point of a 'wall'. A second click will anchor the second point, and you now can see a blue wall. The flood-fill pathfinding will not cross this wall. Continue left clicking to place an unbroken wall around the terrain you wish to block off. Right clicking will end the wall chain. If you are not currently building a wall, right clicking will delete a wall segment.

Installing the toolset

2009-11-22T21:03:05Z

Languard: /* Lightmapper */ Reworked the section to make it a little clearer on what to install

The Dragon Age Toolset installer comes with several pieces of third-party software that are needed for the toolset to function. They are:

* DirectX 9.0c
* Visual C Runtime Library
* Microsoft SQL Server Express 2005 Edition
* Nvidia PhysX drivers

These components will be installed along with the toolset by the toolset's installer.

== Location ==

The first screen you'll get to after starting the installer and passing the title page is the install location selector. The toolset can only install the program into a specific subdirectory of the Dragon Age game directory, so you won't be able to alter the installation path; it's for informational purposes.

'''Note:''' MSSQL Express 2005 is bundled with this toolset and is required for it to function. Unfortunately, MSSQL Express 2005's installer has a limitation that prevents it from installing to a directory path that's longer than 58 characters.<sup>[http://support.microsoft.com/kb/935371]</sup>

Follow the instructions on [[installation into a directory with a long path name]] for a workaround on this issue.

== Components ==

The next screen after location has been selected is where you can choose which components to install. There are only two selectable components here; Core Resources (the toolset itself) and Microsoft SQL Server Express. To run the toolkit you'll obviously need to install the Core Resources option. SQL Server is presented as a separate option so that if you already have a database server installed on your system you can use that instead of installing a whole new one.

If you don't have an SQL server installed, or if you don't know whether you have one installed, it's safe to go with the default and install SQL Server Express. SQLServer's installer will check the existing components and, finding that all required components are already in place, won't do anything after you click "finish."

== Manual database selection ==

If you choose not to install SQL Server Express, the installer will ask for a database server and database name to install the toolset's resource database to instead. The default server is <code>.\BWDATOOLSET</code> and the default database name is <code>bw_dragonage_content</code>.

== Installation ==

Once you have selected these options the Dragon Age toolset will begin the installation process. This can take a while. When the install process is finished you'll be given the option to read a readme.txt file.

The toolset will create a start menu folder named "Dragon Age". The start menu folder will include a link to start the toolset, a link to the toolset's uninstaller, and a link to the toolset's external configuration utility.

The installer will write a log file in your My Documents folder. If installation fails this log file will be helpful for debugging purposes.

If you are installing over a previous version of the toolset, you may need to update the format of your old database to make it compatible with the new version of the toolset. See [[database migration]] for details.

=== Lightmapper ===

The [[lightmap|lightmapper]] is the tool used to calculate lighting in level layouts. You only need to use it if you're going to be creating or modifying level layouts. The lightmapper included with the toolset requires Python to run but Python isn't currently bundled with the toolset, so if you don't already have it installed you'll need to do the following:

# Install [http://www.python.org/ftp/python/2.5.4/python-2.5.4.msi Python 2.5.4 ]
# Install the [http://sourceforge.net/projects/pywin32/ win32 extensions] for Python 2.5 <BR> '''OR'''
# Install [http://downloads.activestate.com/ActivePython/windows/2.5/ActivePython-2.5.4.4-win32-x86.msi ActiveState Python 2.5.4.4]

The easiest way to do this is to download and install ActiveState python which comes with the needed extensions. Just click through the defaults on the installer and you will be ready to go. If you want to use python.org installer, maker sure to install it first, then install the win32 extensions.

* If you don't have Python installed and try to run the lightmapper, you'll receive a standard Windows error message indicating that "EclipseRay.exe has stopped working.

* Note for 64 bit machines: There appears to be a bug with the 64-bit version of ActiveState Python 2.5 for Windows that prevents the lightmapper from functioning. Install the 32-bit version instead, it works. The 32-bit version is the one linked above.

* Do not install both ActivePython and Python.org. This will most likely cause you to get an Error Code 1 when rendering lightmaps.

* If you get an error code of -1073741819 this means you either have the 64 bit version or you have a version higher than 2.5. Uninstall and use the installers from the links above.

== Configuration ==

The external configuration utility is used to configure the toolset's database connection. You shouldn't need to run the configuration utility during routine usage of the toolset, and if the defaults set up by your installer work you may not need to run it at all.

The default database string is "<code>Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\SQLEXPRESS</code>". For advanced configuration, click on the ellipsis button ([[Image:ellipsis.png]]) to open the data link properties window.

Note that the configuration utility will first ask where the game build is. The game executable is not currently available for distribution but it is not necessary for the toolset to run so there's no need to be concerned about this.

== Uninstallation ==

An uninstaller shortcut is available from the same start menu folder as the toolset itself. It will autodetect the location you installed the toolset in, display it to you to confirm that this is correct, and then after you click "next" it will ask which components to uninstall.

* Core Resources - uninstalled by default, this is the toolset itself.
* Database - Since the uninstaller can't automatically determine if you're using SQLServer Express purposes other than just the Dragon Age toolset, SQLServer is ''not'' uninstalled automatically by default. To have the uninstaller remove the database server as well, unselect this checkbox.

The uninstaller is generated on installation and therefore isn't signed. This may cause Vista to complain under some circumstances but shouldn't affect the uninstaller's functioning.

== Troubleshooting ==

See [[installation troubleshooting]] for a list of common problems that can occur during installation and how to correct or work around them.

Note that there is currently an issue with installing the toolset for games that have been installed via Steam. See [[Installation with Steam]] for specific instructions on how to resolve this issue. If you have installed your game in a directory with a path name longer than 58 characters you may also encounter this same issue.

If you experience a crash logs can be found in <code>My Documents\BioWare\Dragon Age\Toolset\logs</code>. The log filenames will include the date on which the log file was created. Sending in a log will help greatly with bug fixing.

== Documentation ==

Documentation is currently provided via the wiki at:

http://social.bioware.com/wiki/datoolset/

[[Category:Toolset installation]]

Exterior Level Manual

2009-11-22T05:13:17Z

Languard: created Pathfinding section

'''In Depth Exterior Level Technical Overview'''

Rough Draft of tutorial that explores in depth the various parts of creating/editing exterior levels. Possibly will break into seperate pages describing the various parts in even more painful detail ;)

== Introduction ==
While good information exists on creating exterior levels, much of it is fragmented. The goal of this article is to provide a very through technical overview of the [[Level_editor|Level Editor]] in exterior mode. Every single button and command that is related to the process of creating an exterior level will be covered. What this article is not is a how-to for creating a level. This is strictly for covering the commands and options. If all you want is a quick-and-dirty guide for making levels, this is not it. For those still reading, let's get to mastering this tool.

== Assumptions ==
I do hold some basic assumptions of knowledge, and wish to get those out in open now. I assume that:

* You know how to [[Creating_a_module|Create a Module]]
* Set the active Module
* Have the correct python version (which is 2.5.4) and have the correct win32 extensions installed
* Understand the difference between [[User:Languard#Dragon Age Modding Terms|Level, Area, and Map]]

== Creating a Level ==
To create a level, you go to File->New->Level. By default terrain will be selected, so click on Next, and we're at our first important screen. We have two versions to pick from:
{| border="1"
| Basic
|-
| [[File:newLevelBasic.png]]
|-
| Advance
|-
| [[File:newLevelAdvance.png]]
|}
The main difference between the two, other than more options, is that changing a field in the Basic version won't affect the numbers in the other fields. In the Advance version, this can happen depending on what you changed. To change back and forth between the two, click on the Basic/Advanced button. BUG: You must click on the Basic button twice to go back into basic mode.

=== What do the Basic options mean ===
* Desired Width - How wide do you want this area to be in meters?
* Desired Height - How long do you want this area to be in meters?
* Base Mesh Resolution - I believe this measures the base of the mesh triangle. In meters.
* Chunk Size - How large or small do you want your terrain chunks? Chunks are explained later in the article. In Meters.
* Default Water Plane - Do you want a default water plane? I would recommend against this, as it creates the water plane up in the sky, and doesn't even match the terrain size you create. Just as easy to manually add it in when you're ready for water.

=== What do the Advanced options mean ===
Notice that in advanced mode, Chunk Size and Area Size aren't directly editable. Instead you alter the other values, and that determines how big the chunks are and how large the area is.
* Mesh Cells Per Chunk - How many cells or triangles will a chunk contain?
* Base Mesh Resolution - Size of the triangle in meters. Resolution * Cells Per Chunk = Chunk Size
* Blend Texel Resolution - In cm, and I'm not sure what this does yet.
* Number of chunks X - How many chunks long is your area? Chunk Size * This = Area Length
* Number of chunks Y - How many chunks wide is your area? Chunk Size * This = Area Width
* Blend Mask Size - Unsure, controlled by Blend Texel Resolution. Can be changed later.
* Tessellation Level - How many levels of tessellation can be done to the terrain mesh. Max Resolution shows the smallest possible triangle.

== Saving the .lvl file ==
As soon as the level is created, I would recommend saving it out. Levels are not part of the database and must be saved to the file system. I would be a good idea to place them into an easy to find directory. Even better would be to use a cloud storage service like [http://www.getdropbox.com Drop Box] to ensure you always have an archive of your file. Your level files will also appear in the Recent Files option under File.

== Camera Controls ==
A detailed description of controls can be fond here: [[3D controls]]. Keep in mind that the [[Level editor]] only supports the 3dsMax camera and WASD camera.

== The Basic Steps All Levels Need ==
All exterior levels will need to have the following basic steps performed on them if they are to be used. I would recommend going through all of these steps as soon you'v done the first save, and then save the level again after you're done.

* Add Export Area
* Add Start Point
* Add Ambient Light
* Render Lightmaps
* Post All Local

=== Export Area ===
{|
|-
|[[File:AreaProperties.png|alt Area Properties|left]]
|Detailed documentation can be found [[Level_editor#Creating_an_Exportable_Area_.28Terrain.29|here]]. What you are doing here is defining the playable area of your level. As stated in the [[Level_editor#Creating_an_Exportable_Area_.28Terrain.29|level editor]] it is possible to create multiple export areas. At this time I haven't experimented with this, and can't write anything on it. For now this will be focused on a single Export Area. To add in an Export Area, you need to click on the purple plus sign [[File:addExport.png]]. This will open a window with a lot of options. There are only two things that you must do, and one thing that you should do.
|}

First, you must set the Layout Name. This can only be seven characters, and the editor will cut-off the name if you enter in more than seven characters so that it is seven characters. This name is what will appear in the Area Layout list when you go to create an area. To this end, I recommend that you come up with a good naming convention. Now if you don't plan on releasing your level as a stand-alone resource for other modders, all you have to worry about is making sure the name doesn't conflict with Bioware's areas. If you are going to release it for others to use, I recommend using the first three letters as a unique code that indicates this belongs to you, the next two letters to indicate the level type (dungeon, plains, mountain, so on) and the last two for variations. For example I might call a level rcfMn1D. rcf = my intiails, Mn = mountain, 1D = 1st variant, day version.

Second, you must click on the Define Area button and set the walkable area of the level. I recommend you zoom out so you can see the whole level before trying to define the area. You will see three colored boxes like this:

[[File:defineArea.png|150px]]

The checkerboard pattern is there because I turned on the display of chunk boundaries [[File:chunkBoundaries.png]] This matters because you can only define the playable area along the chunk boundaries. Use the left mouse button to click and drag the green box around the area you want the play to be able to walk in. The yellow area will be at full detail but unplayable, and the red area is in low detail and considered the vista area.

The one thing you should do is change the Name property. Please do not get the Name and Layout Name properties confused. Layout Name controls what is seen in the Area Layout list, the Name property is just what to call this Export Area in the [[Level editor|level editor]]. You don't have to change it, but I make it a habit to change it to Main.

More detailed information can be found (well no place yet need to write it)

Not sure on mini-map. Anyone get this working yet?

=== Start Point ===
Only thing this is used for is path finding. A start point must be added after the Export Area has been defined. Click on the flag icon [[File:startPointIcon.png]] and then click on your map where you want it. The location doesn't matter as long as it is walkable. What will happen is during path finding, the editor will flood out from this point looking for walkable areas.

=== Ambient Lighting ===
As of build 1.0.982.0, sunlight is broken. That or we are completely misunderstanding what sunlight means in the editor. So for now you must add an ambient baked light. The [[Lighting]] page gives a detailed description of the various kinds of light. To briefly summarize, a baked light only lights the terrain, a static light is expensive and lights both the player and terrain, and I believe animated lights are terrain only, but have animated shadows that get baked into the lightmap. An ambient light is basically a light value that is applied everywhere, and is normally used to ensure shadows aren't pitch black.

There are two ways to add in lights: One is to right-click on the terrain, and the other is to right-click on the Terrain World menu. Select Insert->New Light, and a Point:Baked light will be added in. Leave all the options alone for this light with the exception of Name. I recommend changing the name to ambient so you can find it easily.

=== Render Lightmaps ===
Basic trouble shooting, describe what to toggle on/off to see true lighting. Mention that it is probably a good idea to work with fully lit on and lightmaps off while building. Personal preference though.

=== Post All Local ===
Not sure what exactly this does. I believe it generates and places the .ARL file into a path in My Documents. This path is read by the toolset when selecting area layouts.

== Terrain Mesh Editing ==
What this covers

=== Icons ===
* Deform
* Plateau
* Smooth
* Tessellate

=== Deform Tool ===
What it does and how options affect it

=== Plateau Tool ===
What it does and how options affect it

=== Smooth Tool ===
What it does and how options affect it

=== Tessellate Tool ===
What it does and how options affect it

== Texture Editing ==
General idea behind textures. You can only have 8. No more than three textures blended together.

=== Adding a Texture to the Pallete ===
Explain how to add a texture to the pallete. Explain the differences between diffuse, normal, and specular

=== Texture Paint Tool ===
What it does and how options affect it

=== Texture Smooth Tool ===
What it does and how options affect it

=== Relax Map Tool ===
What it does and how options affect it

== Water ==
Skip for now

== Model and Vegetation Movement Tools ==

=== Snap ===

=== Move ===

=== Rotate ===

=== Select ===

== Vegetation ==

== Models ==

== Pathfinding ==
Flood-fill algorithm. Rays are cast down, so if you have overhangs only the top is walkable. Terrain can get really steep before the auto-no-walk kicks in, so use the Terrain Collision tools

=== Show Terrain Collision ===
This simply toggles on and of the display of the terrain collisions.

=== Build Terrain Collision ==
Toggles show collisions on, and puts you into build mode for terrain collisions. Clicking the left mouse button anchors the first point of a 'wall'. A second click will anchor the second point, and you now can see a blue wall. The flood-fill pathfinding will not cross this wall. Continue left clicking to place an unbroken wall around the terrain you wish to block off. Right clicking will end the wall chain. If you are not currently building a wall, right clicking will delete a wall segment.

Exterior Level Manual

2009-11-22T04:58:01Z

Languard: /* Ambient Lighting */ done

Exterior Level Manual

2009-11-20T20:51:23Z

Languard: /* Start Point */ done

Help talk:Contents

2009-11-20T14:53:54Z

Languard:

Talk:How-tos

2009-11-20T14:33:01Z

Exterior Level Manual

2009-11-18T20:27:14Z

Languard: intial outline

'''In Depth Exterior Level Technical Tutorial'''

Rough Draft of tutorial that explores in depth the various parts of creating/editing exterior levels. Possibly will break into seperate pages describing the various parts in even more painful detail ;)

== Introduction ==
Overview of the tutorial. This will cover in detail on creating an exterior level and cover every tool. It will not cover level design theory, or how to make a good looking module. Just the tools available and what they do and how to use them.

== Assumptions ==
What do I assume you can do? What are pages that describe the assumed knowledge?

* Create a Module
* Set the active Module
* Have the correct python version
* Understand the difference between Level, Area, and Map

== Creating a Level ==
What do the options mean and what do they do

=== What do the Basic options mean ===
Chunk size is fixed, mainly sets the number of chunks

=== What do the Advanced options mean ===
Fine control over starting mesh detail and texture quality

== Saving the .lvl file ==
Talk about save locations and stress that the level only exists on the hard drive.

== Camera Controls ==
A page to exaustive control list
Cover 3dsMax controls and WASD controls, plus zooming

== The Basic Steps All Levels Need ==
* Add Export Area
* Add Start Point
* Add Ambient Light
* Render Lightmaps
* Post All Local

== The Basic Steps Explained ==
So, take take all of the basic steps in detail:

=== Export Area ===
Detailed documentation can be found [[Level_editor#Creating_an_Exportable_Area_.28Terrain.29|here]]. Need to explore setting multiple export areas, this is unknown at this time. The important parts are the Layout Name, Name, and Define Area. Skydome can be changed which is how you get the Fade.

Not sure on mini-map. Anyone get this working yet?

=== Start Point ===
Only thing this is used for is pathfinding. Add it after the area(s), and only one per area is needed. No other use for this that I know of.

=== Ambient Lighting ===
Sunlight is broken, so you must add an ambient light. Steps for doing so.

=== Render Lightmaps ===
Basic trouble shooting, describe what to toggle on/off to see true lighting. Mention that it is probably a good idea to work with fully lit on and lightmaps off while building. Personal preference though.

=== Post All Local ===
Not sure what exactly this does. I believe it generates and places the .ARL file into a path in My Documents. This path is read by the toolset when selecting area layouts.

== Terrain Mesh Editing ==
What this covers

=== Icons ===
* Deform
* Plateau
* Smooth
* Tessellate

=== Deform Tool ===
What it does and how options affect it

=== Plateau Tool ===
What it does and how options affect it

=== Smooth Tool ===
What it does and how options affect it

=== Tessellate Tool ===
What it does and how options affect it

== Texture Editing ==
General idea behind textures. You can only have 8. No more than three textures blended together.

=== Adding a Texture to the Pallete ===
Explain how to add a texture to the pallete. Explain the differences between diffuse, normal, and specular

=== Texture Paint Tool ===
What it does and how options affect it

=== Texture Smooth Tool ===
What it does and how options affect it

=== Relax Map Tool ===
What it does and how options affect it

== Water ==
Skip for now

== Model and Vegetation Movement Tools ==

=== Snap ===

=== Move ===

=== Rotate ===

=== Select ===

== Vegetation ==

== Models ==

Talk:Lighting

2009-11-18T19:34:07Z

Languard: /* No Water */ fixing a typo my class spotted

== Lighting Bugs ==
OK, lighting is borked for creating new levels. Lets get some conversation going that doesn't get buried under endless posts about making characters bi and taking their clothes off :p I'll start by listing the bugs we have found so far.

# The lightmap 'cracks' along chunk boundaries in terrain levels, producing unexplained shadows.
# Sunlight doesn't work in terrain levels. An ambient light must be added
# Water is broken in game. Looks fine in editor, but non-existent in game.

Reproduction Steps: All steps assume starting with a clean terrain level built with these options:

[[File:ExtLevelOptions.png]]

=== Base Steps ===

And all have the following basic steps:

# Save the level
# Add export area
# Define area - set the green square to cover the entire mesh
# Add a start point roughly in the center - Possible bug? If I add the start point before the area, path finding will not recognize it.
# Set start point in export area
# Click Render Lightmaps
# Toggle Lightmap on and Fully Lit off to verify there is no light. This confirms bug 2, no sunlight. Unless I've missed where it says sunlight doesn't act like, well, sunlight.
# Add a light roughly in center. Change type to Ambient, Postion.Z to 25
# Toggle Lightmap off
# Hit the Render Lightmap button
# Toggle Lightmap back on to verify ambient is working. I have never seen lightmap cracking at this point.

Phew. And I don't really want to admit how many times I've gone through this.

=== Lightmap Cracking ===
This one is beating me. I cannot come up with a 100% sure-fire way to force cracking. This time it happened when I did a full local post for the second time. If someone can come up with repro steps, it would be much appreciated. Here's a screen shot of the cracked level. Edit: Messing around and noticed that the cracking happened again on the second Do All Local Posts. However it's 1am so further testing will have to wait.

Edit from [[User:Languard|Languard]]:Dug a hole and placed three baked point lights to light it up. After rendering lightmaps and before posting, the lightmaps cracked. Tried to reproduce but on the second time instead of cracking, one chunk became fully lit and completely unaffected by baked point lights.

Edit from [[User:Ainiana|Ainiana]]:In my experience the 'cracked' light map appears to occur when multiple baked lights are applied to the same exterior area. I have also have experienced the 'one chunk unaffected by baked point lights' on another occasion (this only took 1 baked light to reproduce). On all occasions water was not visible in game when testing (using the steps outlined below).

An example of a 'cracked' lightmap.
[[File:lightmapCrack.png]]

:We've seen this internally as well, there appears to be a bug with how sunlight is handled. Our lightmapper guru has had the bug passed on to him so hopefully a fix will come along soon but at this point we don't know exactly what's wrong so we can't give any sort of estimate. [[User:BryanDerksen|BryanDerksen]] 17:49, 16 November 2009 (UTC)

=== No Water ===
# Use the deform tool to dig a hole
# Right-Click->Insert->New Water Mesh
# Drag it over to the hole
# Make it large enough to cover the hole
# Right-Click->Insert->New Light Probe
# Drag light probe so that is roughly centered on the water and slightly above it
# Place some small oaks around for reflection
# Render Lightmaps
# Render Light Probes
# Verify that yes, it looks correct <BR> [[File:levelWater.png]]
# Do All Local Posts
# Save and close level
# Create new area, set level as layout
# Add a waypoint
# Override Export starting area
# Get into game, verify that water is...missing
[[File:ingameNoWater.png]]

Please, if anyone else has anything to add to this, do so. The more info we can concentrate here, the easier it will be for BioWare to fix this :)

Level Editor Tutorial

2009-11-16T21:49:00Z

Languard: /* Pathfinding and Obstructions */ Added in a bried description of the terrain blocker tool plus minor formating

=Building your room (Interior Level)=
How to create/lightmap a [[Level]] for use in an Interior [[Area]]:
Objective: Following along with this tutorial, you should be able to create a simple room from scratch in 10 minutes or less

This was lifted from a posting by St4rdog http://social.bioware.com/forum/1/topic/8/index/150840
It needs some additional formatting love, but is as good starting place for people to create usable interior levels

File > New > Level > Room Level

* Create a player start. Click flag icon next to lightmapping icons > click anywhere on ground. This is the starting location for the pathfinding algorithm. Make sure you place it somewhere where you expect to be able to walk.

* Click on "New Area" in top-left list > Object Inspector in bottom-right > Layout Name > anything under 8 characters no spaces or strange characters.

*Right-click in 3D view and select Insert > New Room.
*Click Models (blue box) in the Palette in the top-right. These folders contain everything such as floor tiles/walls etc to build your rooms.
*Enable Grid Snap with the magnet icon to make sure they line up.
*The "prp" folder contains things like beds/barrels to clutter your Level.
Hint: Use [[DATool]] (3rd party tool downloadable at http://social.bioware.com/project/41/ )to browse through these quickly to find the floors/walls you want.

Note: If you get "Cannot spawn models into the selected parent object" when trying to place a model then you don't have "New Room" selected.

==Adding lights==

* Right-click on "New Room" in top-left list > Insert > New Light

* Move it up off the floor a little. In Object Inspector > "Color
Intensity" 2 or more > "Light Type" Point - Static (lc) > Choose
any bright color.

*Copy and paste. In Object Inspector >"Light Type" Ambient - Baked (this light stops your shadows being pitch
black) > Choose a dark blue colour and keep the Color Intensity under 2/3.

Note: I'm not sure what the mix of Baked/Static light is supposed to be. If you just put a Baked + Ambient it complains about not having Static, but if you put a Static + Ambient it seems to work fine, but the wiki says Static is the most expensive.

==Rendering Lightmaps==

*Press the Render Lightmaps icon (you need ActivePython 2.5 installed to default location). When it's done click the Display
Lightmaps On/Off icon in the top-left to refresh the results.
*Uncheck the "View Models Fully Lit" icon in the lop-left. You should see shadows from any objects you've dropped in.

note: Lightmap-atlas messages might appear the first time you render. That seems normal.
Sometimes re-rendering the lightmaps messes them up badly when Display Lightmaps On/Off is on. It doesn't seem to use the latest lightmaps. Try pressing Display Lightmaps On/Off a few times to update it. If they're still messed up sometimes one of these fixes it (don't know which)unloading/reloading your Area or Level/changing your Area's layout property/posting your Level to Local.

==Exporting==

*Press the Do All Local Posts icon to the right of the lightmapping icons. It will export the name you typed into the "New Area" "Layout Name". If there's a complaint about walkable/player start then delete your old start then place a new one on a flat area.

*Save your .lvl file. It's not used by the game and the name/location doesn't matter. Only the exported/posted files are used.

==Using this in an Area==

File > New > Area > Any Name

*In the Object Inspector > Area Layout you should get a "..." box (make sure it's Checked Out) > click then select your "Layout Name" which should now be there.

* Now you have a pretty level lightmapped level inside an area.

=Building your terrain (Exterior Level)=
How to create/lightmap a [[Level]] for use in an Exterior [[Area]]:
Objective: Following along with this tutorial, you should be able to create a simple terrain from scratch

File>New>Level

* Choose Terrain (Landscape) Level and then click Next

* Accept the default values for the purpose of this tutorial and click Next and then click Finish. You can learn more about what the different terrain options do at the [[Level editor]] page.

You should now see a flat, dark piece of terrain. To move around you hold down the mouse wheel. If you want to rotate the view press the Alt key while holding down the mouse wheel. You will want some light so you can see what you're doing, so it's good to generate a light source next.

==Lighting:==

* Right click on Terrain World to the upper left and choose Insert>New Light. This will spawn a light source in your area. Make sure you change the Light Type to Ambient - Baked (L). Be sure to click on the Render Lightmaps button if you want to see how your ambient light is lighting up the level.

Now that the terrain is lit we can modify it.

==Modifying Terrain==

The [[Terrain mesh]] tools allow you to modify the terrain by changing elevations, smoothing edges, flatting terrain, or painting textures.

==Water==

Please note that as of build 1.0.982.0 water is broken. You can see it in editor, but it is not making it into the game.

First use the [[Terrain mesh]] tools to make a hole. It doesn't have to be deep. Then right-click on Terrain world and select Insert -> New Water Mesh. Double Click on the Water Mesh to zoom to it. By default it gets placed in a corner. Using the 3 Axis Movement tool [[File:moveTool.png]] grab the water and drag it to your hole. Depending on the size of the hole, you might have to adjust the water mesh size by changing the Size X and Size Y property values. Once you have the mesh placed, it's time to create the light probe. Right-click near the water mesh and select Insert -> New Light Probe. Using the move tool again, drag the light probe so that is roughly centered over the water mesh and slightly above it. Click on Render Lightmaps, then Render Light Probs. You might have to toggle Display Lightmaps, but you should now see your water looking like water and reflecting things around it.

==Placing Models==

* Click the blue box in the Palette Window to access the models that come with the game. The [[Model list]] shows pictures of many of the models available.

* The [[Model]] page has more details on how to work with models.

Tip: I had to change the Snap Options to make the models go where I wanted them. The settings I use were 0.10 for Snap to Grid and Snap Z Size. I also had to turn off Enable Snap to Surface whenever I wanted to change the vertical position of something (like creating the second floor of a building). Enable Snap to Surface is not applied globally, so once you turn it off and position an object vertically, turning it back on will not move that object unless you select it (or have it selected when you turn it back on).

==Adding Vegetation and Wind==

The [[Vegetation]] page includes a list with pictures of the various plants available for placement. If you do not see the plants once you place them with the Scatter Object Tool then you may need to adjust your SpeedTree Rendering Distance Selector. This is a drop-down that you will see in the Tool Bar. It lists the distances at which plants will be visible. I set it to Very Far and left it there.

Each level can have one active wind object in it. The location of the wind object doesn't matter. The wind object defines how wind behaves on this level, which is used for such things as flapping banners and swaying trees.

Image:Level editor wind object.png

The Wind Object may be found by right clicking on Terrain World and selecting:

Insert>New Wind Object

==Pathfinding and Obstructions==

The pathfinding process lays down a grid of points that are marked "accessable" if they can be reached from a pathfinding start spot via passable terrain. This is essentially a flood-fill algorithm.

You must create an Exportable Area before you can generate any pathfinding data.

* Click on the purple + in the tool bar. This will open an Area Properties window. The [[Level editor]] page has moire details on this process, so I will just keep these steps very basic.
* Name your Exportable Area in the Layout Name field of the Area Properties window. The name of an exportable area layout is limited to seven characters. BioWare uses the following naming system:
** Three-letter prefix that describes the region or plot the layout is for. For example, "ost" for Ostagar and environs.
** Three-digit number that uniquely identifies the layout within that region. Increments of one hundred are commonly used for major areas to allow sub-regions to be grouped together.
** A single character identifying variants of the layout. For example, a "d" suffix for the "daytime" version of an exterior layout. "d" is also often used to mean "default", for areas where day and night are irrelevant (deep in a cave, for example).
* Define your walkable area. Do this by clicking the Define Area button in the Area Properties window. The green box must include any areas that you want players to be able to walk. If you click in a corner of the level the green box will appear there. You can then expand it by dragging the corner.
* Close the Area Properties window.

In most cases you will want to block off certain areas of your terrain.
* Turn on the Build Terrain Blocking tool. It is the middle mountain icon.
* Using left-click to place and right-click to end chains/delete, place down blocks or 'walls' around areas you don't want the player to enter
* Be sure to provide visual clues if it isn't obvious why the player can't walk there.

Now that you have your exportable area you can generate pathfinding data.

* Place a Starting Point in your level. I found that pathfinding does not work if you place the Starting Point before you have an Exportable Area. To place a Starting Point click on Setup Start Point in the tool bar.
* Record the name of your Starting Point by clicking on it and looking at the name in the Object Inspector. Do not change the name - changing the name can prevent pathfinding from working.
* Click Exportable Area Properties in the tool bar to open the Area Properties window. Put the Start Point name in the appropriate field and close the window.

You should now be ready to generate pathfinding data by clicking on the Generate Pathfinding for Active Area button in the tool bar.

==Converting Levels into Areas==

Click on Do All Local Posts. This can be found in the menu at Tools>Export>Do All Local Posts

Your level has now been converted and can be used to make an area. The [[Area tutorial]] will walk you through what to do next.

[[Category: Tutorials]]

Talk:Level editor

2009-11-16T21:06:10Z

Languard:

Worth mentioning that the Level editor only works with the 3dsmax mouse controls. -- [[User:Proleric1]]

: And also the flycam mode, which I tend to use myself since I've no experience with 3DS Max and find it very nonintuitive. I've added this to the lead paragraph, though I expect there'll eventually be a better place to move it to. [[User:BryanDerksen|BryanDerksen]] 21:54, 19 July 2009 (UTC)

== Exportable Area ==
Start Point Name - what in the heck is this for? It doesn't affect pathfinding, and I have found no place anywhere in the editor that actually uses this field. Is it a legacy field that just hasn't been removed? [[User:Languard|Languard]] 17:37, 16 November 2009 (UTC)

== Pathfinding ==
Didn't even notice someone had already put in instructions for the terrain tools. Since I had missed it, and at least one other person on the forums missed it, I removed the old text and kept my own. The differences are that I put in two screen shots instead of one and explained all three icons.