Controller Inputs (Trigger, Grip) Unresponsive in WebXR Using Unity XR Interaction Toolkit Demo Scene

[SangeethkumarMahalingam]

I'm working with Unity 2022.2.21f1 and using the XR Interaction Toolkit (XRI) demo scene. I exported my project using the WebXR Exporter and am testing it in the browser with the XR Immersive Emulator.

Everything initializes correctly:

I can see the VR environment.

Headset tracking works.

Both controllers are visible.

However, the controller inputs (such as trigger, grip, and other buttons) are unresponsive — no interaction events are detected.

What I’ve tried:

Verified the WebXR Controller component is added to both controller GameObjects.

Checked the XR Controller settings (Action-based).

Input System package is installed and active.

The WebXR emulator shows controller input is being sent, but Unity doesn’t register it.

Expected behavior:
The XRI Input System should respond to WebXR controller inputs (e.g., ray interactor trigger press, grab, etc.).

Environment:

Unity: 2022.2.21f1

WebXR Exporter: latest version (cloned from GitHub)

Testing browser: Chrome (with WebXR Emulator extension)

Is there an extra step required to map the WebXR controller input to Unity’s Input System/XRI in the browser?

[De-Panther]

There are missing details.
I need to add "help needed" template, but for now use the bugs template, the required info I need to help is there.

Also, the WebXRController component is for legacy Input Manager, not for the new Input System and XRI.
Better look at the WebXR Samples to see what is missing.

[ibytergj]

Hi I was just testing the XRI example from the github web page and I my controllers/hands are not activating in the scene. They work fine in the system environment. Any suggestions on what to check? Quest 3 on Windows 11 Chrome browser - Sorry missed seeing - #430 still seems to be an issue