Develop

Meta Quest Touch Plus Controllers

Updated: Apr 14, 2026

Overview

The Meta Quest Touch Plus Controllers have one new input axis: trigger force.

Key Components

Trigger force

  • 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 when the trigger force value changes, not every frame. The runtime performs a delta check and only reports the event when the current value differs from the previous state.
  • Oculus Touch (R) Trigger Force: Provides the same trigger force event 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 Haptics Studio and Haptics SDK for Unreal to design, test, and integrate haptics for Touch Plus Controllers.
Note: Meta Quest Touch Plus Controllers do not support localized haptics like the Meta Quest Touch Pro controllers.

Learn more

To learn more about using controllers in XR applications in Unreal Engine, see the following guides: