> For the complete documentation index, see [llms.txt](https://docs.optitrack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optitrack.com/v1.1/hardware-setup/capture-setup.md).

# Capture Setup

As important as hardware installation is in motion capture systems, it is also important to properly configure the software setup. After you have installed the system, the next step is to get Motive ready for actual capture. The below workflow pages cover essential setup steps when capturing with Motive. There are three main steps: Calibration of the capture volume, placing retroreflective (or active) markers onto subjects, and creating associated assets or models in Motive. If there is an external device connected to the system, synchronization settings need to be configured accordingly.

\
Software Capture Setup Workflow Pages

1. Calibration
2. Marker Setup
3. External Device Sync Configuration


---

# 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.optitrack.com/v1.1/hardware-setup/capture-setup.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.