Resolved Accessing menuButton on Oculus Quest 2

Hey!

I'm building a game for Oculus Quest 2, I'm using the new input system and the Grip and Trigger are working great.

Now I'm trying to access the menuButton on the left controller with no luck.

That's the schema





and the code for PauseMenu

Code (CSharp):

1. using UnityEngine;
2. using UnityEngine.InputSystem;
3.  
4. namespace Game
5. {
6.     public class PauseMenu : MonoBehaviour
7.     {
8.         [SerializeField] private InputActionReference menuInputActionReference;
9.  
10.         private void OnEnable()
11.         {
12.             menuInputActionReference.action.started += MenuPressed;
13.         }
14.  
15.         private void OnDisable()
16.         {
17.             menuInputActionReference.action.started -= MenuPressed;
18.  
19.         }
20.  
21.         private void MenuPressed(InputAction.CallbackContext context)
22.         {
23.             Debug.Log("MenuPressed!");
24.         }
25.     }
26. }

The log message "MenuPressed" never appears, am I doing something wrong?

I'm using XR Interaction Toolkit Version 1.0.0-pre.3

Thanks!

 

Try using "start" instead of "menuButton", in the Input system.

 

Thanks! it worked!

 

I've tried this same set up but am unable to get the menuButton to work on the Quest 2. It runs fine through PCVR but when I build it's not recognizing the menu button. I've tried both menuButton and Start but no luck, any ideas?

 

Could you elaborate on how you're checking the device? New Input has a lot of ways to do it.

 

Sorry for late reply, my notifications were off. I made a new action for XRI Left Hand called Toggle. It's checking for menuButton[LeftHand XR Controller] (this one only works on PCVR not when it's built on Quest) and then I have secondaryButton [LeftHand XR Controller] (this is my temp solution until I get the menu button to work).

I hope that makes sense

 

I'll have to double check, I swear I did. Have you tried this on a build for the Quest standalone?

 

I'm not sure why but I am not seeing that option here. Even when I go through all of the XR Controller Left Hand options, I don't see one that says Start. Are you on the most up to date version?

 

Still no luck on this one I'm on all control schemes and don't see the option sadly

 

Same same here, I have assigned trigger button and it works, but when assigning menu or menuButton or both together, still cant display menu.

 

If anyone struggles with this, the quick search does not show all 'start' binding paths.



But if you step by manually you can find the option.



The 'start' binding works. It was tested on Quest1 android build. I use the Unity 2021.3.1f1 with these XR packages:

 

Weird I followed your video and didn't see it but I'm also on 2020.3.16 so maybe that's why

 

I'm not him but I can't find the Start either.

I'm on Unity 2020.3.30f1 and these are the packages being used


and these are my interaction profiles


PS: I forgot to mention but I'm testing using Vive Focus with HTC Stream mode (runs on pc, streams on headset), but the issue with the Menu button is the same I believe.

 

@andersoncc this binding isn't working. I'm also having this issue. 2021.2.18f1

OpenXR version is 1.3.1, I am testing on an Oculus Quest 2. (Not Oculus Link)

I've tried Oculus Touch Controller Menu, OculusTouchController Left Menu, XRController Left Hand Menu, XRController Left Hand MenuButton, XRController Menu, XRController MenuButton, and I don't have Start button in any menus, even when not using quick search. This code below works if I change the button to the trigger:

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.InputSystem;

public class MenuToggle : MonoBehaviour
{
[SerializeField] InputActionAsset inputActions;
InputAction menuToggle;
bool menuActive;
[SerializeField] GameObject menuPanel;

// Start is called before the first frame update
private void Start()
{
var inputActionMap = inputActions.FindActionMap("XRI LeftHand Interaction");
menuToggle = inputActionMap.FindAction("Menu Toggle");
menuToggle.performed += ToggleMenu;
menuToggle.Enable();
}

public void ToggleMenu(InputAction.CallbackContext context)
{
if (menuActive)
{
menuActive = false;
menuPanel.SetActive(false);
}
else
{
menuActive = true;
menuPanel.SetActive(true);
}
}
}

 

Updated my OpenXRPlugin to 1.3.1 and was able to find the "start" option in my binding path. Cheers!

Just want to mention, using the "start" binding works in builds for Quest 2, however not in Editor. So i'd say just keep the original binding for "menuButton" for use in Editor alongside your "start" binding.

 

Just an FYI, if you are pasting "<XRController>{LeftHand}/start" as a binding, make sure you hit enter so it takes it

 

HI, i am facing same issue using unity 2021.3.8f1/ xr interaction toolkit 2.1.1, I cant see Start option for Xr controller or oculus controller for left hand.. i have attached my screenshot for reference please help..

 

@andersoncc Thanks! Not selecting Oculus Quest support was exactly the problem for me. I found other suggestions online, like upgrading to the latest version of OpenXR (already on it), or using 'Start' instead of 'menu'. None of these were valid options. Its a bit hard to diagnose as you need Oculus Quest for this button, but all the other buttons seem to work fine without enabling Oculus Quest support.

 

Hi,
this solution worked for me:
As others I couldn't find the "start" binding. The bindings menu, home, app, system, etc. didnt work. I then clicked the "T" symbol besides the binding to manually paste"<XRController>{LeftHand}/start" there and hit enter.

This worked.

Additionally you can add this to comply with meta quest guidelines to pause when opening the oculus dash:

private void OnApplicationFocus(bool focus)
{
#if !UNITY_EDITOR
if (isPaused)
return;
if (focus)
return;
isPaused = true;

PauseGame(); //Your code here

#endif
}

 

Hi! Again.
Recently, I updated the Unity editor to 2021.3.24f1 and it was the only solution that worked for me too on Quest 2. Thank you.
I use these packages:

 

Has anyone figured out why some people are able to access the "Start" binding and other are not? That seems pretty odd. I for one do not see it listed.