> For the complete documentation index, see [llms.txt](https://docs.theiamarkerless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theiamarkerless.com/axiom-v2025/theia3d-documentation/data-formats/c3d-files.md).

# C3D Files

Pose (C3D) files can be saved and used to perform post-processing analysis steps in Visual3D software. Use the Save Skeleton Poses button to save skeleton pose C3D files, or navigate to Save Skeleton Poses under the [File Menu](/axiom-v2025/theia3d-documentation/theia3d-batch/file-menu.md). Saved pose C3D files can be opened in Visual3D, and a subject-specific model will automatically be applied to the Theia3D data in Visual3D without requiring the model to be defined.

The movement of each tracked individual is conveyed within the C3D file using ROTATION signals, which are 4x4 pose (position and orientation) matrices for each segment’s local segment coordinate system, for every frame of data. A description of the [ROTATION data type](https://www.wiki.has-motion.com/doku.php?id=visual3d:documentation:c3d_signal_types:rotation_data_type) is available from Visual3D documentation. Raw tracked landmarks are not included as signals in any output files from Theia3D.

{% embed url="<https://youtu.be/bwizkoNdQ_U>" %}


---

# 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.theiamarkerless.com/axiom-v2025/theia3d-documentation/data-formats/c3d-files.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.