> For the complete documentation index, see [llms.txt](https://docs.multiset.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.multiset.ai/unity-sdk/ar-foundation/sample-scenes/navigation.md).

# Navigation

The AR navigation sample scene, with points of interest and path finding through Unity NavMesh on the map mesh.

## Navigation

The Navigation Scene provides a template for building an AR navigation app using the MultiSet SDK. This scene includes pre-configured scripts and UI elements to handle Navigation Points of Interest (POIs), and utilizes Unity's NavMesh package for path detection and pathfinding.

Getting Started:

1. Open the Navigation sample scene and install the Unity Navigation package (**com.unity.ai.navigation**)
2. Replace the default Sample Map with your map Go to **Map Space > Delete the sample Map > Add your own Map**
3. Goto **Map Space > NavigationContent > NavMesh** and then Bake the surface to create paths
4. Create and configure POIs (Points of Interest) within your map for user navigation
5. Test your scene using the Editor simulator mode
6. Build and deploy to Android or iOS devices

Check out the tutorial below explaining the process end-to-end

{% embed url="<https://youtu.be/0ecv6fOiAWI>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.multiset.ai/unity-sdk/ar-foundation/sample-scenes/navigation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.