SteamVR Tracker Output

Node ID: steamvrTracker · Role: Sink · Realtime config: no

Description

Publishes Optical data over ZMQ for the lpvr_trackers SteamVR driver. Each unique sender_id becomes a generic SteamVR tracker the user can bind to a body part or prop.

Inputs / Outputs

Inputs: Optical
Outputs: (none)

Config aliases

SteamVrTracker, steamvrTracker, steamvr_tracker

Properties

The following fields are exposed in the node’s Properties panel in the UI. Types map to UI widgets (e.g. string → text input, number → numeric, boolean → toggle, select → dropdown, json → JSON editor).

Key	Label	Type	Default	Description / Notes
`endpoint`	ZMQ Endpoint	`string`	`tcp://*:9923`	—

Example node definition

A full node definition in config.json looks like the block below. Paste it under the sinks key of your config, keyed by the node’s instance name (any identifier; it doesn’t have to match the node ID).

{
  "sinks": {
    "steamvrTracker": {
      "inputEndpoints": [
        "inproc://optical_data"
      ],
      "inputDataFilter": [
        "Optical"
      ],
      "settings": {
        "endpoint": "tcp://*:9923"
      }
    }
  }
}

Field reference

Field	Purpose
`inputEndpoints`	List of upstream endpoints this node connects to (`outEndpoint` / `dataEndpoint` values from upstream nodes).
`inputDataFilter`	Optional whitelist of data types. Messages whose type isn’t in the list are dropped at the subscriber.
`settings`	All user-configurable fields — see the Properties table above.

Connections can also be declared at the top-level connections array when settings.explicitConnections is true, as an alternative to filling inputEndpoints on each node.

Loading documentation…