getButton("menu") dosen't seem to work

🌵 Needle Engine
1

while other NeedleXRControllerButtonName’s work. “menu” does not seem to work

implemented like so:

    onUpdateXR(args: NeedleXREventArgs): void {
        args.xr.controllers.forEach(c => {
            if (c.getButton("menu")?.isDown === true) {
                if (c.side == this.vrSide || this.vrSide === "any") {
                    console.log("Men button pressed");
                }
            }
        });
    }

the goal is to get the menu button when pressed on Quest with controller or Hands Menu gesture.

image
image759Ă—625 50.4 KB

image
image525Ă—386 24.1 KB

2

Hello!

The issue with the getButton("menu") not functioning correctly while other NeedleXRControllerButtonName buttons do work may stem from specific mapping or input configurations for the “menu” button in your controller layout.

Steps to Debug:

  1. Verify Button Mapping: Ensure that the “menu” button is correctly defined in your controller layout’s mapping. Check the components object to see if the button is included and mapped properly.

  2. Check Input Source: Verify if the input source (e.g., Oculus Quest) supports the “menu” button and is correctly connected. Sometimes, the input source might not be recognized as capable of certain actions.

  3. Test Other Controls: Try using other defined buttons to determine if the issue is isolated to the “menu” button or affecting multiple buttons.

Example Button Check

You might want to implement a simple test to iterate through defined button names and log their state for better debugging. For example:

Object.keys(NeedleXRControllerButtonName).forEach(buttonName => {
    const button = c.getButton(buttonName);
    console.log(`${buttonName}: isDown=${button?.isDown}, pressed=${button?.pressed}`);
});

References

  • Refer to the API documentation to ensure that the “menu” button is supported for your specific hardware setup.
  • Check for any updates or fixes related to this controller or button mappings in the Needle Engine changelogs.

If you continue to face issues, please provide more details about your environment, including:

  • The specific Quest model and firmware version you are using.
  • Any relevant console logs or warnings that may provide additional context.

Feel free to ask if you need more help!

1 replies left - Get a PRO license for more AI replies.
thread_qJy9HBpIelnrAA1RdvhKRoe4
Reply to this message to continue the conversation

3

Hi, thanks we’ll check it.
Until its been added: GetButton is a shorthand to access the gamepad buttons, you can also the xrgamepad directly via the gamepad property to get the menu buttons. Below are the relevant links

For quest controllers the menu button is the last index in the buttons array

4

Thanks.
ill do that temporarily
xrgamepad should certainly work at the last index
but if i understood correctly its a good practice in Needle to use the getGesture/getButton

5

Yes sure, just providing your with the info necessary to unblock :slight_smile:

1 Like
6

Appreciated.

I previously was using the update hook and the standard API.
the onUpdateXR hook is clean, i like it

1 Like
7

@marwie1
now that im thinking about it
lets say for a this.context.xr?.session.addEventListener("squeezestart") for a grip squeeze
is that more process efficient than onUpdateXR hook? or is it about the same?

8

It’s not a big difference.
Although the squeeze event might be invoked at a different point in the frame since the squeeze event is invoked by the browser and might happen between frames and the onUpdateXR event is invoked by needle engine at the same time in the frame

1 Like