Hey guys, I am having a really awkward problem with the xbox wireless controller on the HoloLens for a while now, and I have not heard of other people with the same problem. Running on 2018.2.18f1, without extra plugins, just the native Unity solution. The axes from the trigger input do not always return the correct value. Many times, the input will return as fully pressed (value 1), and get stuck on this number for a while (can be 1s, can be >10m). This happens for both triggers, including the shared axis, although usually the right trigger seems to be the most frequent one. Sometimes the problem fixes by removing batteries on the controller and connecting again, but others the problem will still persist until I restart the application. I have also noticed that the shared axis does not always shows the correct equivalent value of the sum of both triggers (also gets stuck). I have been trying to find a pattern for this problem for quite a while now, and I haven't been able to find a behavior that necessarily causes the problem, although I it seems to be more frequently when I move the controller around (perhaps a bluetooth issue? or could be a random issue and just luck). I was never able to reproduce the problem inside the Unity Editor on Windows, using the same controller and bluetooth connection. I have tried 2 different controllers and 2 different HoloLens running different versions of OS. I have tried using .NET and IL2CPP backends. I have reported this to Unity (#1104486) but have not heard back yet. Has anyone experienced anything similar and found a solution?