Question OpenXR Primary2DAxisClick not working

Hi,

I am currently trying to bind primary2DAxisClick with the new Input System.
For testing I use an HTC Vive Pro Eye.
When looking into the documentation https://docs.unity3d.com/Manual/xr_input.html
primary2DAxisClick should be triggered when I click the touchpad of the Vive controller.

However nothing happened when I clicked the touchpad (a bit similar to this thread, but without any errors)
To check if my setup is wrong I tested a few other bindings (see screenshot):

​

The exact paths were:

<XRController>{RightHand}/gripPressed - works
<XRController>{RightHand}/primary2DAxisClick - no event
<XRController>{RightHand}/primary2DAxisTouch - no event
<XRController>{RightHand}/triggerButton - works​

It seems my setup is working (as grip and triggerButton are recognized) but primary2DAxisClick and primary2DAxisTouch seem not to be recognized.
I also looked into the XRInteractionDebugger, here primary2DAxisClick and primary2DAxisTouch change their state accordingly. Which is even more confusing .

​

So in summary for primary2DAxisClick/Touch no event seem to be sent.
Do I maybe need to setup something differently for the primary2dAxisClick binding? Perhaps I am missing something.
Maybe I have used the wrong paths?
Does recently anyone else have encountered the same problem?

---
My Unity version is 2021.1.10f1
XR Interaction Toolkit 1.0.0-pre.4
Device: HTC Vive Pro Eye

This is the script I used for testing the bindings of my InputAction:

Code (CSharp):

1. using UnityEngine;
2. using UnityEngine.InputSystem;
3.  
4. public class DebugOpenXRAction : MonoBehaviour
5. {
6.     public InputActionReference dbgInputActionReference;
7.  
8.     // Start is called before the first frame update
9.     void Start()
10.     {
11.         dbgInputActionReference.action.performed += InputActionPerformed;
12.         dbgInputActionReference.action.started += InputActionStarted;
13.         dbgInputActionReference.action.canceled += InputActionCancel;
14.     }
15.     // Update is called once per frame
16.     void Update()
17.     {
18.         // nothing to do
19.     }
20.  
21.     private void InputActionCancel(InputAction.CallbackContext obj)
22.     {
23.         Debug.Log("dbg InputActionCancel");
24.     }
25.  
26.     private void InputActionStarted(InputAction.CallbackContext obj)
27.     {
28.         Debug.Log("dbg InputActionStarted");
29.     }
30.  
31.     private void InputActionPerformed(InputAction.CallbackContext obj)
32.     {
33.         Debug.Log("dbg InputActionPerformed");
34.     }
35.  
36.  
37. }

 

Thank you, I wasn't aware of this notation difference .
Especially as I only used the GUI for setting up the bindings.
With this adjustment, the events are also sent for Click and Touch.

I initially came to this binding-path (without the curly brackets) over the dropdown menu:

XR Controller > XR Controller (Right Hand) > Optional Controls > primary2DAxisClick

which inserts the binding-path without the mentioned usage notation:

<XRController>{RightHand}/primary2DAxisClick

-> which will not work

Is this a bug? or maybe intentional?

Another thing about the usage syntax is confusing me, as some paths such as for the TriggerButton:

<XRController>{RightHand}/triggerButton

and

<XRController>{RightHand}/{triggerButton}

work fine with and without the usage-syntax.

Which is confusing asTiggerButton is also a usage (such as primary2DAxisClick) but it does work without the usage-syntax.

 

Ah ok thank you, this explains why it is working for some of the bindings.
Then its probably best for now to always check if the gui sets up the correct path (with the {}) for usages (in case there is no alias set).


if it is still of help:

I only have the OpenXR plugin 1.2.2 installed.
(Under XR Plug-in Management also only OpenXR is selected)

XR Controller > XR Controller (Right Hand) > Optional Controls > primary2DAxisClick

=> when selecting over the gui a path without the {} is set.

 

I have set up the

• Eye Gaze,
• HTC Vice Controller
• and Oculus Touch Controller

 

I just noticed, while setting up a new project
for me primary2DAxisClick was only added in the UI after importing the "XR Interaction Toolkit"-Plugin to the project

 

When I use the search function for the bindings:
It also seem to have added 3 bindings (LeftHand, RightHand and Simulated) for primary2DAxisClick and Touch
When I select one of those it is in the notation without the {}.


When I Select the one marked [Any] (which was always there) it is in the correct notation with the {}

 

Thank you for your help , I would have never noticed the error in the binding-path.

I assume the mentioned bug report that I should open is now not needed anymore?

 

Thank you! I was having the same issue, and edited the path to include the curly brackets to get it working.

In case it matters, I am using:
Unity: 2020.3.15f2
XR Interaction Toolkit: 2.0.0

 

This is stilll the case for 2.2.0, so annoying...