Difference between revisions of "Navmeshing"

From Sunrust Wiki
Jump to navigation Jump to search
Line 1: Line 1:
[[File:Navmeshing article.png|thumb|right|upright=1.05|<div style="text-align: right">''Art by AltShadow.''</div>]]
[[File:Navmeshing article.png|thumb|right|upright=1.05|<div style="text-align: right">''Art by AltShadow.''</div>]]
<!-- <span style="color:orange">'''Navmeshing'''</span> – the process of creating navigation for bots, or more simply, creating paths so that bots can work correctly on a given map. There are many different types of bots that are used for the zs gamemode: AzBots, D3Bots, MarcoBots, etc.


MarcoBots are currently used on Sunrust servers. MarcoBots are not open-source bots, they are private and exclusive type of bots and you cannot download them for your single player. Therefore, the navmesh creation takes place on a dedicated server (or directly in the main server itself).


The advantages of MarcoBots is the simplicity navmesh creation, the automation of many bot actions, since you don’t need to specify when they need to jump or crouch, and a huge level of optimization, as a result these bot load server much less and this leads to less lags.


The better navmesh is created, the more powerful the bots will be, since they will know how to act in each area of the map. A good navmesh also affects the optimization, server network and is especially necessary for the correct work of [[The Undead|Great Evils]] - exclusive zombie boss classes only for bots.


== Terminology ==


{| class="wikitable"
|- style="vertical-align: center;"
! scope="row" style="width: 13%;" | <span style="color:orange">Navmesh <br>(abbreviated "mesh")</span>
| style="padding: 0.8% 0.5% 0.8% 0.5%;" | Navigation for bots.
|- style="vertical-align: center;"
! scope="row" style="width: 13%;" | <span style="color:orange">Navmeshing</span>
| style="padding: 0.8% 0.5% 0.8% 0.5%;" | The process of creating navigation for bots.
|- style="vertical-align: center;"
! scope="row" style="width: 13%;" | <span style="color:orange">Nodes</span>
| style="padding: 0.8% 0.5% 0.8% 0.5%;" | Points between which bots move and where they can find you.
|- style="vertical-align: center;"
! scope="row" style="width: 13%;" | <span style="color:orange">Paths <br>(or "links")</span>
| style="padding: 0.8% 0.5% 0.8% 0.5%;" | Connections between nodes that allow or not move between specific nodes.
|- style="vertical-align: center;"
! scope="row" style="width: 13%;" | <span style="color:orange">Areas</span>
| style="padding: 0.8% 0.5% 0.8% 0.5%;" | A special type of bot navigation that differs from nodes. Instead of nodes, you select the required area and the bot can find you if you are in it. Will be discussed this type of navigation in more detail below.
|- style="vertical-align: center;"
! scope="row" style="width: 13%;" | <span style="color:orange">Targeting</span>
| style="padding: 0.8% 0.5% 0.8% 0.5%;" | A bot pathfinding for the closest or highest priority target.
|- style="vertical-align: center;"
! scope="row" style="width: 13%;" | <span style="color:orange">Pursuit mode</span>
| style="padding: 0.8% 0.5% 0.8% 0.5%;" | The bot stops moving on the nodes and starts moving exactly behind you, is activated for ~200 units.
|}


== Required commands and control ==
To be able to create navmesh, you need to be granted access to a dedicated navmesh server. Contact Scott to have access to dev server: Scott#3224. After obtaining the necessary rights, you can connect to it and begin to create navmesh.
Dev Server IP: 104.194.10.86:27020


Next, you need to get the navmesh tool and start creating the navmesh. Let's look at the required commands for this:
- /navmeshtool – gives you a navmesh tool
- /startmeshing – gives you a navmesh tool, god mode and an infinite wave time
- /changemapnavmesh mapname – allows you to change the map on server
- zs_admin_purgepaths – completely clears navmesh (SA only,console command)
- /give weapon_zs_adminpathtool PlayerName – Alternative way to get navmesh tool (SA only)


[[console_commands.png]]


