# Outputs

In this section we go over the motion capture outputs that Kinoca can be configured to work with.

## UDP

Send mocap data to a UDP port. Each UDP packet is a mocap frame in JSON format. The JSON schema can be downloaded {download}`here <../_static/kinoca-frame.schema.json>`.

A frame without inverse kinematics contains the 3D keypoints, in meters:

```json
{
  "version": "1.0.0",
  "timestamp_us": 1728467000000000,
  "frame": 42,
  "features": {
    "nose": [0.02, 1.61, 0.13],
    "left_shoulder": [0.18, 1.42, 0.05]
  }
}
```

When a 3D model is set up for inverse kinematics, `features` is replaced by `bones`, which contains the model-space 4x4 transform of each bone as an array of rows.

```{jsonschema} ../_static/kinoca-frame.schema.json
:lift_definitions:
:auto_reference:
```

## File dump

Dump the mocap frames to a file on disk. Uses the same format as UDP, with one frame per line.

## VMC protocol

This enables Kinoca to be compatible with all kinds of VR software, such as EVMC4U, Warudo and Animaze.