> For the complete documentation index, see [llms.txt](https://portalgraphvr.gitbook.io/portalgraph-document-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portalgraphvr.gitbook.io/portalgraph-document-en/developer-documentation/tracker-app-guide.md).

# Tracker App Development Guide

## Overview

Portalgraph applications receive coordinates from the tracker app via OSC (Open Sound Control) communication and display visuals based on those coordinates. The receiving protocol is a subset of the [VirtualMotionTracker API](https://gpsnmeajp.github.io/VirtualMotionTrackerDocument/api/). The default receiving port is **49570**.

**API List** Portalgraph's OSC communication supports the following APIs:

* **/VMT/Room/Unity** `(int)index, (int)enable, (float)timeoffset, (float)x, (float)y, (float)z, (float)qx, (float)qy, (float)qz, (float)qw`\
  Left-handed coordinate system, Quaternion, Room space, similar to Unity (recommended).
* **/VMT/Room/UEuler** `(int)index, (int)enable, (float)timeoffset, (float)x, (float)y, (float)z, (float)rx, (float)ry, (float)rz`\
  Left-handed coordinate system, Euler angles, Room space, similar to Unity (recommended).
* **/VMT/Input/Button** `(int)index, (int)buttonIndex, (float)timeoffset, (int)value`\
  Button input. `value(int)`: 1 = Press, 0 = Release
* **/VMT/Input/Button/Touch** `(int)index, (int)buttonIndex, (float)timeoffset, (int)value`\
  Button touch input. `value(int)`: 1 = Press, 0 = Release
* **/VMT/Input/Trigger** `(int)index, (int)triggerIndex, (float)timeoffset, (float)value`\
  Trigger input. `value(float)`: 0.0 – 1.0
* **/VMT/Input/Trigger/Touch** `(int)index, (int)triggerIndex, (float)timeoffset, (int)value`\
  Trigger touch input. `value(int)`: 1 = Press, 0 = Release
* **/VMT/Input/Trigger/Click** `(int)index, (int)triggerIndex, (float)timeoffset, (int)value`\
  Trigger click input. `value(int)`: 1 = Press, 0 = Release
* **/VMT/Input/Joystick** `(int)index, (int)joystickIndex, (float)timeoffset, (float)x, (float)y`\
  Joystick input. `x, y(float)`: -1.0 – 1.0
* **/VMT/Input/Joystick/Touch** `(int)index, (int)joystickIndex, (float)timeoffset, (int)value`\
  Joystick touch input. `value(int)`: 1 = Press, 0 = Release
* **/VMT/Input/Joystick/Click** `(int)index, (int)joystickIndex, (float)timeoffset, (int)value`\
  Joystick click input. `value(int)`: 1 = Press, 0 = Release

## Registering the App

You can set Portalgraph to automatically launch your custom tracker app.

<figure><img src="/files/KxHl3n1kGAtwYYCrlUvP" alt=""><figcaption></figcaption></figure>

In the settings screen (opened by pressing F12), enter the app’s path in the **Tracker App** field in the bottom-left corner to have it launch automatically on startup.

Alternatively, you can add the app to the dropdown in the bottom-left corner by adding it to the file:\
`(Windows Documents folder)/Portalgraph/portalgraph_user_trackers.json`

Use the following format to register the app in the dropdown.

```
{
  "trackerApps":[
    {
      "name":"Great Tracker",
      "path":"C:/YourGreatTracker.exe"
    }
  ]
}

```


---

# 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://portalgraphvr.gitbook.io/portalgraph-document-en/developer-documentation/tracker-app-guide.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.