ALVR Bridge

Node ID: alvr · Role: Filter · Realtime config: no

Description

Bidirectional ZMQ bridge between FusionHub and LPALVR. Sends fused pose to the VR headset, receives IMU data and native tracking pose back.

Inputs / Outputs

Inputs: FusedPose, Optical
Outputs: Imu, FusedPose

Config aliases

alvr, AlvrBridge, alvrBridge

Properties

Each row shows the setting’s label in the node’s Properties panel and, in code, its key in the node’s settings object in the config file. A setting omitted from the config file uses the default shown here.

Property	Type	Default	Description
ALVR IMU Endpoint `imuEndpoint`	string	`tcp://127.0.0.1:8898`	ZMQ endpoint to connect to for receiving IMU data from the ALVR headset.
ALVR Native Pose Endpoint `nativePoseEndpoint`	string	`tcp://127.0.0.1:8899`	ZMQ endpoint to connect to for receiving the headset’s native SLAM pose.
FusedPose Publish Endpoint `poseEndpoint`	string	`tcp://*:8799`	ZMQ endpoint this node binds to publish the FusionHub fused pose back to ALVR.
Left Controller Endpoint `leftControllerEndpoint`	string	`tcp://*:8500`	ZMQ endpoint this node binds for left-controller pose publication.
Right Controller Endpoint `rightControllerEndpoint`	string	`tcp://*:8501`	ZMQ endpoint this node binds for right-controller pose publication.

Example node definition

A minimal entry in config.json looks like the block below. Paste it under the sinks key, keyed by an instance name of your choice. All settings are optional: anything not listed under settings uses the default from the Properties table above. See The configuration file for how the sections and endpoint wiring work.

{
  "sinks": {
    "alvr": {
      "dataEndpoint": "inproc://alvr_data",
      "inputEndpoints": [
        "inproc://fusedPose_data",
        "inproc://optical_data"
      ],
      "inputDataFilter": [
        "FusedPose",
        "Optical"
      ],
      "settings": {}
    }
  }
}

Loading documentation…