Controller Overview
Unity developers can use the OpenXR Magic Leap 2 Controller Interaction Profile to access the controller's input using Unity's Input system. This profile can be enabled inside your project's OpenXR Settings Window > XR Plugin Manager > OpenXR Settings
To learn about the Magic Leap 2's controller hardware features, see the Controller Features guide.
Input actions contain using 3 callbacks, started, performed, and canceled. While the order and how the events are triggered depend on the type of the action, the table below shows the default behavior.
| Type | Description |
|---|---|
| InputAction.started | When a control is actuated (i.e. moving away from its resting position) |
| InputAction.performed | Called right after started, and continues to be called while the action is being performed. |
| InputAction.canceled | When the control moves back to its default value (i.e. resting position) |
🗃️ Quick Start
1 items
📄️ Input Bindings
Unity's Input System can locate Controls using paths. Bindings on Input Actions utilize this feature to identify the Control(s) they receive input from. You can also use paths to directly look up Controls and Devices, or to have the Input System search for Controls among all devices using the InputSystem.FindControls method.
📄️ Input Device Feature Values
It is recommended that developers read the controller input using Unity's Input System. However, developers can obtain the controller's input directly from the InputDevice. This section provides an example of reading input using the TryGetFeatureValue method and XRCommonUsages features.