Re: XBox Controller Not Working on PC for Battlefield 2042

@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