- Home /
FPS Standard Asset movement when switching to android platform
Hey all, I'm hitting a wall trying to understand whats happening in my project.
I have a scene with a Standard Asset FPSController.prefab. Movement works great in Editor with WSAD, arrows, and gamepads. However, when I switch it over to Android in Build Settings > Switch Platform, I have no more movement in editor. The buttons work perfect on all gamepads, but I have no AXIS movement. not even wsad or arrow keys.
I built it out to an apk and threw it on a droid to test, but even then only the buttons work on the gamepads.
I noticed that if I switch the platform back to PC, movement is no issue and I can control again with WSAD and arrow keys and gamepads. Its really frustrating but none of my searches have turned up anything and when I look over the player controller script it looks like its just using the typical input variables for input, and my input settings have everything right since it works in PC platform.
Any tips?!
Isn't this to be expected, since the vast majority of Android devices do not have keyboards? So, if you're building for Android, why would the WASD keys be mapped to Input Axes?