Develop
Touch Plus Controllers
Updated: Sep 4, 2024
Overview
The Touch Plus Controllers have one new input axis: trigger force.
Key Components
New entries
- Oculus Touch (L) Trigger Force: The left controller trigger force event. The Axis Value returns a floating point value, from 0.0 to 1.0, that expresses the amount of force being applied by the user to the trigger after it reaches the end of the range of travel:
- 0 = no additional pressure applied
- 1 = maximum detectable pressure applied.
- This event fires once per frame, when input is enabled for the containing actor.
- Oculus Touch (R) Trigger Force: Same functions as the left controller.
Meta Quest Touch Plus Controllers support index curl and slide from the Meta Quest Touch Pro controllers. For more information, see Controller Input Mapping.
Haptic feedback
Meta Quest Touch Plus Controllers have one haptic actuator in the body of the controller. This actuator is a VCM (Voice Coil Motor) that provides wideband feedback to the palm of the user.
You can use Meta Haptics Studio and Meta Haptics SDK for Unreal to easily design, test and integrate haptics for Touch Plus Controllers.
Note: Touch Plus Controllers do not support localized haptics like the Meta Quest Touch Pro.*
Learn more
To learn more about using controllers in XR applications in Unreal Engine, see the following guides:
Did you find this page helpful?
Virtual reality / Meta Horizon
Support and legal
Virtual reality / Meta Horizon
Support and legal
Virtual reality / Meta Horizon
Support and legal
English (US)
© 2025 Meta