VR tracking · offline connection planning

Separate optical tracking, radio slots and app evidence.

Plan optical tracking generations, receiver capacity, base-station sync and paired-versus-tracked observations. Not a room-coverage or compatibility guarantee.

01 · Identify

Optical Tracking Generation Checker

Compare a device’s documented Lighthouse sensor generation with Base Station 1.0 or 2.0, without assuming that SteamVR support means optical compatibility.

Open tool →
02 · Assign

Tracking Receiver Assignment Planner

Plan logical radio assignments within verified classic-compatible and Ultimate receiver pools, keeping reserved channels and unknown capacities explicit.

Open tool →
03 · Plan

Base-Station Sync Planner

Build a logical Lighthouse 1.0 mode or 2.0 channel worksheet, distinguishing optical sync, approved sync cables and duplicate channels.

Open tool →
04 · Resolve

Tracking Evidence Isolator

Record observed tracking stages to distinguish receiver ownership, runtime visibility, valid pose and app/coordinate-space issues without automatic hardware diagnosis.

Open tool →

Different decisions, not one repeated verdict

Optical-generation support, radio receiver resources, station synchronization and observed runtime/app stages have different inputs and different next actions. Buying another USB dongle cannot convert a 1.0-only optical sensor, and a paired LED cannot assign an app body role.

Try an error you can actually resolve

Example: three requested classic-compatible devices and three verified total slots fit when none are reserved. Reserve one of those same three slots for an existing controller and one requested device is short. Five spare Ultimate channels cannot fill that classic-pool shortfall.

Offline planning, explicit limits

No connected-device scan, room/laser coverage estimate, automatic tracking diagnosis or coordinate calibration. SteamVR, VIVE and Tundra names identify the documented systems; this independent site is not affiliated with their manufacturers.