Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

note for computepath/obstacles #1012

Merged
merged 1 commit into from Nov 16, 2023
Merged

note for computepath/obstacles #1012

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 3 additions & 0 deletions content/features/featuresDeepDive/crowdNavigation/obstacles.md
View file
Open in desktop
Expand Up @@ -40,6 +40,9 @@ const navmeshParameters = {
Note the addition of `tileSize`. It's the world unit size of each tile. If it's not present or has a value a zero, it falls back to the standard use and obstacles won't work.
Also, depending on your use case, this value must be carrefully chosen to trade between too many tiles and too much cpu intensive updates.

**Note :**
The `ComputePath`` method will handle obstacles exclusively when a crowd has been instantiated. Otherwise, the path will adhere to the navmesh without considering obstacles. If your use case involves computing a path with obstacles, agents are optional but a crowd is mandatory.

## Obstacles API

Once the navigation mesh is updated to take tiles into account, obstacles are accessible thru 3 simple functions:
Expand Down