> For the complete documentation index, see [llms.txt](https://multiset.gitbook.io/multiset/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://multiset.gitbook.io/multiset/multiset-app/simulation-data-capture.md).

# Simulation Data Capture

Simulation data is a short recording of camera frames and sensor data taken at a physical location. Once captured, you can replay it against any of your maps to test localization without standing in the space again, either in the [Developer Portal](/multiset/basics/localization/simulation.md) or in the [Unity Editor](/multiset/unity-sdk/localization-simulation.md).

The MultiSet app is the quickest way to record it, no build required.

### How to Capture Simulation Data

1. **Download the MultiSet App:** Install the MultiSet application on your mobile device.
2. **Start a New Capture:** Open the app and tap the **+** button to begin a new session.
3. **Choose "Simulation Data":** From the options presented, select "Simulation Data." This will open an AR scene using your device's camera.
4. **Position Yourself:** Walk to the physical location where you want to capture the simulation data.
5. **Capture the Data:** Tap the **Capture** button. The app will record simulation data for a few seconds.
6. **Name Your Simulation:** A pop-up will appear after the capture is complete. Give your simulation a descriptive name so you can easily identify it later.
7. **Upload:** Finalize the process by uploading the captured data.
8. **Repeat:** You can repeat this process at every location where you want to capture simulation data for later testing.

<figure><img src="/files/3DcbFnUmsHtUzkgnHU9v" alt="" width="188"><figcaption></figcaption></figure>

### Where Your Captures Go

Captured datasets are tied to your **account**, not to a single map, so anything you record can be run against any of your maps or MapSets. Uploads are available immediately, in two places:

* **Developer Portal:** Open a map or MapSet, choose **Simulation**, and run any dataset against it as a single frame or multi frame query to compare pose accuracy and confidence. See [Simulation](/multiset/basics/localization/simulation.md).
* **Unity Editor:** Use the **SimulationDataManager** component to fetch and download your captures, then localize in Play mode without leaving your desk. See [Localization Simulation](/multiset/unity-sdk/localization-simulation.md).

{% hint style="info" %}
You can also record simulation data from your own Unity build using the **SimulationDataCapture** scene in the MultiSet Unity SDK. See [Build a simulation data capture app](/multiset/unity-sdk/localization-simulation.md#build-a-simulation-data-capture-app).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://multiset.gitbook.io/multiset/multiset-app/simulation-data-capture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.