I do the same as you, use mouse / keyboard on foot, and my Xbox One controller in vehicles. However, I have not had to unplug the controller to work. I do have to hit a few keys, etc before it does switch back to the mouse / keyboard input. I usually make sure I do so before re-spawning, as it is not a super fluid transition.
Maybe I should try hitting a few more keys before giving up and unplugging the controller. Maybe I get stuck somewhere in the middle of the transition between control methods since the only things I'm able to do with mouse/keyboard is walk/look around? It's not like I have a whole lot of patience when I'm shot at and can't shoot back...
Will try this when I get home, thanks 🙂
@EA_David That's what I usually do with my pad, but I'll be extra careful in the future on that detail.
The weird thing for me is that the game swaps back to the KBM UI, but I'm still stuck with being unable to do anything but walking/looking around with KBM.
The same thing happened for me when I played the beta, with the extra bonus of the controller having the same issues (just being able to walk). I have not tried using the controller when I've run into these errors in the full game, I just unplugged the controller instead.
Just a small update here:
Tried the advice from both of you, unfortunately I'm still stuck with this awkward restricted movement when my controller is plugged in. Oh well, the controller works absolutely great for Figther Squadron... :/
@nobbyallsortsWell, all the controller inputs are put on a separate tab in the keybinding menues from keyboard/mouse and the only thing I've changed is adding some melee and starcard 1 activation on mouse buttons.
I did however find an interesting bug with the controller itself while doing some experimenting with a debugging program for Xbox controllers:
Inputs from all buttons register as signals ranging from 0-1. The standard buttons like A,B,X,Y, RB, LB give completely digital signals, 0 or 1, active or not.
Since the triggers are analog inputs register anywhere between 0 (not pressed) to 1 (fully pressed). Even while my right trigger wasn't pressed it registered as a 0.0023... ish active signal, as if the trigger was always slightly pressed. I guess this slight input from the controller gets registered by the game and gets the game stuck in switching between kb/m and controller modes. Anyone got a way to bypass this that does not involve buying a new controller?
Maybe DICE could put the treshold for registering trigger inputs at a slightly higher value so that the game doesn't keep doing this?
