This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
navmesheditor [2017/01/04 18:34] – created fxfire | navmesheditor [2017/06/14 12:05] (current) – fxfire | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | **Under Construction** FIXME | + | =====Navigation Mesh Editor===== |
+ | The Bot operates ontop of a so called Navigation Mesh. This is a surface generated from many Triangles which present the input mesh data. | ||
+ | In order to build a navigation mesh, the triangle mesh has to be recorded. | ||
+ | |||
+ | Under C: | ||
+ | .obj - "mesh input data" aka the yellow mesh \\ | ||
+ | .nx2 - the built navmesh (from the input data) aka the purple-ish mesh \\ | ||
+ | .omc - offmesh connections, | ||
+ | .cub - cubes for flying & under water navigation\\ | ||
+ | .cpc - cube-floor-connections, | ||
+ | .mmn - macro mesh nodes \\ | ||
+ | .mmp - precomputed navigation paths between macro mesh nodes\\ | ||
+ | By default, the .obj files are 0 bytes. This data is only needed for people modifying the meshes. To not forcing everyone to download several GB of not needed data, these files are empty. If you want to edit an official navigation mesh file, you'll need to be given access to the original .obj file and have to replace the one in your local folder. Then you can edit the navigation mesh. | ||
+ | \\ | ||
+ | === 1. Creating a Navigation Mesh === | ||
+ | |||
+ | {{youtube> | ||
+ | |||
+ | === 2. Flying / Diving - Cube Mesh Recording | ||
+ | |||
+ | {{youtube> | ||
+ | |||
+ | \\ | ||
+ | |||
+ | === 3. Cube-Floor-Connections === | ||
+ | {{:: | ||
+ | Cube-Floor-Connections are by default automatically placed when Cubes are recorded. The MeshManager allows you to manually place additional connections, | ||
+ | \\ | ||
+ | |||
+ | |||
+ | === 4. Macro Mesh === | ||
+ | |||
+ | {{:: | ||
+ | For very long distances and to quickly check if a point can be reached by navigation without freezing the game ;), a new MacroMesh was put into the bot. This is automatically used when the bot asks for a Path to a goal which is beyond a certain distance threshold. | ||
+ | \\ |