Search Issue Tracker

Won't Fix



Found in






Issue ID




[WindowMR][HoloLens] Xbox controller isn't detected after connecting controller while app is minimized

Steps to reproduce:
1. Download attached project
2. Build a "Debug" scene for UWP
3. Open Visual Studio solution and build an app
4. Launch app on mixed reality device
5. Test that Motion and Xbox one controllers are working
6. Minimize app
7. Disconnect controllers (remove batteries or disable Bluetooth)
8. Reconnect controllers and test if they are working in MR Portal
9. Maximize the app and test controllers

Expected results: Motion and Xbox one controller inputs are detected.
Actual results: Motion controller inputs are detected Xbox one are not.

Reproduced with: 2019.1.0a12, 2018.3.0f1, 2018.2.20f1, 2017.4.17f1

Notes: After reconecting Xbox controller in 2017.4 and 2018.2 buttons presses are detected, but trigger and joysticks input are not detected.
Reproducible if Xbox one controller is connected via bluethooth.
Bug is reproducible on HoloLens as well.

  1. Response avatar

    Resolution Note (2020.2.X):

    This is a bug within Windows: specifically the WinRT API: Windows.Gaming.Input.Gamepad.
    When the app is minimized, the Gamepad.GamepadAdded event (sometimes) doesn't fire, and Unity isn't notified the controller has been re-enabled.

    The Gamepad API (basically the WinRT version of XInput) is only used for Xbox controllers while all other input controllers are managed through HID. Unfortunately, Xbox controller do not work properly with HID (Left/Right triggers treated as a single axis), and so we have to use this special XInput/Gamepad implementation.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.