Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
The navmesh divides the map into walkable polygons ("nav areas").
AI entities (like NextBots) use these areas to calculate paths instead of relying on simple line-of-sight or collision detection.
Without a navmesh, most AI will just stand still, move randomly, or fail to chase properly.
Key points about GMod navmesh:
Generated manually or automatically:
You can generate a navmesh using the console command nav_generate. This scans the map and builds a mesh based on its layout.
Stored in files:
The navmesh is saved as a .nav file alongside the map (e.g., gm_construct.nav).
Editable:
You can tweak it with commands like nav_edit 1, which lets you see and modify the mesh in-game.
Used by NextBots:
Most custom NextBots (like "Sanic," "Obunga," etc.) need a navmesh to function properly, or they’ll just sit there.
Glad I read descriptions.