> For the complete documentation index, see [llms.txt](https://docs.motorica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motorica.com/documentation/style-cloning/how-to-guides/export-motionbuilder-mocap-data.md).
# Export MotionBuilder Mocap Data
## Prerequisites
To follow this guide, first you must have:
1. Brought your mocap data into MotionBuilder
2. Retargeted your animations to the Motorica hierarchy
## Preparation
Before exporting your animation files, it is highly recommended to **plot all animation properties** to the Motorica skeleton. This avoids issues caused by improper interpolation, or keyframes that lie outside the take's play range.
1. Select all bones in the Motorica skeleton by right-clicking on `Root` then `Select Branches` :
2. Open the plotting tool via `Animation > Plot Selected (All Properties)` :
3. Plot your animation with the following settings:
* `Plot On Frame` enabled
* `Plot All Takes` if you have multiple takes in the same file
* A frame rate **of 30, 60 or 120 FPS**
* `Constant Key Reducer` disabled
## Exporting
Now that the animation data has been plotted, we are ready to export. For this, we recommend using **Motion File Export** to ensure you're only sending animation data to Motorica. We must also ensure that each exported file only has **one take** inside it.
1. Select all bones in the Motorica skeleton by right-clicking on `Root` then `Select Branches` :
2. Open the export dialog via `File > Motion File Export` :
3. Choose your folder and name the files as you wish, but ensure it is an `.fbx` or `.bvh` filename:
4. Finally, select all takes you wish to upload to Motorica, with `One Take Per File` enabled:
And you're done! Following these steps will make the style cloning process simpler, preventing technical issues caused by the FBX file format, allowing you to focus on reviewing the quality of your uploaded data.
---
# 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://docs.motorica.com/documentation/style-cloning/how-to-guides/export-motionbuilder-mocap-data.md?ask=&goal=
```
`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.