Forum Discussion

ML_916's avatar
10 years ago

Star Wars Battlefront (PC) - Xbox 360 controller issues

I have an Xbox 360 controller plugged in to my PC, it works great to play with in this game but I can't play with keyboard and mouse properly when it's plugged in.

Whenever I try to switch back to keyboard/mouse controls I can't sprint, jump or fire any weapons unless I disconnect the controller which is rather annoying, especially since I prefer to switch back to the 360 controller when I get my hands on a vehicle.

So, how do I solve this without crawling under my desk every two-three minues of gameplay?

10 Replies

  • @ML_916

    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.

  • ML_916's avatar
    ML_916
    10 years ago

    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's avatar
    EA_David
    Icon for Community Admin rankCommunity Admin
    10 years ago

    @ML_916 One thing to check is make sure the pad is placed down on its back so no buttons/sticks at the front are being activated.

    I also swap between control schemes and I just click a few times until the UI swaps to the KBM UI, just like Tony described. 

  • ML_916's avatar
    ML_916
    10 years ago

    @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... :/

  • Anonymous's avatar
    Anonymous
    10 years ago

    hello,

    could you help me. I've plug my xbox 360 controler but i don't manage to play with it. The controler is well detected by my pc (Windows 10) but still not working with star wars battlefront.

    how did you manage to play with yrou controler?

    sorry for my poor English langage but i'm French :-)

    regards,

    Philippe

  • Anonymous's avatar
    Anonymous
    10 years ago
    @ML_916 As silly as this sounds I don't mean it to insult you but have you checked key bindings?
  • Anonymous's avatar
    Anonymous
    10 years ago

    in fact, i've try all the key on the controler but it doesn't work

  • Anonymous's avatar
    Anonymous
    10 years ago

    what are key bindings

  • ML_916's avatar
    ML_916
    10 years ago

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

About Star Wars Games Discussion

Talk with the community about EA's STAR WARS™ games.14,768 PostsLatest Activity: 10 years ago