navtool_weapon_choice.png
After you give yourself a navmesh tool, you may notice control tips in the upper left corner. Disable the experience display in the options in “F4 –> Interface” to see them more correctly. If you also have spark_currency_widget 1, disable it as well.
When you hold down the “Alt” key in the lower right corner, a menu for tool control will appear. Consider this interface:
navmesh_menu.png


Path edit mode path_edit_mode_options.png Allows you to select the navmesh type. Will be discussed in more detail below.
Path draw distance path_draw_distance_menu.png Allows you to change the display range of nodes
Flags navmesh_menu_flags.png Ghost Mode – Gives you noclip.
Hide Air Paths – Hides air nodes.
Hide Sublevel Paths – Disables the visibility of nodes you cannot see.
Draw Through Walls – Enables drawing nodes through walls.


Let's consider these options in more details.


== Path edit mode ==


path_edit_mode.png


=== Create Node ===
This mode allows you to create nodes and select types of nodes.
Control:
cratenode_control.png


LMB – Creates a node at the specified point
RMB – Deletes the selected node
R – Creates a node that is in your position
Shift + RMB – Removes the node that is in the position of your gaze. This is an extremely useful tool that allows you to delete nodes that you cannot direct, such as nodes in the air or underground.


Options for Create Node:
navmesh_nodes_noautopath_menu.png


Path type – allows you to select the type of node you want to create
No Auto-Path – Creates a node that will not automatically connect to other nodes


=== Node Types ===
Regular regularnode_example.jpg A common node type that allows bots to walk between them and automatically connects to all visible nodes.
No Auto-Path noautopathnode_example.jpg A common node type, but will not automatically connect. This kind of node must be connected using the “Edit ReachSpecs” option, which will be discussed below.


Changes the color to red for the regular node and adds a red icon on top too. For all other node types, simply has a red icon on top.
Flying flyingnode_example.jpg An aerial node type that is created for flying zombie classes, such as Wisp. Creates a node at your position. Since there are no regular flying classes on sunrust servers, creating a flying node is unnecessary.
Ladder laddernode_example.jpg A noclip node that allows bots to fly through paths in and out of it.


You need to be extremely careful with this type of node, since it gives "cheats" to bots for a certain segment, which may not be to the liking of players.


This node is often useful for long ladders or ladders that are difficult for bots to climb, but it can be used for other gameplay elements as well.


Let's consider an example of the correct placement of nodes for correct bots work:
- 1 regular node at the bottom of the ladder
- 1 ladder node on top of the ladder. It can be located both on the ground or on the ladder prop itself, or in the air above the ladder case opening
- 1 regular node on top of the ladder on the ground a little further from the ladder node.


correct_placement_ladder_topnode.jpg
correct_placement_ladder_bottomnode.jpg


[[Tip icon]] Tip: The “regular - ladder - regular – ladder” connection will speed up the bots, so this can be used for speed boosts. But the bots will not noclip right up to you, they will stop at ~200 units and start moving to you at a normal speed due to the activation of the “pursuit mode” (this will be discussed below). This is useful for surf parts of the map, for maps where zombies need to be extremely close to people, etc.


nodes_speed_boost.jpg


[[Bug icon]] Bug: If you use this node with a HL2 ladder, then the bot may not stop at the node, but fly to the nearest target with a noclip. This is because HL2 ladders hook you to the ladder at a certain point and you can climb towards other exit points. A bot with a ladder node doesn’t touch them (or doesn’t hit the node), so it just goes to the nearest target.
Always check what type of ladder case you must make sure this doesn't happen! If this is a HL2 ladder, then either don’t use the ladder node, or use it so that the bot doesn’t get to the point where it hooks onto the ladder (i.e. as far as possible from the beginning of the ladder).
Armory Node armorynode_example.jpg Node designed for placing the armor crates on HG. Not used, it is advisable to delete such nodes.
No Leave Node noleavenode_example.jpg A special node that makes bots go exactly at it or along the path from one to another. With a regular node, bots can deviate slightly, because of which they can fall on some places.


A great example is the sewers on the zs_obj_6_nights_v15 map, where bots must move on small boards, causing them to fall off with regular/no auto-path nodes.


noleavenodes_application.jpg


