Oculus Touch
More actions
| Oculus Touch | |
|---|---|
| |
| Basic Info | |
| Type | Input Device, Motion Tracker |
| Subtype | Haptics |
| Platform | Oculus Rift (Platform) |
| Developer | Oculus VR |
| Release Date | December 6, 2016 |
| Price | US$199 (pair with sensor, launch price) |
| Website | https://developers.meta.com/vr/documentation/native/pc/dg-input-touch-overview/ |
| Versions | TO-L (left), TO-R (right) |
| Requires | Original Oculus Rift, PC and external Oculus Sensors |
| System | |
| Operating System | Windows (Rift PC software) |
| Tracking | |
| Tracking | 6DoF, optical-inertial |
| Rotational Tracking | Optical tracking and IMU |
| Positional Tracking | External Oculus Sensors (Constellation) |
| Connectivity | |
| Power | One replaceable AA alkaline battery per controller |
| Device | |
| Haptics | Vibration |
| Input | Thumbstick, face buttons, index trigger, grip trigger, capacitive touch sensing |
Introduction
Oculus Touch is a pair of handheld, wireless input devices developed by Oculus VR for the original Oculus Rift (CV1). The left and right controllers are shaped as mirror images, combining conventional game controls with tracked movement and finger-contact sensing. The original retail models are TO-L and TO-R.[1][2]
Touch uses the Rift's Constellation system to track controller position and orientation, while buttons, triggers and touch sensors provide separate input signals. Applications can represent a controller as a virtual hand or an object held in that hand.[3][4] This article describes the original Rift accessory, released on December 6, 2016. Later controllers carrying the Touch name use different tracking arrangements and are distinguished below.[5]
Release and prices
Announcement and launch
Oculus presented a Touch prototype alongside the consumer Rift on June 11, 2015. Half Moon was the prototype's codename, rather than a separate retail product name.[6][1] At Oculus Connect 3, on October 6, 2016, Oculus announced a US$199 price and December 6 shipping date, with preorders opening October 10. The package included the two controllers, an additional Oculus Sensor and a connector for Rock Band VR guitar controllers. The Unspoken and VR Sports Challenge were preorder bonuses.[7]
The December 6 launch added Touch as an accessory to an existing Rift system. Oculus also released software that demonstrated object manipulation, creative work and social gestures.[5]
Price history
These are historical US dollar prices for the specified packages, rather than current offers.
| Date | Package or change | Announced price |
|---|---|---|
| December 6, 2016 | Touch pair, one additional sensor and Rock Band VR connector | US$199[7][5] |
| March 1, 2017 | Touch for existing Rift owners; an additional sensor sold separately | US$99 for Touch; US$59 for the sensor. Rift plus Touch was US$598.[8] |
| July 14, 2017 | New single-box Rift + Touch bundle with two sensors and cables | US$499 regular price; US$399 during the temporary Summer of Rift sale.[9] |
| October 11, 2017 | Rift bundle, including Touch and sensors | US$399, announced as a permanent reduction.[10] |
The July bundle replaced the previous inclusion of an Xbox One controller and Oculus Remote. Oculus continued to permit gamepad-based applications, including a dashboard option described as "Touch (as Gamepad)" for gamepad-only titles.[9]
Features
Oculus described Touch's purpose as bringing "hand presence" to virtual reality: a representation of the user's hands that moves with the controllers and responds to their inputs. Oculus presented this as a design goal.[1][5] The controller design supports several forms of interaction:
- Moving and orienting a virtual hand or tool with a tracked controller.[4]
- Grabbing objects with the grip control and using the index trigger for a separate action.[11]
- Animating pointing and thumbs-up gestures from touch-state signals.[12]
- Providing haptic feedback through vibration and using familiar thumbstick and button controls.[13][14]
Development
In interviews with the design team, Peter Rubin described how hardware prototypes and software experiments developed together. An internal demo called Toybox Zero tested actions such as grabbing, fastening objects with a nail gun and throwing. By the June 2015 Half Moon demonstration, the demo had become Toybox, with activities shared by two people in VR. The team also investigated worn controllers before choosing a handheld design.[15]
Hardware
Traditional controls
Each controller has a thumbstick, two main face buttons, an index trigger and a grip control. The right controller's face buttons are A and B; the left controller's are X and Y. The thumbsticks also register presses.[1][14] The original PC SDK distinguishes the following signals:
| Control | Reported input |
|---|---|
| Face buttons and thumbstick press | Binary pressed/released state |
| Index trigger | Analog value from 0.0 to 1.0; 1.0 means fully pressed |
| Grip control (called the hand trigger in the API) | Analog value from 0.0 to 1.0, commonly mapped to grabbing |
| Thumbstick movement | Horizontal and vertical values from -1.0 to 1.0; the normal API applies a dead zone |
The input structure also provides variants without the dead zone and raw, unfiltered values.[14]
Tracking
The original controllers provide six degrees of freedom: position and orientation. External cameras observe infrared LEDs on the controllers, and the tracking system combines optical observations with inertial measurement unit data. In a 2019 engineering account, Oculus identified 22 tracking LEDs on the original Rift Touch, compared with 15 on the later Quest controller.[16] WIRED's 2016 design history described 24 LEDs, so these source-specific counts should not be treated as an agreed specification.[15]
The tracking ring carries visible-to-camera markers around the hand, but it does not eliminate occlusion. Body position, furniture and sensor placement can block the camera's view. Oculus' Rift guidance advised developers to keep front-facing interactions within the sensors' view and avoid demanding interactions very close to a sensor, near the floor or far overhead.[1][11]
Gesture sensing
Capacitive sensing detects contact with the face buttons, thumbsticks, thumb rests and index triggers. The SDK exposes these as bits in the Touches field, separately from a button press. It also exposes states for an index finger pointing beyond the trigger and a thumb lifted away from the controls.[3][12]
These signals let an application choose or animate hand poses. They do not supply a continuous optical measurement of every finger joint. The original SDK's listed touch states concern the thumb and index finger, while the grip control provides a scalar squeeze value. A displayed whole hand therefore includes animation chosen by the application, rather than a directly measured pose for each finger.[12][14][11]
Ergonomics
The thumb operates the top controls, the index finger rests at the front trigger and the middle finger operates the grip control. Oculus used a diagonal grip intended to leave the thumb and index finger free to move.[1][5] Its developer guidance recommends mapping the grip to grabbing and matching virtual hand position and orientation to the real controller. It also recommends accommodating either dominant hand instead of assuming that every player is right-handed.[11]
Haptics
The original Touch produces vibration. The Rift PC SDK documents simple vibration commands through ovr_SetControllerVibration and a buffered mode that sends a sequence of amplitude samples. For the original Rift, the documented non-buffered modes are 160 Hz and 320 Hz. Buffered playback consumes one byte per sample at 320 Hz, with a maximum 256-byte buffer, equivalent to 0.8 seconds of samples.[13]
The documentation accessed in October 2026 labels buffered haptics deprecated and retained for legacy support, and limits that API to the original Rift with external sensors. It gives different non-buffered frequencies for Rift S. Those distinctions matter when interpreting old Touch examples or comparing later controllers.[13]
Specifications
The following details apply to the original Rift controllers.
| Item | Detail |
|---|---|
| Models | TO-L (left), TO-R (right)[2] |
| Tracking | Six degrees of freedom; external Constellation cameras and inertial data[4][16] |
| Battery | One replaceable AA alkaline battery per controller; the manual specifies 1.5 V[2] |
| Battery-life estimate at launch | Lead electrical engineer Jason Higgins reported up to 30 hours without haptics and about 20 hours with haptics during Oculus Connect 2016. These were manufacturer estimates reported from the presentation.[17] |
| Battery compartment | Removable battery under a magnetic cover; no built-in rechargeable battery[17] |
| Feedback | Vibration, with simple and legacy buffered PC SDK interfaces[13] |
Historical setup and sensor layouts
The original Touch package supplied one sensor in addition to the sensor used with the Rift. A complete Rift-and-Touch installation thus used at least two external sensors; Rift S instead uses headset cameras and cannot use those external sensors.[7][4]
Oculus' January 2017 roomscale guide distinguished these layouts and recommended maximum play areas:
| Configuration | Historical guidance |
|---|---|
| Two sensors for 360-degree tracking | Maximum recommended play area of 5 ft by 5 ft; the guide also describes opposing-corner placement |
| Three sensors for roomscale | Maximum recommended play area of 8 ft by 8 ft; greater overlapping coverage reduces occlusion |
| More than three sensors | Oculus recommended staying with three because extra sensors could introduce technical and performance problems |
These recommendations depended on the room and camera visibility. The guide's April 28, 2017 update states that Oculus app version 1.14 fully supported three-sensor setup for 360-degree tracking.[18]
Sensor count also affected USB bandwidth. The companion guide recommended two sensors in USB 3.0 mode and the third in USB 2.0 mode, explaining that several physical ports may share one host controller. Adding a USB hub does not add host-controller bandwidth.[19]
The manufacturer's manual describes the Oculus Guardian System as a boundary guide. It requires recalibration if sensors move and does not identify every object or overhead obstacle in the play area.[2] These layouts and software instructions document the original Rift system, not a current setup procedure for Quest headsets.
Apps
Bundled titles and introductory experiences
At the December 2016 launch, Oculus made Dead and Buried, Medium and Quill free when setting up new Touch controllers, and introduced Oculus First Contact as a tutorial encounter. Toybox was separately announced as free at Touch launch.[5][20]
| Title | Launch-era role |
|---|---|
| Oculus First Contact | Tutorial introducing Touch and hand presence through a robotic encounter with 1980s sci-fi styling |
| Oculus Medium | Sculpting and sharing 3D objects in VR |
| Quill | Painting in VR |
| Dead and Buried | Wild West target practice and shootouts |
| Toybox | Social playground with activities and virtual gadgets to use with a friend |
The descriptions and offers above are from the original launch announcements.[5][20] Robo Recall, by Epic Games, followed on March 1, 2017 and was announced as free with Touch.[8]
Free with preorder
The Unspoken and VR Sports Challenge were included with Touch preorders. The launch lineup credits The Unspoken to Insomniac Games and VR Sports Challenge to Sanzaru Games.[7][20]
Additional launch titles
Oculus' final launch announcement listed 54 games and experiences for December 6, 2016. Selected entries from that list are shown below.[20]
| Title | Developer credit in the launch list |
|---|---|
| Final Approach | Phaser Lock Interactive |
| I Expect You To Die | Schell Games |
| Job Simulator | Owlchemy Labs |
| Pulsar Arena | Zero Transform |
| Surgeon Simulator: Experience Reality | Bossa Studios |
| Serious Sam VR: The Last Hope | Croteam VR |
| Pro Fishing Challenge VR | Opus |
| Fantastic Contraption | Radial Games and Northway Games |
The same announcement identified Robo Recall, Lone Echo, Arktika.1 and Giant Cop: Justice Above All as titles coming in 2017, rather than December 2016 launch titles.[20]
Developer
The Rift PC SDK provides C++ development interfaces, with Unity and Unreal Engine documentation also available. The PC SDK overview directs Rift developers to the Windows SDK.[21]
In the original API, ovrTrackingState::HandPoses[2] contains controller poses and tracking state. ovr_GetInputState returns button, thumbstick, trigger and capacitive-touch input. The SDK keeps these separate because they come from different systems and times; hand poses are predicted together with the headset pose for a consistent rendering snapshot.[3] Pose data includes position, orientation and their first and second derivatives, in the same coordinate frame as the headset.[4]
Oculus' application guidance calls for virtual hands and controls to animate in response to grabbing, pointing, thumbs-up, button presses and thumbstick movement. It provides Unity and Unreal examples and recommends preserving expected grip-to-grab behavior.[11] The pairing page, last updated July 30, 2024, describes choosing the Rift's Device Setup in the Oculus app and pairing the left controller with Menu and Y held down. This is a dated record of the Rift workflow.[22]
Tracking measurements in research
Shum, Valdés and Van der Loos evaluated a right-hand original Touch controller in a single-session 2019 laboratory study. They used two Oculus Sensors, a Rift, Windows 10 and Unity 2017 in a 2.4 m by 2.4 m area. A jig held the controller at static points near the floor; reference displacements came from graph paper, calipers, measured blocks and a ruler. The analysis averaged 180 samples over two seconds per point, at about 90 Hz.[23]
Table 2 reports a mean displacement error of 3.5 mm (SD 2.0 mm) for a 500.5 mm depth-axis step. The abstract and discussion give an SD of 2.5 mm for this result. The smallest vertical step, 6.23 mm, had a 12.7% mean relative error (SD 9.9%) in Table 1. Average static noise was 0.036 mm. The experiment measured relative displacement, not full finger motion, rotational accuracy or dynamic performance. The authors called for testing across sessions, experimenters and moving conditions, and noted possible floor-level LED occlusion. These results characterize that setup, rather than a universal precision specification or evidence of therapeutic efficacy.[23]
Related Touch generations
Later controllers retained the Touch name but changed the tracking hardware. The original Rift sensor layouts, batteries and haptic interfaces above should be read within their generation.
| Controller | Associated headset | Distinction from original Rift Touch |
|---|---|---|
| Original Touch (2016) | Oculus Rift (CV1) | External Constellation cameras; tracked LED ring; replaceable AA batteries.[2][4] |
| Revised Touch for Quest and Rift S (2019) | Oculus Quest, Oculus Rift S | Headset-mounted cameras observe controller LEDs and combine the observations with inertial data. Rift S needs no external sensors.[16][4] |
| Touch for Quest 2 (2020) | Meta Quest 2 | Revised ergonomics inspired by original Touch. Oculus claimed up to four times the battery life of the first Quest controllers, with performance varying by use.[24] |
| Touch Pro (2022) | Meta Quest Pro | Controllers track themselves with three cameras and a Snapdragon 662 processor per controller. They use rechargeable batteries and a charging dock.[25] |
| Touch Plus (2023) | Meta Quest 3 | Ringless controllers retain infrared markers in the faceplate and base of the handle, rather than Touch Pro's onboard-camera tracking. The SDK exposes a two-stage index trigger and a single body haptic actuator.[26][27] |
Images
References
- ↑ 1.0 1.1 1.2 1.3 1.4 1.5 Ben Lang (2015-06-11). "Oculus Reveals ‘Oculus Touch’ Half Moon Prototype VR Input Controller". Road to VR. https://roadtovr.com/oculus-reveals-oculus-touch-half-moon-prototype-vr-input-controller-breaking/. Retrieved 2026-10-13.
- ↑ 2.0 2.1 2.2 2.3 2.4 Oculus VR. "Oculus Touch Health & Safety and Warranty Guide" (PDF). FCC equipment-authorization exhibit. https://fccid.io/2AGOZTO-R/User-Manual/User-Manual-3153840.pdf. Retrieved 2026-10-13.
- ↑ 3.0 3.1 3.2 Meta. "Controller Data". Meta Horizon OS Developers. https://developers.meta.com/vr/documentation/native/pc/dg-input-touch/. Retrieved 2026-10-13.
- ↑ 4.0 4.1 4.2 4.3 4.4 4.5 4.6 Meta. "Controller Tracking". Meta Horizon OS Developers. https://developers.meta.com/vr/documentation/native/pc/dg-input-touch-poses/. Retrieved 2026-10-13.
- ↑ 5.0 5.1 5.2 5.3 5.4 5.5 5.6 Oculus VR (2016-12-06). "Oculus Touch Launches Today!". Meta Quest Blog. https://www.meta.com/blog/oculus-touch-launches-today/. Retrieved 2026-10-13.
- ↑ Oculus (2015-06-11). "Introducing the Oculus Rift". Meta Newsroom. https://about.fb.com/news/2015/06/introducing-the-oculus-rift/. Retrieved 2026-10-13.
- ↑ 7.0 7.1 7.2 7.3 Oculus (2016-10-06). "Oculus Reveals Touch Launch Details and Unveils Santa Cruz Prototype at Oculus Connect 3". Meta Newsroom. https://about.fb.com/news/2016/10/oculus-reveals-touch-launch-details-and-unveils-santa-cruz-prototype-at-oculus-connect-3/. Retrieved 2026-10-13.
- ↑ 8.0 8.1 Nate Mitchell (2017-03-01). "Introducing Rift + Touch for $598—Plus ‘Robo Recall’ Is Now Available!". Meta Quest Blog. https://www.meta.com/blog/introducing-rift-touch-for-598plus-robo-recall-is-now-available/. Retrieved 2026-10-13.
- ↑ 9.0 9.1 Oculus VR (2017-07-14). "New Hardware Bundle Now Available". Meta Horizon OS Developers. https://developers.meta.com/vr/blog/new-hardware-bundle-now-available/. Retrieved 2026-10-13.
- ↑ Oculus VR (2017-10-11). "The Best VR Experience at the Most Affordable Price: Rift Bundle Now $399". Meta Quest Blog. https://www.meta.com/es-es/blog/the-best-vr-experience-at-the-most-affordable-price-rift-bundle-now-399/. Retrieved 2026-10-13.
- ↑ 11.0 11.1 11.2 11.3 11.4 Meta. "Rift Touch Controllers". Meta Horizon OS Developers. https://developers.meta.com/vr/documentation/native/pc/dg-input-touch-overview/. Retrieved 2026-10-13.
- ↑ 12.0 12.1 12.2 Meta. "Button Touch State". Meta Horizon OS Developers. https://developers.meta.com/vr/documentation/native/pc/dg-input-touch-touch/. Retrieved 2026-10-13.
- ↑ 13.0 13.1 13.2 13.3 Meta. "Haptic Feedback". Meta Horizon OS Developers. https://developers.meta.com/vr/documentation/native/pc/dg-input-touch-haptic/. Retrieved 2026-10-13.
- ↑ 15.0 15.1 Peter Rubin (2016-12-06). "Inside Oculus' Quest to Design an Invisible VR Controller". WIRED. https://www.wired.com/2016/12/oculus-touch-design/. Retrieved 2026-10-13.
- ↑ 16.0 16.1 16.2 Andrew Melim (2019-09-20). "Increasing Fidelity with Constellation-Tracked Controllers". Meta Horizon OS Developers. https://developers.meta.com/vr/blog/increasing-fidelity-with-constellation-tracked-controllers/. Retrieved 2026-10-13.
- ↑ 17.0 17.1 Ben Lang (2016-10-07). "Final Touch Battery Life Improved 40% Over Original Prototype, Up to 30 Hours of Use". Road to VR. https://roadtovr.com/oculus-touch-battery-life-confirmed-40-percent-improvement-over-half-moon-prototype/. Retrieved 2026-10-13.
- ↑ Oculus VR (2017-01-25). "Oculus Roomscale—Tips for Setting Up a Killer VR Room". Meta Quest Blog. https://www.meta.com/blog/oculus-roomscale-tips-for-setting-up-a-killer-vr-room/. Retrieved 2026-10-13.
- ↑ Oculus VR (2017-01-26). "Oculus Roomscale: Balancing Bandwidth on USB". Meta Quest Blog. https://www.meta.com/en-gb/blog/oculus-roomscale-balancing-bandwidth-on-usb/. Retrieved 2026-10-13.
- ↑ 20.0 20.1 20.2 20.3 20.4 Oculus VR (2016-11-30). "Introducing the Oculus Touch Launch Lineup: Over 50 New Rift Titles Coming December 6". Meta Quest Blog. https://www.meta.com/es-es/blog/touch-launch-lineup/. Retrieved 2026-10-13.
- ↑ Meta. "PC SDK". Meta Horizon OS Developers. https://developers.meta.com/vr/documentation/native/pc/pcsdk-intro/. Retrieved 2026-10-13.
- ↑ Meta (2024-07-30). "Pairing the Rift Touch Controllers". Meta Horizon OS Developers. https://developers.meta.com/vr/documentation/native/pc/pairing-touch-controllers/. Retrieved 2026-10-13.
- ↑ 23.0 23.1 Shum, Leia C; Valdés, Bulmaro A; Van der Loos, HF Machiel (2019-06-06). "Determining the Accuracy of Oculus Touch Controllers for Motor Rehabilitation Applications Using Quantifiable Upper Limb Kinematics: Validation Study". JMIR Biomedical Engineering 4 (1): e12291. doi:10.2196/12291. Retrieved 2026-10-13.
- ↑ Oculus (2020-09-16). "Introducing Oculus Quest 2, the Next Generation of All-in-One VR". Meta Newsroom. https://about.fb.com/news/2020/09/introducing-oculus-quest-2-the-next-generation-of-all-in-one-vr/. Retrieved 2026-10-13.
- ↑ Meta (2022). "Meta Quest Pro and Meta Quest Touch Pro Controllers Tech Specs" (PDF). Meta product sheet, hosted by Seton Hall University. https://www.shu.edu/documents/meta-quest-pro-specs.pdf. Retrieved 2026-10-13.
- ↑ Ben Lang (2023-09-29). "Quest 3 Brings a Big Change to Controller Tracking Coverage". Road to VR. https://roadtovr.com/quest-3-touch-plus-tracking-coverage/. Retrieved 2026-10-13.
- ↑ Meta. "Meta Quest Touch Plus Controllers". Meta Horizon OS Developers. https://developers.meta.com/vr/documentation/native/pc/native-touch-plus-controllers/. Retrieved 2026-10-13.