ART DTrack
Overview
Section titled “Overview”Receives head and Flystick tracking from ART DTrack over UDP. The interface generates its own signals; see Common concepts for names, timeout behaviour and licence counting.
Set up and parameters
Section titled “Set up and parameters”Choose ART DTrack (tracking) (interface type DTrack) to receive head and Flystick tracking over UDP. Configure DTrack to send its ASCII output to the CONNECT PC’s address and the LocalPort below. The interface generates its signals from the configured counts; Browse and manual signal creation are unavailable.
| Setting | Default | Range and purpose |
|---|---|---|
| LocalPort | 5000 | UDP receive port, 1–65535 |
| LocalBindAddress | 0.0.0.0 | Local IP address; 0.0.0.0 listens on every adapter, 127.0.0.1 accepts local traffic only |
| BodyCount | 4 | 0–32 standard bodies; DTrack ID 0 becomes body1, ID 1 becomes body2, and so on |
| FlystickCount | 1 | 0–8 Flysticks; DTrack ID 0 becomes fly1 |
| ButtonCount | 8 | 0–16 buttons per Flystick, each with a held value and press counter |
| SourceUpAxis | Z | Z for a Z-up source; choose Y when the tracking room is calibrated Y-up |
| TimeoutMs | 1000 ms | 50–60000 ms without a recognized frame before data is marked stale |
Counts and timeout are clamped to these ranges. UpdateCycleMs, shared by CONNECT interfaces, defaults to 10 ms and controls how often the newest received data is published. Button presses are counted for every received packet, including presses between publish cycles.
The supported tracking records are 6d for standard bodies and 6df2 or the older 6df for Flysticks. IDs beyond the configured counts are ignored and reported. Allow inbound UDP to LocalPort through the CONNECT PC’s firewall. If no data arrives, check DTrack’s destination IP and output port, the local bind address and other applications using that port.
See Tracking signals and coordinates for the generated names, timeout behavior and licence counting, and Display Walls for using a body as a head source.
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: the signals are generated from the configured counts.
- File import. No protocol-specific file import.
- A display wall viewport connects the generated signals to its pose and heartbeat slots, for example with Fill from body on the pose group
dtrack.body1.
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