Re: XBox Controller Not Working on PC for Battlefield 2042

@EA_Atic I'm using a scuf impact and my key bindings are completely incorrect and unusable. I also cannot rebind them. Works perfectly on other games.

@EA_AticI got a new generic Xbox controller. Ive gone in and unbound every single button on my controller and it still doesnt work correctly. B and A is looking up and down. Up and down on my right stick is turn left and right. My rb button is weapon swap. 

I've attached a picture of my keybinds. When I click B on my controller the input it takes for the keybind is dpad up for example. A is dpad left and Y is dpad down

@EA_Atic I have done a bit of research on this so far, and from my understanding, there are multiple issues with controllers and or devices such as joysticks, etc.

There are 3 main issues I've seen, the first is where most of an Xbox controller's functions do not work and they are unable to be rebound inside the menu.

The second issue is for PlayStation, where it does not look like the controllers are supported (show's Xbox controls in-game) the button maps are completely scrambled (Circle is escape), and you are stuck looking at the ground or sky and are unable to rebind any of the keybinds in the menu.

The third issue is sometimes extra peripherals can be giving false inputs causing players to spin in circles shooting or cannot controller their character without disconnecting all peripherals. (Don't have much evidence on this issue, only have seen once or twice)

I am personally using a PS5 controller, I was able to use DS4windows, which is a third-party application, for the beta completely fine. I have tried turning it off, using no controller support and running the game through Origin, running the game through Steam and using their controller support, emulating an Xbox controller through DS4windows, using the play config files from the beta for the live game, unplugging everything but my controller, and trying to remap buttons in the game (detects L2 as up on the joystick, and the joystick as a button so its not possible to do).

https://www.reddit.com/r/battlefield2042/comments/qs6ubf/can_not_use_controller_on_pc/ (PS controllers)

https://www.reddit.com/r/battlefield2042/comments/qsdxrz/what_is_wrong_with_controller_on_pc/ (Comments for both PS controllers and Xbox)

https://www.reddit.com/r/battlefield2042/comments/qs6utu/playstation_controller_not_working_on_pc/ (PS controllers)

https://www.reddit.com/r/battlefield2042/comments/qsf69h/controller_on_pc/ (PS controllers)

https://www.reddit.com/r/battlefield2042/comments/qs601u/randomly_looking_to_sky_on_controller/

https://www.reddit.com/r/battlefield2042/comments/qsc9k6/pc_controller_issue/ (Xbox controller)

Made my own thread for posterity but bumping this one up.  

No input whatsoever from my Xbox One controller plugged directly into MOBO.  

I tried toggling "Enable Steam Input" in the controller properties sub menu on the steam page but that just caused a title screen crash.  I tried setting it to "Disable Steam Input" per a reddit suggestion and still wasn't getting input (ofc).  The game only launches with Disable Steam Input or Default toggled in the controller override menu - but with no controller support.

It's absolutely insane to me that this game has released so fundamentally broken.

So far I’ve been able to add origin to steam open origin through steam and launch battlefield and controller works fine. Scuff impact on Bluetooth through steam using ds4 

So I’ve had this issue since the beta as well. Xbox nor PlayStation controllers will work on my desktop. I tried every single solution still will not work. However on my gaming laptop all my controllers worked perfectly fine for battlefield 2042. I have no idea what the issue is

https://www.driverscloud.com/en/services/GetInformationDriver/33440-27296/microsoft-xb1usb1105901405... 

I downloaded this driver and my Xbox One controller is working now.

@EA_Atic

https://www.driverscloud.com/en/services/GetInformationDriver/33440-27296/microsoft-xb1usb1105901405... 

I downloaded this driver and my Xbox One controller is working now.

I have tried it and my xbox one pc controller keeps crashing :-(

@EA_AticI am using an Xbox Controller From the Xbox Accessories App, the controller has the Firmware ver. 2.3.2381.0 it is a Xbox one Controller from 2013. However, it works on BF5 and Call of Duty with no issues. I do have an wireless apdapter, and I have also tried to use the USB hookup method. It acts like its not reading the controller.

Random aim adjustment to either the sky or the ground with Xbox Elite Controller 

@EA_Atic a lot of people including myself are using xbox controllers, mainly series. But a lot of other people are using ps4 controllers. To be honest I think the proble is with all controllers in general to be honest

@EA_Atic

PS4 controller and Microsoft Sidewinder Force Feedback 2 joystick.

During the beta I could get the joystick to work by having got the beta from Steam. It was frustrating that the game would randomly look all the way up or down, a bug that has vanished with launch sans joystick input acceptance.

I bought the Ultimate Edition it via Origin so as to not need to use multiple launchers. However both my PS4 Pro controller and my Microsoft Sidewinder Force Feedback 2 are ignored in game when launched via Origin.

I tried using third party tools called X360 and then Xoutput to make my joystick emulate an Xbox 360 controller. BF 2042 did not recognize their inputs at all. I tried launching Origin through Steam, then using Steam Big Picture, and then Steam Big Picture with Xoutput. The joystick was ignored in all cases. I tried DS4Windows and 'hide DS4' settings as suggested on Reddit but that did not help either. I tried with my PS4 controller plugged in and unplugged.

If I launch Origin from the desktop while Steam is running in the background, the PS4 controller does not work.

There is ONE SOLUTION that I have found - and it only works for the PS4 controller. That is to add Origin into Steam as a shortcut and then launch Origin & BF2042 from within Steam itself. Then, and only then, the PS4 controller is finally recognized within game for key bindings. But still my joystick gets nothing. I went through and thoroughly removed all traces of SCPToolkit and VGem framework which are also used to help emulate controllers, just in case. No dice. Noooo, DICE!

This makes me think I should refund the game on Origin and buy it on Steam, in the hope that my joystick might work like the beta - though it would suck to have the old glitches returning. And I thought you guys wanted our money to go to you more than to Steam!

Is anyone here using Steam to launch BF2042 or is everyone using Origin?

The joystick worked with all previous Battlefield games without me needing to jump through hoops.

PLEASE let us know this is being looked into. While squad play and scoreboards and missing server browser and no ability to ensure I'm playing in my region are all vital features that I really miss, it is my joystick not working with this game which triggers my seeking a refund. I have always flown in these games. Please please please pretty pretty please with icecream and candy and sour nerds on top please tell me this is being worked on and I promise to buy every battlepass it takes to keep the game alive. And it's not just my game, my wife plays too, and our clan - but if I'm out, I'm not the only one who's out.

And I don't want to be out! I want to love this like I've loved every Battlefield. ☹️

Doesn’t even recognize Xbox Elite Series 2. Bluetooth and hardwired.

Alpha Heir's video fix through steam seemed to do the trick.  

Have to go through controller configuration and uncheck the two boxes.  Then when i went in, it almost fully worked but I had to disable raw mouse input in order for it to fully work.  

Still don't get why 2042 requires all these work arounds when Apex.. another EA title IN origin.. has native Dualshock 4 support. 

I’m having a problem where I look straight up randomly I’ve tried ps5 controller an a PS4 controller an I still have the problem is anyone else having this issue?

@EA_Atic I have solved it for now.

SIMPLE ANSWER:

• For now, we have to use Steam edition of BF2042 for joysticks to function, with a specific setting: Steam Input Enabled.
• Origin will only recognize controller if joystick (or similar input device) is unplugged.
• If using Steam, stick with the default bindings in game and map your stick correctly in Steam controller settings instead. You may need to wipe your profile in documents if you've fiddled with it.
• UNTESTED BY ME: You may be able to get joystick and even a HOTAS recognised in Origin if you are using an emulator like x360ce or xoutput and Vgembus along with Hidhide to hide your joystick and only show Origin the emulated 360 controller. 

I disabled Origin In-Game, which may not be relevant since it seems to be force enabled when launching Steam version of BF2042. I tried deleting the Xbox drivers and my PS4 drivers, but my joystick was still not recognized within Origin. I have uninstalled all hidden devices under Device Manager > Sound, Video and Game Controllers and Human Interface Devices, just in case. I uninstalled VirtualMIDI files, virtual xbox controller emulators like x360 and Xouput and SCPToolkit and VGembus, again, just in case.

I have bought and tested the game both via an Origin purchase and the Steam purchase. EA Support said they would be kind enough to refund my Origin purchase if I could get it working via a Steam purchase. That's pretty awesome and allows me to test further. It would be appreciated if I could have temporary testing access on one of the platforms so that I don't need to own it on both since it's not cheap!

SOLUTION A: USING ORIGIN DIRECTLY, YOUR CONTROLLER CAN WORK: Unplug your joystick. The controller will not work at the same time as your joystick. You can then use your controller via Origin, but not your joystick. If this does not work, you have other joystick drivers messing with you. This worked even without me deleting all the various drivers listed above, however, and I did not need to delete or reinstall the Xbox drivers. This worked for my PS4 controller. Obviously my joystick did not work with this method, since it was unplugged.

SOLUTION B, USING STEAM TO LAUNCH ORIGIN'S BF2042, YOUR CONTROLLER CAN WORK: Launch Origin from within Steam itself. This also only works for your PS4 controller, but meant I did not need to unplug my joystick. My joystick did not work with this method.

SOLUTION C, USING STEAM TO LAUNCH STEAM'S BF2042, YOUR JOYSTICK CAN WORK: I have Enabled Steam Input under Steam > BF2042 > Properties > Controller settings. I have defined my joystick layout within Steam as an PS4 controller. The joystick can be saved Xbox 360 Controller within Steam or another type as long as Enable Steam Input is force ticked as mentioned above. Under Steam > Settings > Controller > General, I have ticked both Playstation Configuration Support and Xbox Configuration Support. My PS4 controller is currently both unplugged and uninstalled. MY JOYSTICK INPUTS ARE NOW RECOGNIZED IN-GAME!

I was very happy at this point. However, I still had ongoing issues. The game was temperamental about reading inputs correctly.

---

@Kuiriel wrote:

@EA_Atic I have solved it for now.

SIMPLE ANSWER:

• For now, we have to use Steam edition of BF2042 for joysticks to function, with a specific setting: Steam Input Enabled.
• Origin will only recognize controller if joystick (or similar input device) is unplugged.
• If using Steam, stick with the default bindings in game and map your stick correctly in Steam controller settings instead. You may need to wipe your profile in documents if you've fiddled with it.

I disabled Origin In-Game, which may not be relevant since it seems to be force enabled when launching Steam version of BF2042. I tried deleting the Xbox drivers and my PS4 drivers, but my joystick was still not recognized within Origin. I have uninstalled all hidden devices under Device Manager > Sound, Video and Game Controllers and Human Interface Devices, just in case. I uninstalled VirtualMIDI files, virtual xbox controller emulators like x360 and Xouput and SCPToolkit and VGembus, again, just in case.

I have bought and tested the game both via an Origin purchase and the Steam purchase. EA Support said they would be kind enough to refund my Origin purchase if I could get it working via a Steam purchase. That's pretty awesome and allows me to test further. It would be appreciated if I could have temporary testing access on one of the platforms so that I don't need to own it on both since it's not cheap!

SOLUTION A: USING ORIGIN DIRECTLY, YOUR CONTROLLER CAN WORK: Unplug your joystick. The controller will not work at the same time as your joystick. You can then use your controller via Origin, but not your joystick. If this does not work, you have other joystick drivers messing with you. This worked even without me deleting all the various drivers listed above, however, and I did not need to delete or reinstall the Xbox drivers. This worked for my PS4 controller. Obviously my joystick did not work with this method, since it was unplugged.

SOLUTION B, USING STEAM TO LAUNCH ORIGIN'S BF2042, YOUR CONTROLLER CAN WORK: Launch Origin from within Steam itself. This also only works for your PS4 controller, but meant I did not need to unplug my joystick. My joystick did not work with this method.

SOLUTION C, USING STEAM TO LAUNCH STEAM'S BF2042, YOUR JOYSTICK CAN WORK: I have Enabled Steam Input under Steam > BF2042 > Properties > Controller settings. I have defined my joystick layout within Steam as an PS4 controller. The joystick can be saved Xbox 360 Controller within Steam or another type as long as Enable Steam Input is force ticked as mentioned above. Under Steam > Settings > Controller > General, I have ticked both Playstation Configuration Support and Xbox Configuration Support. My PS4 controller is currently both unplugged and uninstalled. MY JOYSTICK INPUTS ARE NOW RECOGNIZED IN-GAME!

I was very happy at this point. However, I still had ongoing issues. The game was temperamental about reading inputs correctly.

• Throttle goes up but cannot be lowered all the way, as if it ignores half the axis.
• Yaw does not function at the same time as throtttle, and is cancelled for the sake of throttle, as if multiple axis inputs over ride each other instead.
• Yaw left does not function at all, again as if half the axis is being ignored. 
• There was an issue in the beta where view would randomly look all the way up, I'm still testing to see how regularly this occurs.
• When not in a flying vehicle, I was locked to looking down while on foot despite having cleared all inputs for controller on everything besides pilot.

The next stage of joystick solutions was to:

 

• Wipe your PROFSAVE_Profile in your "Documents\Battlefield 2042" folder because the game has issues saving keybindings correctly it seems, leading to above Yaw/Throttle conflict. Unless you know know how to read the various GSTKeyBinding.jet.Concepts instructions!
• Go through all controller settings, make sure all inputs for controller were cleared besides pilot.
• Make sure everything besides pilots in Controller Schemes is marked as 'Custom' so your blanks override the defaults. Beware the CUSTOM crash if you mess with the pilot settings and try to change them both away from custom!
• Use Steam to map your joystick buttons to exactly what they need to be in game, rather than tweaking them in game.

My joystick works now and it's fantastic. :D

---

Wow what a lot of faffing around just to play a game, I will wait until EA fixes the game. If they cant be bothered to fix then I wont bother playing. Life is too short to waste messing around with all those steps listed. Its only a game. Shame on EA for releasing yet another garbage game.

This only works sometimes for me when I launch origin from within Steam

It seems completely random as I sometimes launch on the first try with controller input or not at all.

I have all the settings in play that you mentioned above but it seems completely random. I either get the controller to work on the first couple tries or it takes me an hour of trying to get it to work.

EITHER WAY, this needs to be addressed and fixed because there is no reason for a game to be launched like this. 100% something they need to fix