TouchFrame Puts Quest 3 Controllers on Steam Frame

Digital Citizen (Justin Nelon, October 4, 2026) covers a public MIT-licensed project that puts Meta Quest 3 TOUCH PLUS controllers on Valve’s standalone STEAM FRAME. The repository is kotorvr/TouchFrame on GitHub. Its README pitches first-party behavior — 6DOF, full inputs, HAPTICS, and Touch BINDINGS in SteamVR and OpenXR games — then labels the work IN PROGRESS.

Meta Quest 3 Touch Plus right controller
Meta Quest 3 Touch Plus pads are the hardware TouchFrame TARGETS. Image: Wikimedia Commons.

That GAP between the pitch and the current path is the story. Today’s working milestone is a RELAY, not native Frame-camera TRACKING. A Quest 3 sits on a shelf as radio and TRACKER, streaming controller state to the Frame over Wi-Fi. The Frame-side OpenVR DRIVER — driver_touchframe, built natively on SteamOS aarch64 — presents two oculus_touch devices with Quest 3 render models, hand skeletons, and haptics. Per the project’s install guide, the bridge uses UDP port 28430.

Meta Quest 3 headset
A spare Quest 3 acts as the controllers’ radio and tracker while the Frame runs the SteamVR driver. Image: Wikimedia Commons.

What Valve Already Documents

Valve sells the Steam Frame 1TB Kit with its own controllers — full 6-DOF, gamepad controls, capacitive finger tracking — and does not publish a third-party controller PROGRAM. It does document a binding FALLBACK: SteamVR prefers a Frame Controller binding, then OpenXR Generic, then an Oculus Touch binding remapped to the Frame LAYOUT. TouchFrame rides that fallback, which is why titles such as The Lab can pick up Touch-class INPUT without a custom Frame profile. Valve’s Steamworks controller docs spell out that path.

Steam Frame VR headset marketing still from Valve
The Steam Frame ships with first-party controllers; TouchFrame is an UNOFFICIAL route to Touch Plus hardware. Image: Valve / Steam store.

How Finished It Is, From the Repo

The project’s own feasibility notes (updated October 4, 2026) put the relay milestone as DONE: the SteamVR side is BUILT, live Quest controllers stream to the Frame, and a one-time CALIBRATION aligns spaces. An early real-world calibration run logged roughly 7.6 MM RMS when a Touch pad and a Frame controller were held together. Native radio host mode on an nRF52840 DONGLE is built offline and still needs hardware VALIDATION. Frame-camera 6DoF for Touch-only LEDs remains an open GATE — LED strobes must land inside the Frame’s exposures, and Gate B is not CLOSED.

There are no tagged RELEASES and no packaged INSTALLER. Users clone, build, enable Developer Mode (SSH/ADB), and accept that installing RESTARTS SteamVR. The repo states it ships no Meta or Valve FIRMWARE — research tools read firmware from the user’s own devices or matching official OTAs. A separate PSVR2 Sense driver reported around October 2 still has no public code; TouchFrame’s docs note that gap.

Metaverse Watcher’s takeaway is practical: TouchFrame PROVES SteamVR on the Frame will ACCEPT Quest-class controllers through Valve’s own Touch fallback, but OWNERSHIP of tracking still sits with a second HEADSET until Gate B CLOSES. Watch the GitHub log for dongle validation and LED-blob RESULTS before treating this as a daily driver.

Sources: Digital Citizen (Oct 4, 2026); kotorvr/TouchFrame; FEASIBILITY.md; Valve Steamworks — Steam Frame Controllers; prior MW coverage of the PSVR2 Sense report.

Leave a Comment