Skip to main content
danrossi90
Up and Coming
May 8, 2025

Controller is webXR are not connecting randomly. No inputsourceschange event.

  • May 8, 2025
  • 4 replies
  • 834 views

I have discovered the controllers are taking ages to connect or don't connect at all because of no inputsourcechange event. I get it sometimes but not all the time. If I put the headset down and controller and enable where the controller vibrates I get connection temporarily. 

Here is a few tests

https://threejs.org/examples/webgpu_xr_cubes.html
https://threejs.org/examples/webxr_xr_ballshooter.html

    4 replies

    danrossi90Author
    Up and Coming
    May 8, 2025

    It took a couple of reboots to finally get connected. But eventually it wont get anymore inputsourcechange events. 

    danrossi90Author
    Up and Coming
    May 10, 2025

    Is this the space for bug reporting ? I am seeing too many bugs to report. I am able to replicate reconnection of the controllers. By putting both the controller and headset down while in a webXR session, let the headset go to rest mode. pick headset and controller up and it's activated again.  Refresh the browser go back to an XR session and the controller isnt connected again

    danrossi90Author
    Up and Coming
    May 11, 2025

    The left controller needed a battery and also connected even though I am using the right one. Or else the inputchange event doesn't get dispatched. 

    danrossi90Author
    Up and Coming
    May 13, 2025

    This is still a problem. There is no bug tracker for the oculusbrowser I've tried to report here but I am not sure it's the right place.

    https://github.com/immersive-web/webxr-samples/issues/218

    Both controllers work on the quest home screen. Just not when in a WebXR session. It's intermittent when they connect. It's an issue with not much resources about the problem. 

    Terms & ConditionsAccessibility statement