OptiTrack source
The OptiTrack source receives the pose of one rigid body from OptiTrack Motive over NatNet (UDP unicast, port 1510 for commands and 1511 for data, Motive's defaults). Motive's settings: CinePuck tutorial, step 1.
Supported versions
| Motive |
NatNet |
RigFX |
| 3.0 to 3.5 |
4.0 to 4.5 |
Supported, tested with Motive 3.5.1. Motive 3.5 needs firmware 1.13 or later |
| 2.x |
3.0, 3.1 |
Same data format as NatNet 4.0, not tested |
| 1.x |
2.x |
Not supported |
- Motive must stream in Unicast: Multicast is not supported (Network).
- Other applications can receive the same Motive at the same time (eZtrack, a game engine…). An application can ask Motive for a given NatNet version, which can change what Motive sends to the others: RigFX reads every version and never asks for one, so it does not change what the other applications receive.
What it publishes
| Channel type |
Source channel |
Where to bind it |
| 3D pose |
source/optitrack/pose |
A node on the Rig page, usually the tracked camera body |
Each axis is also offered on its own (source/optitrack/pose/x … /roll), to bind one of them to any field of a node.
The pose is the rigid body's position (metres) and orientation, relative to Motive's origin, converted from Motive's axes (Y up) to RigFX's axis convention (Z up):
| Motive |
RigFX |
| +Z, forward |
+Y, front |
| +Y, up |
+Z, up |
| +X, left |
−X (RigFX +X is right) |

Motive's origin is the zero of the studio, and the rigid body reads pan, tilt and roll 0 when its orientation matches Motive's axes: create it with the camera level and looking along Motive's +Z, or reset its orientation that way.
Source card
| Field |
What it does |
| Status |
LED + label, see Status states. |
| Server IP |
The Motive PC's address: its Local Interface in Motive's streaming settings. |
| Rigid Body ID |
The rigid body's Streaming ID in Motive (Assets → Rigid Body Properties), 1–9999. |
| Enable |
Turns the source on and off. |
| Mode (under Advanced) |
Latest: the last packet before the sync pulse. Subframe: one chosen packet of each frame, when Motive runs at a multiple of the frame rate (240 Hz for a 60 Hz output, for example). |
| Multiplier (under Advanced) |
Subframe mode: Motive's Camera Rate Multiplier, or the eSync 2's Input Multiplier (1–16). |
| Subframe (under Advanced) |
Subframe mode: which packet of each frame to use, 0 to Multiplier − 1. Pick the one that arrives just before the PHASE marker in the Phase View. |
| Timing |
When the source is enabled: the packet rate and when packets arrive after the sync pulse. Phase view › opens the Phase View. |
Status states
| LED |
Label |
Meaning |
| Off |
Disabled |
The Enable toggle is off. |
| Off |
Not Connected |
Enabled, but Motive doesn't answer: wrong Server IP, Motive not streaming, or a firewall. RigFX keeps trying. |
| Amber |
No rigid body with ID N in stream |
Motive streams, but not this ID. |
| Amber |
Rigid body N not tracked (occluded or inactive) |
Motive lost the rigid body: markers hidden from the cameras, or the asset deactivated. |
| Amber |
No Rigid Body |
Connected, waiting for the rigid body's first data. |
| Green |
Tracking |
The rigid body is tracked. |
Network
- RigFX and the Motive PC on the same network (Network).
- Motive streams in Unicast (Edit → Settings → Streaming; multicast is not supported), with Local Interface set to the Motive PC's address on the studio network.
- UDP 1510 and 1511 open in the Motive PC's firewall.
Troubleshooting
Status stays at Not Connected
- The Server IP must be the Local Interface set in Motive's streaming settings.
- In Motive, Stream Rigid Bodies must be on and Transmission Type set to Unicast.
- Allow Motive through the Windows firewall on the studio network. RigFX reconnects by itself.
Status shows No rigid body with ID N in stream
- The Rigid Body ID must be the Streaming ID of the asset in Motive, not its row number or its name.
- With Motive 3.5, update RigFX to firmware 1.13 or later: earlier firmware does not read the data Motive 3.5 sends, and never finds the rigid body although Motive tracks it (Supported versions).
Status shows Rigid body N not tracked
- Check that enough markers are visible to the cameras in Motive's live view.
- Check that the asset is active in Motive (not greyed out in the Assets panel).