sorry for the weird posting but I need to know why when I build for UWP the xbox one controller I am using fails to work. I get it to work in stand alone build but not when I switch to UWP build. Its only when I switch that the support for the controller stops. Any help? (Note: using the standard assets third person controller). Here's a picture of my input manager setup:
To answer your question, UWP uses a completely different API compared to Windows standalone; it implements the WinRT "Windows.Gaming.Input.Gamepad" API whereas standalone uses XInput. As to why it's not working, we'll need some more information: - Can you elaborate on "fails to work"? Are you receiving any input at all, is the controller detected by Unity but not producing input events? - What version of Unity are you using? - Do you know (or can you check) if the controller works with other UWP games (want to eliminate hardware/system issues as the cause)
For the first question, I receive no input at all compared to stand alone. It's only when I change project types from stand alone to UWP does this happen. I am using unity 2018.2.18f1 (edited to reflect the full version number. As far as I know other UWP games work. Give me a free one and I'll try it.
I have edited the version number. Some other notes to mention are: I am using visual studio 2017. I am hoping to do debugging of the uwp game to an xbox one s console. I got it to deploy already but the character does the same idle animation but does not move.
I forgot to add: since last time I posted that a similar error appeared to what happened to this persons unity project after I did the same thing (I was using it over Bluetooth): https://forum.unity.com/threads/a-r...te-of-uwp-in-unity-2018-2-and-2018-3b.585061/ I will update my unity and see if that has anything to do with it.
Nevermind, I found out that mobile input was causing this to not work (it interfered with the keyboard and controller input): https://answers.unity.com/questions/30685/why-is-my-character-not-moving.html
Thanks for the updates. I did some checking with controller functionality for UWP (both wired and Bluetooth) but was unable to find the problem on Windows. I don't have an Xbox One S console readily available. The controller disconnect bug you mention is fixed in 2018.3 but so far hasn't been backported to 2018.2. So, at this point please file a bug so we can continue investigating the issue. Thanks.
Thanks but upgrading unity to 2018.3 and disabling mobile input fixes this. I wish I saw the mobile input earlier though.
I have the same problem in Unity 2019.1.0f2 LWRP 5.7.2. I have two controllers that switch when the character goes from sea to land. When on sea the character uses a physics script that I made, and everything works fine. When he goes to land and uses the standard 3rd person controller that comes with Unity the character idles and the camera look works but the character does not move walk or jump with wasd/space bar. This is happening in the editor. I converted the project from a windows build to a UWP build. The windows build works fine. The UWP build does not work. I tried disabling mobile input in the Mobile Input tab and it didn't have any change. Keys are set up right, because it works in the windows build and because everything works when the physics controller is active (the player is on a layer with a different tag). There are no errors on the console and I'm not sure what to try to fix it from here. Any update to this question would be appreciated.