VR tracking · offline connection planning
Separate pairing, pose and app-assignment evidence
Record observed tracking stages to distinguish receiver ownership, runtime visibility, valid pose and app/coordinate-space issues without automatic hardware diagnosis.
Your setup and observations
For a wireless receiver path, record what has actually been observed using the exact device and app manuals. A paired LED, a listed runtime device, a valid tracked pose and an assigned app role are not interchangeable. A direct wired-USB device is outside this pairing-stage model.
Work through a concrete example
Example: the exact manual confirms the device is paired, but the runtime does not list it. The next evidence is receiver ownership/runtime integration, not station placement. If a valid runtime pose reaches the app but has no assigned body role, use that app’s documented role workflow instead.
A tracking-specific evidence record
The next step is the earliest unresolved stage: supported baseline, pairing/receiver ownership, runtime detection, optical/camera pose, app detection, role assignment or coordinate alignment. It does not diagnose a cable or prove a failed station from a single LED.
Keep unknown observations unknown
The Tool never converts an unknown LED, unobserved pose or unverified shared coordinate space into no/yes. Multiple affected devices prompt a shared-dependency record; one affected device retains an already-working comparison without disrupting it.
App limits are app-specific
VRChat documents runtime roles, supported tracking points and calibration. It is an example, not a universal game limit or guarantee that every headset/tracker combination shares coordinates.
No risky troubleshooting prescriptions
No device access, laser inspection, opening, firmware or driver reinstall, reset, security-disable command, blind re-pairing or calibration math is performed or prescribed. A complete observation chain does not certify accuracy or eliminate intermittent faults.