@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?
