The public OhhO-VR project on main is Unity 6000.5.2f1. There is no demo video and no GitHub Release. Works today on this page is only the edit-mode CI run linked below. Open pull requests stay In progress. Everything else is Vision: not built.
No public footage. This slot is empty until a recording exists. It is not a video.
Status
Works today
Edit-mode tests on OhhO-VR main passed in CI at commit 4ebc555 (Unity 6000.5.2f1). The run covers calibration round-trip, drive-spec parsing, control-scheme factory selection, and a FABRIK solver. It is not a headset session, a demo video, or a release.CI
That same commit pins ProjectSettings/ProjectVersion.txt to Unity 6000.5.2f1, changeset eb73d3b415a1. The CI workflow uses that editor version.Code Workflow
Tracker
In progress
OHH-242: Setup, safety, and user-guide docs on branch ohh-242-vr-docs. Open pull request. Not merged. A Public docs workflow on that branch succeeded. That check does not install a headset build.PR Docs CI
OHH-212: Simulate or Drive real session picker on branch ohh-212-session-picker. Open pull request. Not merged. The safety notice on that branch does not add a grip check to the drive loop.PR
OHH-59: Grip deadman and a latched both-grips stop on branch ohh-59-gameci-quest-teleop. Open pull request. Not merged. Main commit 4ebc555 does not contain that gesture. Do not brief an operator to hold a grip to drive unless their build contains it.PR
OHH-205: Windows WSL2 path so a Quest on the LAN can reach rosbridge and MJPEG, on OmniBot branch ohh-205-wsl2-network. Open pull request. Not merged. The VR docs say those steps were not run on a headset while that page was written.PR
OHH-232: Release pipeline on branch ohh-232-release-pipeline. Open pull request. Not merged. No GitHub Release is published.PR
OHH-191: CI APK build on branch ohh-191-vr-ci-apk. Open pull request. Not merged. There is no public APK.PR
OHH-213: AprilTag spike on branch ohh-213-apriltag-spike. Open pull request. Not merged. The detector in that commit returns no detections and is not in the build scene.PR
OHH-197: Arm teleop mux on OhhO-VR branch ohh-197-arm-teleop-mux. Open pull request. Not merged.PR
OHH-197: Arm teleop mux on OmniBot branch ohh-197-arm-teleop-mux. Open pull request. Not merged.PR
OHH-226: Recorder source for VR episodes on OmniBot branch ohh-226-recorder-vr-source. Open pull request. Not merged.PR
OHH-194: Teleop safety changes on OmniBot branch ohh-194-teleop-safety. Open pull request. Not merged. This page does not treat that pull request as a change to the stop on OhhO-VR main.PR
OHH-207: Simulated robot link on OhhO-VR branch ohh-207-simulated-robot-link. Open pull request. Not merged.PR
OHH-211: URDF twin on OhhO-VR branch ohh-211-urdf-twin. Open pull request. Not merged.PR
OHH-192: Quarantine of legacy VR code on OhhO-VR branch ohh-192-quarantine-legacy-vr. Open pull request. Not merged.PR
OHH-192: Retirement of the in-repo VR tree on OmniBot branch ohh-192-retire-omnibot-vr. Open pull request. Not merged.PR
Future
Vision: not built
Cloud sim is not ready. There is no cloud simulator to connect to. Vision: not built.Doc
WebRTC is not the video path a build from main runs. Signaling does not finish, and the WebRTC package is not a dependency. No latency figure is claimed. Vision: not built.Code
Apple Vision Pro and a visionOS client are not in the repository. Vision: not built.Doc
A public demo video does not exist. No release carries footage. The hero slot on this page is a placeholder. Vision: not built.coming with v1.0
Dual-arm humanoid teleop is not a shipped product. A scheme class is in the repository. The edit-mode CI does not drive a humanoid. Vision: not built.Code
Drone teleop is not a shipped product. A scheme class is in the repository. The edit-mode CI does not fly a vehicle. Vision: not built.Code
Underwater-vehicle teleop is not a shipped product. A scheme class is in the repository. The edit-mode CI does not run that vehicle. Vision: not built.Code
A headset build that finds a printed tag on the robot is not built. Vision: not built.Code
A measured video latency is not claimed. Vision: not built.Doc
Docs
Requirements
The VR docs list three requirements: Quest 3/3S, a PC with a GPU or cloud, and a robot. Each row is what those docs support. Cloud is not a working option.
Headset: Quest 3/3S. The VR docs name that pair as the primary target and tell you to enable OpenXR on the Android tab, including Quest support, hand tracking, and passthrough, before you build. In the committed OpenXR settings the Meta Quest Support feature is off, and the Android Hand Tracking Subsystem is off. The device checklist inside that disabled Quest feature includes Quest 3 and Quest 3S. That checklist does not turn the feature on. Developer Mode and a USB cable are required to put a build you make yourself on the headset.Doc Settings
PC with a GPU, or cloud. The documented PC path is a Windows machine running the OmniBot simulator (WSL2 and Docker) on the same LAN as the headset. A GPU compose file is in those docs and was not run for that page.Doc
Cloud is not ready. There is no cloud simulator, no gateway, and no session starter. Use the local PC path.Doc
Robot: a ROSBridge peer on port 9090, or the OmniBot Gazebo sim in place of a physical robot. The headset repository does not contain the robot stack. The real-robot launch lines in the docs were not run for that page.Doc
Setup
Install
These steps are the install procedure in the open docs pull request. There is no released installer. coming with v1.0
1. Install Unity 6000.5.2f1 (changeset eb73d3b415a1) and the Android Build Support module.Doc
2. Open the OhhO-VR repository as a Unity project. The only enabled scene is Assets/scene1.unity.Doc
3. Enable OpenXR on the Android tab, including Quest support, hand tracking, and passthrough.Doc
4. Switch the build target to Android and build Assets/scene1.unity onto the headset. Developer Mode and a USB cable are required.Doc
5. GitHub Releases is where a headset build will be published. The list is empty today.coming with v1.0
Notice
Safety notice
The headset software is not a safety system. For a real robot, a hardware emergency stop that cuts power to the motors must be installed, tested, and within reach of a person who is not wearing the headset before the wheels touch the floor or the arm is enabled.
The headset software is not a safety system. For a real robot, a hardware emergency stop that cuts power to the motors must be installed, tested, and within reach of a person who is not wearing the headset before the wheels touch the floor or the arm is enabled.Doc
On main commit 4ebc555, both grips together publish /emergency_stop true and stop new twist messages. They do not publish a zero twist. Releasing both grips publishes false. There is no latch and no separate reset. Releasing the grips is not safe.Code
No grip is required to publish velocity on that commit. Thumbsticks alone produce /cmd_vel/teleop while the socket is up. A grip-to-drive deadman is under review on OHH-59 and is not in this commit.PR
Do not practice a real-robot stop on the Gazebo sim path in the docs. That launch does not start the base driver that honors /emergency_stop. Killing the launch is the stop for that sim.Doc
Sources
Docs and GitHub release
Guides below are on the open docs branch, not a merged release. The install link is coming with v1.0.