|
|
| (100 intermediate revisions by 40 users not shown) |
| Line 1: |
Line 1: |
| [[Category:Level Design]]
| | {{LanguageBar}} |
| =Introduction=
| |
| A ''Navigation Mesh'' represents the "walkable areas" of a map. This data is '''required''' by [[bot|Bots]] and Hostages in Counter-Strike:Source, allowing them to "know" how to move around in the environment.
| |
|
| |
|
| Navigation Mesh data is stored in a ''.nav'' file corresponding to the map file (.bsp) for which it is used. For example, the nav mesh for <code>cstrike\maps\de_dust.bsp</code> is stored in <code>cstrike\maps\de_dust.nav</code>. | | A [[w:Navigation mesh|'''Navigation Mesh''']] ('''NavMesh''' or '''nav mesh''') is a data structure that stores data used for path finding, which is typically used by bots. In {{source|4}}, navigation meshes are used by the following entities: |
| | # [[Bot]]s and Hostages in: |
| | #* {{css|4}} |
| | #* {{csgo|4}} |
| | # [[NextBot]] entities in: |
| | #* {{l4d|4}} |
| | #* {{l4d2|4}} |
| | #* {{gmod|4}} |
| | #* {{tf2|4}} |
| | #* {{p3|4}} |
| | #* {{jb3|4}} |
| | #* {{bms|4}} |
| | …to realize what's navigable in their environment, and path to their desired destination. |
|
| |
|
| =Automatic Navigation Mesh Generation= | | ==NAV file format== |
| To support the many community-created maps, Counter-Strike:Source includes an automatic mesh generation system. The first time you attempt to play a custom map with bots, the generation system will build a .nav file for that map. Depending on the size and complexity of the map, this may take a few minutes to a few hours. Most maps take about 5 minutes to auto-generate a .nav file. Once the generation is complete, a .nav file is saved to your hard drive for future use.
| | {{Main|.nav}} |
|
| |
|
| ==What is Computed During Generation== | | ==NAV files == |
| The following steps occur during Navigation Mesh generation:
| | Navigation Mesh data is stored in a [[NAV]] file corresponding to the map file ([[BSP|.bsp]]) for which it is used. For example, the nav mesh for <code>cstrike\maps\de_dust[[.bsp]]</code> is stored in <code>cstrike\maps\de_dust[[.nav]]</code>. |
| * Starting at a player spawn point, walkable space is sampled by "flood-filling" outwards from that spot, searching for adjacent walkable points
| |
| * Rectangular ''Navigation Areas'' are constructed from the sampled data
| |
| * Hiding and Sniper spots are computed
| |
| * Encounter Spots and Approach Points are computed (this can take awhile)
| |
| * Initial Encounter areas are computed
| |
|
| |
|
| ==Manually Starting the Generation Process== | | ==Navigation Mesh Editing== |
| To start the generation process manually, type <code>nav_generate</code> from the console.
| | {{Main|Nav Mesh Editing}} |
| | {{Main|Nav Mesh Commands}} |
| | The Navigation Mesh Editing is done in-game. A (new) .nav file can be generated with <code>nav_generate</code> (which requires {{Command|sv_cheats|1}} and {{Command|nav_edit|1}}). |
|
| |
|
| ==Viewing the Navigation Mesh== | | ==Game Specific SubVersions== |
| To see the resulting Navigation Mesh, type <code>nav_edit 1</code>. To turn the mesh editor off, type <code>nav_edit 0</code>. You will need to have <code>sv_cheats 1</code> to be able to view the navigation mesh.
| | {| class="standard-table" |
| | | ! Game !! Nav Mesh Class !! Subversion !! Notes |
| ==Explicitly Marking Walkable Areas (ie: "There's no mesh upstairs")== | | |- |
| Some maps that have very steep stairs, ramps, or hills may confuse the generation system, resulting in the Navigation Mesh not covering the entire map. To solve this, you can manually place additional ''walkable markers'' that tell the generator to search outwards from that point during its sampling phase.
| | | {{source|2}} |
| | | {{gmod|2}} |
| To add one or more walkable markers, first aim your view towards a known walkable spot in your map, then type <code>nav_mark_walkable</code> in the console. When you are finished placing markers, type <code>nav_generate</code> to re-generate the mesh.
| | | TheNavMesh |
| | | | 0 |
| ==Quickly Generating Meshes for Testing==
| | | Garry's Mod uses the base navigation mesh (It doesn't use its own implementation unlike Valve games) |
| The analysis phase of the generator can be quite time consuming. To skip it, type <code>nav_quicksave 1</code> in the console.
| | |- |
| <blockquote>'''NOTE:''' "Quicksaving" skips the analysis phase, and the resultant nav mesh will be missing important data required by the CS Bots and Hostages higher-level planning and attention systems. While useful for testing, editing, and tuning a nav mesh, be sure to do a full analyze (ie: <code>nav_analyze</code> with <code>nav_quicksave 0</code>) before publishing your nav file to others.</blockquote>
| | | {{css|2}} |
| | | {{csgo|2}} |
| =Editing the Navigation Mesh=
| | | CSNavMesh |
| [[Image:nav_edit.jpg|thumb|300px|right|Enabling the Navigation Mesh editor in de_dust]]The automated Navigation Mesh generator does a reasonable job of constructing a mesh, allowing you to start using Bots and Hostages on custom maps easily.
| | | 1 |
| | | | * Appends approach area data to each area. |
| However, careful hand-tuning of the Navigation Mesh can markedly improve the performance of Bots. In addition, manually decorating the mesh with ''Place Names'' allows the Bots to tell others where events occur, enhances the Counter-Strike radar and includes Place Names in all radio messages.
| | |- |
| | | | {{tf2|2}} |
| ==The Navigation Mesh Editor==
| | | CTFNavMesh |
| | | | 2 |
| To enable the editor, type <code>nav_edit 1</code> in the console (type <code>nav_edit 0</code> to disable it).
| | | Appends TF2-specific attribute flag to area data. |
| | | |- |
| * The white cross in the center of your view is the ''cursor''. | | | {{l4d|2}} |
| * The Navigation Area you are pointing at is the ''selected area'' and is shown with a yellow outline.
| | | TerrorNavMesh |
| * Navigation Areas that can be reached from the selected area are shown in red.
| | | 13 |
| * The white line in the selected area denotes where the area will be split if the <code>nav_split</code> command is executed.
| | | |
| | | |- |
| ===Area Types===
| | | {{l4d2|2}} |
| {| border="0" cellpadding="0" cellspacing="0" | | | TerrorNavMesh |
| |- | | | 14 |
| | [[Image:nav_jump.jpg|thumb|300px|none|'''Jump areas''' (marked with green X's) tell bots that they must jump to reach the higher connected area, and that this area is not usable as a hiding/sniping spot.]] | |
| | [[Image:nav_crouch.jpg|thumb|300px|none|'''Crouch areas''' (marked with a blue diagonal slash) force bots to crouch when moving through this area.]] | |
| |} | |
| | |
| ===Connection Types===
| |
| {| border="0" cellpadding="0" cellspacing="0"
| |
| |- | |
| | [[Image:nav_connections.jpg|thumb|300px|none|'''Bidirectional (two-way) connections''' (marked with light blue lines at the area edges) allow bots to freely move between the two areas.]] | |
| | [[Image:nav_jump_down.jpg|thumb|300px|none|'''One-way connections''' (marked with dark blue lines) are usually used for "jump-down" links from a high ledge to the ground. This tells the bots that they can jump down, but they can't jump back up. One-way links can also be useful for forcing bots to travel a specific direction, perhaps to set up for a tricky jump.]] | |
| |} | | |} |
|
| |
|
| ==Using Mesh Editing Commands== | | ==See also== |
| Although all of the mesh editing commands can be typed in the console, in practice it is far easier to ''bind'' these commands to keys. For example, <code>bind del nav_delete</code> binds the delete key to the command nav_delete. After this binding, pressing the delete key will delete the nav area under your cursor (if you are nav editing mode).
| | * [[Nav Mesh Commands|Navigation Mesh Console Command Reference]] |
| | | * [[List of L4D Series Nav Mesh Attributes]] |
| You can temporarily bind many commands at once by using a CFG file. This is useful for bot navigation editing, because there are many commands, and you will probably not want them to be permanently attached to your keys. See [[Bot Navigation Editing CFG File]] for a pre-made file and instructions on its use.
| | * [[L4D Level Design/Nav Meshes]] |
| | | * [[L4D Level Design/Nav Flow]] |
| See [[Counter-Strike: Source Navigation Mesh Console Command Reference|Navigation Mesh Console Command Reference]] for a list of all commands related to bot navigation.
| | * [[L4D Level Design/Advanced Nav Editing]] |
| | |
| ==Basic Mesh Editing Commands==
| |
| ===Save===
| |
| Currently, there is no "undo" command in the Navigation Mesh editing system. Therefore, it is very important to '''save your work often''' via the <code>nav_save</code> command.
| |
| | |
| ===Split===
| |
| To split an area into two adjacent, inter-connected areas, aim your cursor at an area and execute the <code>nav_split</code> command.
| |
| [[Image:nav_edit.jpg|400px|Before split]] | |
| [[Image:nav_split.jpg|400px|After split]] | |
| | |
| ===Merge===
| |
| To merge two adjacent areas:
| |
| # Aim your cursor at the first area and execute <code>nav_mark</code>
| |
| # Aim your cursor at the second area and execute <code>nav_merge</code>
| |
| | |
| Note that both areas must be the same size along the edge to be merged.
| |
| | |
| [[Image:nav_mark.jpg|300px|Marked first area]]
| |
| [[Image:nav_pre_merge.jpg|300px|Aim at second area]] | |
| [[Image:nav_post_merge.jpg|300px|Merged]]
| |
| | |
| The resulting area will retain all of the connections of the original two areas, and inherit properties (ie: Place Names, etc) from the marked area.
| |
| | |
| ===Splice===
| |
| Splicing creates a new area between two existing areas. Splicing is a powerful tool, and can be used to easily create sloped areas, as shown in the example below.
| |
| | |
| To splice a new area in between two existing areas:
| |
| # Aim your cursor at the first area and execute <code>nav_mark</code>
| |
| # Aim your cursor at the second area and execute <code>nav_splice</code>
| |
| | |
| [[Image:nav_prep_splice.jpg|300px|Marked first area]]
| |
| [[Image:nav_pre_splice.jpg|300px|Aim at second area]]
| |
| [[Image:nav_post_splice.jpg|300px|New area spliced between]]
| |
| | |
| ===Delete===
| |
| To delete an area, aim your cursor at it and execute <code>nav_delete</code>
| |
| | |
| ===Creating a New Area===
| |
| To manually create a new area:
| |
| # Place your cursor at where a corner of the new area should be
| |
| # Execute <code>nav_begin_area</code>
| |
| # Move your cursor to drag out the area's extent
| |
| # Execute <code>nav_end_area</code>
| |
| | |
| [[Image:nav_begin_area.jpg|300px|Start dragging area at first corner]]
| |
| [[Image:nav_drag_area.jpg|300px|Drag area extent]] | |
| [[Image:nav_end_area.jpg|300px|Area created]]
| |
| | |
| ===Adding and Removing Connections Between Areas===
| |
| The connections between areas define whether an agent can move from one area to another. Usually these connections are ''bidirectional'', meaning agents can move back and forth between two areas at will. However, sometimes the connection is ''one way'', as in the case of high ledges that can be jumped down, but not back up.
| |
| | |
| To make a one-way connection from area A to area B (meaning you can move from A to B):
| |
| # Place your cursor on area A
| |
| # Mark area A with <code>nav_mark</code>
| |
| # Aim your cursor at area B
| |
| # Execute <code>nav_connect</code>
| |
| | |
| To make a bidirectional connection, repeat the above steps reversing the roles of A and B.
| |
| | |
| To remove all connections from areas A and B:
| |
| # Aim at area A
| |
| # Mark area A with <code>nav_mark</code>
| |
| # Aim at area B
| |
| # Execute <code>nav_disconnect</code>
| |
| | |
| ==Adding Place Names==
| |
| ''Place Names'' can be assigned to areas to label that region of the map. For instance, if there is a prominent house in the map, all of the nav areas in the house can be tagged with the "House" Place Name.
| |
| | |
| Place Names are used by the CS Bot chatter system to announce where they are, as well as by the radar to show the current location of the player, and is appended to the player's name when they use text chat or radio commands.
| |
| | |
| To enter and leave "Place Painting Mode", execute <code>nav_toggle_place_mode</code> (assuming <code>nav_edit</code> is set to "1").
| |
| | |
| For a list of all available Place Names, execute <code>nav_place_list</code>.
| |
| | |
| Select a Place by typing <code>nav_use_place (name)</code>. Then aim your cursor at an area you want to label with that Place Name and execute <code>nav_toggle_place_painting</code>. While "place painting" is active, each area you point at will be tagged with the current Place Name. To stop place painting, execute <code>nav_toggle_place_painting</code> again.
| |
| | |
| There are several additional commands that provide tools for picking, flood-filling, replacing, and so on. For a complete reference, see [[#Place Name Commands|Place Name Commands]]. *(Bad or Broken Link)
| |
| | |
| ==Common Mesh Problems and Solutions==
| |
| ===Extraneous Areas on Stairs and Ramps===
| |
| The automatic generation system tends to build areas that hang off the side of stairs and ramps. These should be removed to force the bots to take the stairs or ramp straight-on.
| |
| | |
| ===Railings===
| |
| Railings can be a problem for the current bot navigation system. Including jump-down links that must pass over railings should be avoided unless necessary. The bots will eventually make these jumps, but they are not terribly elegant while doing so.
| |
| | |
| ===Preventing Excessive Jumping===
| |
| Mark an area with <code>nav_mark</code>and use the <code>nav_no_jump</code> command to flag the area to discourage jumping.
| |
| | |
| ===Dealing with Rotating Doors===
| |
| Carving out empty space in the nav mesh to allow for the rotating door.
| |
| | |
| ==Advanced Editing Techniques==
| |
| | |
| ===Ladders===
| |
| Ladders can be manually built against climbable surfaces. Your editing cursor will turn green when pointing at a climbable surface.
| |
| | |
| '''Using <code>nav_build_ladder</code>'''
| |
| | |
| The easy way to build a ladder is to simply point at a climbable surface, and execute <code>nav_build_ladder</code>.
| |
| | |
| [[Image:nav_build_ladder_before.jpg|300px|Point at a climbable surface]]
| |
| [[Image:nav_build_ladder_after.jpg|300px|Ladder created]]
| |
| | |
| '''Using <code>nav_begin_area</code> and <code>nav_end_area</code>'''
| |
| | |
| If <code>nav_build_ladder</code> isn't what you need, you can manually create a ladder:
| |
| #Place your cursor at where a corner of the new ladder should be
| |
| # Execute <code>nav_begin_area</code>
| |
| # Move your cursor to drag out the ladder's extent
| |
| # Execute <code>nav_end_area</code>
| |
| | |
| This can be useful to get bots to start going up the ladder, and jump off halfway up, onto the crate:
| |
| | |
| [[Image:nav_begin_ladder.jpg|300px|Start dragging ladder at first corner]]
| |
| [[Image:nav_drag_ladder.jpg|300px|Drag ladder extent]]
| |
| [[Image:nav_end_ladder.jpg|300px|Ladder created]]
| |
| | |
| '''Reversing ladders'''
| |
| | |
| Sometimes a ladder will be created facing the wrong way. If a ladder is drawn in red, you are looking at it from the back. The ladder is drawn in green if it is facing you. To change the orientation of a ladder, simply point at the ladder and use <code>nav_ladder_flip</code>.
| |
| | |
| [[Image:nav_ladder_backward.jpg|300px|Ladder facing into the wall (incorrect)]]
| |
| [[Image:nav_ladder_forward.jpg|300px|Ladder facing away from the wall (correct)]]
| |
| | |
| ===Obstacle Avoidance and Precision Movement===
| |
| Using <code>nav_precise</code>, <code>nav_walk</code>, and <code>nav_stop</code> to disable local obstacle avoidance behaviors and control bot movement.
| |
| | |
| ===Marking Areas to Avoid===
| |
| Using <code>nav_avoid</code> to tell bots to avoid the area unless the normal route has become too dangerous.
| |
| | |
| ===Controlling Where Bots Can Hide===
| |
| Using <code>nav_no_hide</code> to prevent bots from hiding in that area.
| |
| This can be used to force the creation of hiding spots during the analysis phase.
| |
| | |
| ===Setting up Sniper Spots===
| |
| Mark an area using <code>nav_walk</code> and execute <code>nav_make_sniper_spots</code>. This will break the area into small sub-areas which are used internally by the navigation mesh to encourage sniping.
| |
| | |
| ===Lining up Tricky Jumps and Narrow Doorways===
| |
| Arranging nav areas to force specific paths.
| |
| | |
| * If the bots are getting hung up on the sides of a door or window, you can carve out a narrow path through the middle of the opening.
| |
| * The highest a bot will try to jump is 58 units. If the top of a jump is 59 or more units above the bottom, bots will give up as soon as they jump. If this happens in a spot that the bots can actually jump up to, use <code>nav_corner_lower</code> to lower the upper nav area slightly.
| |
| | |
| [[Image:MaximumJumpCrouch.jpg|300px|Highest possible crouchjump]]
| |
| | |
| =See also=
| |
|
| |
|
| [[Counter-Strike: Source Navigation Mesh Console Command Reference|Navigation Mesh Console Command Reference]] | | ==External links== |
| | * Official forums for the bot system (down) - [http://web.archive.org/web/*/http://www.turtlerockstudios.com/forums/csbot/ Archived version]. |
| | * [https://www.editlife.net/tutorial.php?tutid=60 Waypointing for CS:S Bots/Hostages (Edit Life)] |
|
| |
|
| [http://www.turtlerockstudios.com/forums/csbot/viewtopic.php?t=725 Official forums for the bot system]. | | [[Category:Source]] |
|
| |
|
| {{otherlang:en}} {{otherlang:en:jp|Bot Navigation for Counter-Strike:Source:jp}}
| | [[Category:Level Design]]<!--Why?--> |
Source, navigation meshes are used by the following entities:
Counter-Strike: Source
Team Fortress 2
Left 4 Dead
Left 4 Dead 2