[[Tip icon]] Tip: Sometimes no leave nodes can help with the pursuit mode, so the bots will function more correctly and attack the cade instead of trying to hit you through the wall. Of course, a lot of places are better fix with volumes, but that can help.


== Overview ==
noleavenodes_disable_pursuit_example.jpg


[[Bug icon]] Bug: Due to the fact that no leave node forces bots to follow them exactly, sometimes bots can start spinning as if they got stuck when they hit the node, but in fact they are trying to get to it more accurately position and after a while they begin to walk normally along them. Therefore, it is not recommended to use these nodes in places of good fire angles, where they can become an easy target for survivors.
Water Node waternode_example.png This node is created by placing a regular node in water. This also works for a flying node, which allows you to place nodes not only at the bottom, but also in the water itself.


Soon...
Unfortunately, these types of nodes turn out to be very "dirty" for the water space and rather difficult to remove, and bots are not so good at walking with them. I highly recommend using “areas” instead of water nodes.


[[Bug icon]] Bug: For this type of nodes only the “water path” created automatically works, and this node can only function with similar water nodes or just regular nodes. This means that you cannot add a teleport path or make a link to a ladder, the bots simply will not perceive it. To solve this problem, use regular nodes connected to the ladder, then lower the lower one into the water using “EditNodes mode” and connect it to the water node.
[[Bug icon]] Bug: Sometimes with water nodes bots can float up to the ceiling, causing them to get stuck. This is very important for underwater caves like zs_obj_enervation_v22. It is recommended to use “areas” for the water.
=== Edit ReachSpecs ===
With this mode you can change paths ("links") between nodes. For example, you can delete the path from one node to another or completely disconnect the nodes, as a result of which the bots will either be able to go to this node, but will not be able to return, or, accordingly, will not move between these nodes at all. It also allows you to create special paths between nodes, for example, fast jump paths or teleport paths.
Regular nodes automatically create paths between themselves, but sometimes they may not be correct, so this is an extremely useful tool to edit them. If there are a lot of nodes, it will often be easier to use “Create nodes + Path draw distance”. This will be discussed later.
autopaths_nodes_example.jpg
Controls:
editreachspecs_control.png
editreachspecs_selected_control.png
When choosing a node:
LMB/RMB – Select the node on which the green icon will appear to edit its paths.
editreachspecs_node_choice.jpg
Shift + LMB/RMB - Select the node that is in the position of your gaze.
With a selected node:
LMB – Creates a path from the node that you have selected to another node of your choice, where the node with the red icon is the one you have selected, and the node with the green one is the one you want to select
editreachspecs_choice_1st_and_2nd_nodes.jpg
RMB – Deletes path from the node you have chosen to another node.
Shift + LMB – Creates a path from the node that you have chosen to another node of your choice, which is at the position of your gaze
Shift + RMB – Deletes the path from the node that you have chosen to another node, which is in the position of your gaze
A useful example to make it easier to understand how this function works.
editreachspecs_exampleingame.gif (mp4)
=== Path Types ===
editreachspecs_flags.png
Flying flyingpath_example.jpg Used for flying classes. Not needed as there are currently no flying classes for bots.
Headcrab jump headcrabpath_example.jpg Used for jumping or paths where only headcrabs can go. Since bots don’t use these classes, it is not necessary to create these paths.
FastZombie leap fastleappath_example.jpg Used for fast zombie jumps. It is not recommended to use it because bots rarely use these classes.
[[Bug icon]] Bug: This type of path only works with nodes and does not work with “areas”. On "areas" they don't try to jump, they just go forward and get stuck.
[[Bug icon]] Bug: Since bots can often miss the desired node, they can get stuck and this can cause a server crash!
FleshBeast climb fleshbeastpath_example.jpg Not used.
Door path doorpath_example.jpg An extremely useful tool that detects a trigger on a door and activates this path when the trigger is enabled. It’s an indispensable tool for most obj maps.
Let's take the zs_seclusion map as an example. When the board on the door is broken, the door will open, so until the trigger is activated, this path will be inactive.
doorpath_usage_blockentity_example.jpg
doorpath_usage_example.jpg
Don't confuse this with a door that opens with a button! Bots won't press the button and open that door, they just won't use it until it's open.
This path only works with brush entities, does not work with props!
[[Bug icon]] Bug: This path is ignored by the ladder node; bots will always use it.
Teleport hack teleportpath_example.jpg Used to teleport from one node to another. Not to be confused with teleports on the map! This is a very "cheating" tool, so it is recommended to use it in extreme cases. Better to use a ladder node.
Zombies only zombieonlypath_example.jpg Used as a regular (auto) path to connect all types of nodes. Enabled automatically. Do not need to use this flag
Humans only humanpath_example.jpg Used only by bots in a team of survivors. Since bots in the human team have not been added to the game, this type of node doesn’t need to be used.
No strafe path nostafepath_example.jpg It’s used to disable bhop or other similar movement on some paths. Since bhop is disabled for bots, these paths are not used.
Water path waterpath_example.png Automatically created for water nodes.
=== Edit Nodes ===
A mode that allows you to replace a node to another location while saving paths for it. It must be used carefully, otherwise some of the saved paths may go through the wall.
Controls:
editnode_control.png
editnode_selected_control.png
Node selection:
LMB – Select a node for replace
R – Select a node at the position of your gaze
Selected node:
LMB – put the node in the desired position
R – Put a node on your position
RMB – Deselect
Using:
editnodes_exampleingame.gif (mp4)
=== Volumes ===
Allows you to create playerclip (invisible walls), trigger_hurts, etc. brushes. An extremely useful tool when used correctly.
volume_navmesh_example.jpg
Basically, it is very useful for placing brushes that will not let anyone pass to fix the map or fix the bots that are not working properly. The fact is, since bots automatically crouch/jump over obstacles, decorative geometry can cause disruption of their work. For example, if the ventilation has a 1-unit brush at its exit, then the bots will jump on it instead of getting into the ventilation, which will cause them to get stuck. If you put block all volume on top, then they will use ventilation correctly. However, it will not have any effect on the gameplay. It also works the other way around, when bots need to jump, they can crouch and get stuck.
block all.gif (mp4)
This brush is also used to cover elements that don’t greatly affect the gameplay, such as fences/handrails brushes, static fences/handrails props, any obstacles from static props, holes in the walls (through which a normal class cannot pass), etc. This can significantly fix bots pathfinding for their correct work.
This issue is due to the "pursuit mode". Bots at a distance of ~ 200 units stop moving exactly along the nodes and start moving exactly behind you, repeating some of your movements. But this mode works when there are no obstacles between you and the bot, which leads to bots getting stuck in some places
volume_using_1.jpg
For specific examples, you can look at the maps zs_fear_nuclear (the hole for crawlers/headcrabs does not work correctly), zs_obj_day_zero_v16 (the final part broke bots targeting because of fences and bad brush building), zs_obj_filth_v19 (too many changes due to not using playerclip on the map itself), zs_detriot_skylines_v1 (due to the fact that there was no playerclip on the brush fences, bots tried to go through walls with pursuit mode)
Controls:
volumes_control.png
volumes_selected_control.png
General:
LMB - Create Brush
R - Remove brush
When creating a brush:
LMB - put the end point of the brush
Shift + LMB - put the end point of the brush at your position
RMB - Cancel Creation
[[Bug icon]] Bug: The brush after creation turns out to be a little larger than you want to create, so initially take a smaller area so that you get a smooth geometry!
[[Bug icon]] Bug: If you are a mapper use playerclip on ladders, especially if you can shoot or hit through them! This breaks the bots targeting, and they start to malfunction.
Volumes types:
The names speak for themselves what and how each type does.
volumes_types.png
=== Nav Mesh ===
Allows you to create and edit "areas" - a special type of navmesh that is fundamentally different from nodes. Instead of placing multiple nodes in a room, you select space for the bots to navigate.
navmesh_area_example.jpg
The navmesh made with areas is much more optimized and improves server performance but takes much more time to create. It is often combined with nodes, because nodes are a priority for bots and can be used to manage them more efficiently.
MarcoBots areas work differently from D3Bots, in fact, an area is a kind of nodes. Look at the picture for a better understanding of how areas work.
areas_work_essence.png
Controls:
navmesh_areas_control.png
navmesh_areas_selected_control.png
Basic:
LMB - Add area start point
RMB - Delete area
R – Resizes an area
When the first point of the area is set:
LMB - Set the end point of the area
RMB - Delete start point
Flags:
navmesh_areas_triangle_flag.png
Auto-Generate NavMesh - Not working and not used.
Navigate a nav area - Not used
Use Triangle Mesh - Allows you to create a triangular area in the form of an isosceles right triangle (square truncated diagonally)
triangle_area_example.jpg
Some materials to help you better understand how areas are created:
navmesh_areas_creation_ingame.gif (mp4)
triangle_areas_creation_ingame.gif (mp4)
More specific examples of creating navmesh using areas will be described below.
=== Settings ===
Used only by developers or SA.
== Path Draw Distance ==
path_draw_distance_menu.png
An extremely useful tool that allows you to change the drawing distance of the navmesh. This can often help to find where some paths are going by setting the range to “short”; so that in some places the whole view does not turn into spaghetti; so that you can take the final navmesh photo. Draw range also has a big impact on your fps.
Look at this example to better understand how draw range can be used effectively:
use_draw_distance_changes_to_viewanddelete_paths.gif (mp4)
== Navmeshing with nodes==
Navmeshing with nodes is the simplest and fastest navmeshing method. This method is often temporary till an area mesh is created, but the principles discussed in this heading will form the basis of any navmeshing method.
To create navmesh with nodes, you need to use the edit mode "Create node" and "Edit ReachSpecs". The nodes will automatically connect to each other if you place regular nodes. The red cube from each node will show the maximum distance at which the bot can detect you. But the fact that the distance is quite large doesn’t mean that you only need to place a couple of nodes on the map and your navmesh will be ready. You need to put the required number of nodes so that the bots can move freely around the map when they are not in "pursuit mode".
correct_distance_for_put_nodes.gif (mp4)
Consider navmesh for staircases. It is enough to put just a few nodes for the bots to work correctly. You don't need to put one node for each step. Overall, this simple example shows that giving bots more freedom to overcome obstacles automatically will perform much better.
correct_stair_node_example.jpg
wrong_stair_example.jpg
Now let's look at how to work with windows. The best way is to place one node near the window and one on the other side. Bots will treat the window as an obstacle to jump over, instead of jumping onto the node on the window. That is, the less you control bots, the better they will work.
correct_windows_nodeplacement_example.jpg
Consider boxes as a final example. The principle of working is practically the same as for the stairs, but the “steps” have become larger.
correct_crates_nodeplacement_example.jpg
[[Tip icon]] Tip: Don't place your nodes close to vertical surfaces like walls. If the node is close to the wall, then the bot next to these nodes will crouch! Bots will be an easy target for shooting.
node_near_the_wall.jpg
[[Tip icon]] Tip: Each node that connects automatically can be easily disconnected, because if you put another automatic regular node in front of this node in the direction of the path, then the paths switch to it.
Let's create two stripes of nodes. Let's place auto regular nodes.
navmesh_2_lines_of_nodes_connect.jpg
Now disconnect them using other nodes. Let's place a lot of auto regular nodes in the center and delete them. As a result, we will get 2 lines of nodes that will not be connected.
navmesh_2_lines_of_nodes_unconnect.jpg
Example in GIF for better understanding:
crate_2_lines_of_nodes_unconnected_ingame.gif (mp4)
Now, let's say we need to disconnect some node or line of nodes from others. We use the same example described above
navmesh_node_need_unconnect.jpg
By adding a couple of nodes in front and deleting them, we can easily detach what we need
navmesh_line_of_nodes_manynodes_unconnect.jpg
GIF example:
crate_line_of_nodes_unconnected_ingame.gif (mp4)
With this tip, you can very quickly delete paths, almost without resorting to using the Edit ReachSpecs mode, without connecting/disconnecting each node one by one. If you think the auto-mode is "disgusting" and impossible to keep track of, then this tip and Path Draw Distance completely solve this problem and significantly speed up the process of creating a navmesh.
== Navmeshing with areas ==
Navmeshing with areas uses the same rules as node navmeshing, except that you have areas instead of nodes. You should select an area where bots can find you.
It is important to understand that nodes and areas differ not only in the way they create navigation. Nodes are a priority for bots, so they will choose a node path rather than another. This can often lead to issues when bots will walk on the same nodes indefinitely. Also, the ability to jump over doesn’t work for areas (i.e. bots will not jump from one roof to another, etc.), and the fast paths also don’t work. Therefore, you need to combine nodes and areas for a good navmesh.
An example of using nodes for a ladder case with areas:
correct_areas_ladder_example.jpg
The areas must be connected to each other. This means that to connect several areas, you need to create a small area in the doorway, etc., or use the method of nodes, connecting them with areas. If areas are much higher in relation to other areas (roofs areas), then they need to be connected to more distant areas so that the bots can jump much faster.
areas_shouldbe_on_any_entrance.jpg
This is very important as it can lead to incorrect pathfinding for bots. Let's take this example:
areas_connecting_wrong.jpg
areas_connecting_correct.jpg
[[Tip icon]] Tip: When creating areas in entrances, it’s much better to create an area slightly smaller than the entrance itself. Bots will get stuck less in front of the entrance and will move closer to the entrance center.
correct_entrance_example.jpg
[[Tip icon]] Tip: Areas are easiest to create "from the corner", this will make it easier to find the area boundaries.
good_example_for_areas_creation.gif (mp4)
When creating areas on complex geometry, such as circular and semicircular surfaces, complex surfaces with many props, rooms with many decorative elements, etc., you need to understand that you don’t need to mesh everything with detailed precision or don’t mesh something at all. You will be in one of the other areas, so it makes no sense to create it on small ledges, this will simplify navmesh several times
Example of decorative beams on the walls:
correct_example_areas_1.jpg
wrong_example_areas_1.jpg
[[Tip icon]] Tip: For long staircases, it is a good idea to divide the area into several so that the areas correctly cover the surface!
Example for complex surfaces:
multiefaceted_entrance_example.jpg
For props, it’s much better to use nodes instead of creating multiple areas there:
correct_placement_nodes_to_areas_crates.jpg
correct_placement_nodes_to_areas_crates_withoutnodeonmiddle.jpg
[[Tip icon]] Tip: You can create areas underneath static props that you can jump over. Be careful with brush entities, as they may incorrectly create a detection area (red cube)
[[Bug icon]] Bug: Areas can automatically connect through thin walls or through props. Watch how they connect!
always_check_how_areas_connected.jpg
[[Tip icon]] Tip: When creating nodes to fall, put a no leave node in the air and put a regular node on the area. Connect them
correct_example_for_path_to_falloff_into_hole.jpg
correct_example_for_path_to_falloff_into_hole_lesserhole.png
When creating areas on displacements, you need to be extremely careful, as geometry can often be quite tortuous, even if it does not seem so at first glance. It is recommended to create smaller areas so that they can approximate the displacement.
navmesh_areas_on_displacements_example.jpg
Triangular areas are an extremely useful tool for creating areas on displacements. Consider this example:
displacement_areas_example_1_no_areas.jpg
Here is a "pit" that goes down from all sides, so it would be much better to use triangular areas:
displacement_areas_example_1.jpg
displacement_areas_example_1_drawing_through_walls.jpg
Let's look at another example. Here is a slide that rises to the wall.
displacement_areas_example_2_no_areas.jpg
When using triangular areas, here we get
displacement_areas_example_2.jpg
displacement_areas_example_2_drawing_through_walls.jpg
[[Tip icon]] Tip: Triangle Areas are a very useful tool to create nice areas for almost any surface
good_example_for_triangle_areas_uses.png
[[Tip icon]] Tip: Bots work much better underwater with areas than with water nodes. Try to make areas for underwater surfaces!
water_areas_example.png
== [[File:Youtube icon.png|frameless|45px]] YouTube videos ==
https://youtu.be/LLGLuRNalYE - Areas navmeshing
https://youtu.be/82vNoRpGTCs - Areas navmeshing
-->
__NOEDITSECTION__
__NOEDITSECTION__

Revision as of 09:30, 25 August 2020

Art by AltShadow.
Retrieved from "https://sunrust.org/wiki/index.php?title=Navmeshing&oldid=1898"