> 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/data-export/data-export-bvh.md).

# Data Export: BVH

Motive can export tracking data in BioVision Hierarchy (BVH) file format. Exported BVH files do not include individual marker data. Instead, a selected skeleton is exported using hierarchical segment relationships. In a BVH file, the 3D location of a primary skeleton segment (Hips) is exported, and data on subsequent segments are recorded by using joint angles and segment parameters. Only one skeleton is exported for each BVH file, and it contains the fundamental skeleton definition that is required for characterizing the skeleton in other pipelines.

| Option              | Description                                                                                                                                                         |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Units               | Sets the length units to use for exported data.                                                                                                                     |
| Skeleton            | Set this to the name of the skeleton to be exported.                                                                                                                |
| Single Joint Torso  | When this is set to true, there will be only one skeleton segment for the torso. When set to false, there will be extra joints on the torso, above the hip segment. |
| Hands Downward      | Sets the exported skeleton base pose to use hands facing downward.                                                                                                  |
| MotionBuilder Names | Sets the name of each skeletal segment according to the bone naming convention used in MotionBuilder.                                                               |

#### MotionBuilder BVH Naming Conventions and Segments Hierarchy

<figure><img src="https://v110.wiki.optitrack.com/images/thumb/b/b5/DataExport_MobuNaming.png/380px-DataExport_MobuNaming.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://v110.wiki.optitrack.com/images/thumb/7/7e/DataExport_BVH.png/280px-DataExport_BVH.png" alt=""><figcaption></figcaption></figure>


---

# 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/data-export/data-export-bvh.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.