OptiTrack NatNet
Overview
Section titled “Overview”Receives Motive rigid-body tracking over NatNet 3.1, 4.0 and 4.1. The interface generates its own pose signals; see Common concepts.
Set up and parameters
Section titled “Set up and parameters”Choose OptiTrack NatNet (tracking) (interface type NatNet) for Motive rigid-body tracking. CONNECT supports NatNet 3.1, 4.0 and 4.1. It exports top-level rigid bodies; skeletons and assets do not become body signals. Configure Motive’s streaming mode and network settings to match the interface.
| Setting | Default | Range and purpose |
|---|---|---|
| ServerAddress | Empty | Motive server’s IPv4 address; required for Auto version discovery and used to filter incoming data to that server |
| CommandPort | 1510 | Server command port, 1–65535 |
| MulticastGroup | 239.255.42.99 | IPv4 multicast address in 224–239; leave empty for unicast |
| DataPort | 1511 | Local UDP data port, 1–65535 |
| LocalInterface | Empty | Local IPv4 address for receiving data and joining multicast; empty uses the OS default |
| BitstreamVersion | Auto | Discover the version from the server, or select 3.1, 4.0 or 4.1 explicitly |
| BodyIds | [1, 2, 3, 4] | Unique Motive rigid-body IDs, in the order in which they become body1, body2, etc. |
| SourceUpAxis | Y | Y or Z; selects the source calibration’s up axis |
| TimeoutMs | 1000 ms | 50–60000 ms without a recognized frame before data is marked stale |
With Auto, enter ServerAddress: CONNECT queries that address at CommandPort for the bitstream version before accepting data. An unknown or unsupported version prevents tracking from starting. A fixed version skips version discovery; it must match the stream. The status details show bitstreamVersion (the resolved version) and versionSource (Auto or the configured fixed version).
For multicast, match Motive’s group and DataPort and select the receiving network adapter through LocalInterface when the PC has several adapters. For unicast, clear MulticastGroup and enter ServerAddress so CONNECT can subscribe and keep the server connection alive; a fixed version still needs this command exchange. The default publish cycle is 10 ms through UpdateCycleMs.
Allow UDP data on DataPort and command traffic to ServerAddress:CommandPort, including replies, through the firewall. Multicast must reach the selected network adapter. If tracking stays in Connecting, check Motive streaming, adapter selection, ports, firewall and version discovery.
Body slots follow BodyIds order, not packet order: [12, 7] publishes Motive ID 12 as <id>.body1 and ID 7 as <id>.body2. Only configured IDs generate pose signals. NatNet does not generate Flystick, button or joystick signals.
Create or import signals
Section titled “Create or import signals”- Manually. Not available: manually entered signals on a tracking interface are ignored and reported as unsupported.
- Browse. No browse: pose signals are generated in BodyIds order.
- File import. No protocol-specific file import.
- A display wall viewport connects the generated pose signals to its slots, for example with Fill from body.
How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.
See also
Section titled “See also”- Common concepts — text signals, direction, write access, tracking signals
- Configuring interfaces — adding signals, direction and write access
- All supported interfaces
- Troubleshooting — connection and signal problems