A community project called TouchFrame is putting Quest 3 Touch Plus controllers on a standalone Steam Frame, and the code is public under an MIT licence. What it does not do yet is track those controllers with the Steam Frame’s own cameras.
The project is published on GitHub by a developer who goes by kotorvr. Its README promises Touch Plus controllers working “like first-party controllers: 6DoF, all inputs, haptics, Touch bindings in every SteamVR/OpenXR game” on a standalone Frame.
The very next line reads “Work in progress” in bare type. That gap between the pitch and the state of the code is the whole story here.
What Valve actually supports
Valve sells the headset with its own hardware. The Steam Frame 1TB Kit pairs the headset with Steam Frame Controllers that Valve describes as having full 6-DOF and gamepad controls. The kit also carries the copy of Half-Life: Alyx bundled in when the Frame launched at $1,059.
Valve’s Steamworks documentation says those controllers carry console gamepad capabilities plus touch states, grip buttons, capacitive finger tracking and 6-DOF spatial tracking. Games identify them through the controller type string frame_controller.
Valve publishes nothing about running another company’s VR controllers on the headset. It does, however, document a binding fallback for games.
SteamVR uses a Frame Controller binding by default. If none exists, Valve says it looks for an OpenXR Generic Controller binding, then an Oculus Touch binding, and remaps those to the Frame layout. The mod rides that official fallback, which is also why first-party titles such as The Lab picked up Frame controller support cleanly.
A second headset is doing the tracking
The driver itself is called driver_touchframe, and it is compiled on the headset. It presents two oculus_touch devices to SteamVR with Quest 3 render models, hand skeletons and haptics.
The input, though, arrives over the network. The install guide states that a Quest 3 headset sits on a shelf as the controllers’ radio and tracker, streaming their state to the Frame over Wi-Fi on UDP port 28430.
Haptics travel back the same way. A one-time calibration asks the user to hold a Touch controller and a Frame controller together for about 20 seconds, which the project says lands under 1 cm RMS.
So the Frame is not seeing the Touch controllers. A spare Quest is, and it is relaying what it sees.
How finished this is, by the project’s own grading
The feasibility document puts the work at Phase 0 as of October 3, 2026. It grades the SteamVR side as built, a radio link that works without a Quest as likely, and 6DoF from the Frame’s cameras as uncertain research.
The reason given is that Valve’s closed camera service owns those sensors, and Touch Plus carries only around eight infrared LEDs that strobe on host beacons. The plan even writes in its own failure case: if nothing shows up in the camera frames, the project ships 3DoF instead.
Smaller gaps are listed too. Battery level does not pass through, the finger skeleton is estimated from button and trigger sensors rather than sensed, and the keep-awake watchdog on the Quest does not survive a reboot.
At the time of writing the repository shows 15 commits, no tagged releases and no packaged download. This is a repository to clone and build, not an installer.
The PSVR 2 version is a report, not a download
A separate driver putting PSVR 2 Sense controllers on the Frame, tracked by the headset’s own cameras, was reported around October 2, 2026. No repository, release or author write-up for it could be found, and the TouchFrame documentation that references it notes the code is not public.
Sony lists the Sense controllers as working with PS5 and, through its PC adapter, with Steam on a PC. Meta likewise lists Touch Plus only for its own headsets. Neither mentions Steam Frame.
Trying any of this means turning on Developer Mode, which Valve documents as a settings toggle that enables SSH, ADB and RDP, with a password set in the Developer section. That is the same door sideloading tools already use, and it is not a bootloader unlock.
Valve publishes no warranty warning about Developer Mode, and none should be read into its absence. The practical risks the project names are mundane. Installing restarts SteamVR and interrupts whatever is running in VR. The documentation also warns users off the Frame’s internal controller radio, since reflashing it would break the stock controllers.
None of the mod’s claims have been verified outside the project. Anyone weighing it should also weigh that the headset is still a tightly built piece of hardware, and that a research driver can change shape or stall at any point.
Discussion (0)
Be the first to comment.