> 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/motive-documentation/overview.md). # Overview Welcome to Motive documentation wiki. \ Motive is a software platform designed to control motion capture systems for various tracking applications. Motive not only allows the user to calibrate and configure the system, but it also provides interfaces for both capturing and processing of 3D data. The captured data can be both recorded or live-streamed to other pipelines. Motive obtains 3D information via Reconstruction, which is the process of compiling multiple 2D images of markers to obtain 3D coordinates. Using 3D coordinates from tracked markers, Motive can obtain 6 Degree of Freedom (3D position and orientation) data for multiple rigid bodies and skeletons, and enable tracking of complex movements in the 3D space. The below workflow pages provide detailed instructions and tips on using Motive for various motion capture applications. \ *Note that skeleton tracking related features are offered only with the Motive:Body license.* *** *** Motive Workflow Pages 1. Installation and Activation 2. Motive Basics 3. Capture Setup (Calibration, Marker Setup, and Synchronization Configurations) 4. Assets (Rigid Body Tracking and Skeleton Tracking) 5. Data Recording 6. Data Types 7. Labeling 8. Data Editing 9. Data Export 10. Data Streaming 11. Motive Batch Processor --- # 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/motive-documentation/overview.md?ask=&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.