I'm considering pre-ordering as I have for past Battlefield games but wanted to know more about any details regarding support for joysticks. I find flying with them is much better but support for the...
Product: Battlefield 2042 Platform:PC Please specify your platform model.PC AMD or Nvidia Model NumberMS-7C37 Enter RAM memory size in GB32GB Are you using any software with an overlay?Yes If yes, can you list them here?Geforce Experience If you disable this software, does that have any effect?No Which part of the game is the issue happening in?Multiplayer Which part of the mode?Conquest Please select your regionEurope On which server did this happen? When did this happen? (dd.mm.yy hh:mm) Summarize your bugThe Logitech Extreme 3D HOTAS controller is not recognized by the game as a flight stick. How often does the bug occur?Every time (100%) Steps: How can we find the bug ourselves?Attach the Logitech Extreme 3D HOTAS controller and try using it. What happens when the bug occurs?The game does not recognize input. What should be happening instead?The game should recognize input as it has with ALL modern Battlefields that came before ....
The Logitech Extreme 3D HOTAS controller is not recognized by the game as a flight stick.
released a game for pc with console controls proper lame if you ask me, if we wanted to play console we would of purchased that format, get this sorted ASAP.
Looks like the the game recognizes whatever xinput device is connected to Device ID 0, and assumes it's an Xbox controller.
You can install vJoy, and map each axis and buttons on your HOTAS devices to individual axes and buttons on a virtual vJoy device.
For reference, here is how the game expects to see the mapping:
Left Stick X Axis = vJoy X axis Left Stick Y Axis = vJoy Y axis Right Stick X Axis = vJoy Z axis Right Stick Y Axis = vJoy X Rotation Axis (rx) D-Pad Left = vJoy button 0 D-Pad Up = vJoy button 1 D-Pad right = vJoy button 2 D-Pad down = vJoy button 3 X button = vJoy button 4 Y button = vJoy button 5 B button = vJoy button 6 A button = vJoy button 7 Back button = vJoy button 8 Start button = vJoy button 9 Left Bumper = vJoy button 10 Right Bumper = vJoy button 11 Left Trigger = vJoy button 12 Right Trigger = vJoy button 13 Left Stick Pushed Down = vJoy button 14 Right Stick Pushed Down = vJoy button 15
Also, if you have additional xinput devices connected, the game gets confused. To workaround this, you need to show only a single device when the game starts. You can use a utility called HidHide to selectively hide devices when you start the game. You have to make sure that only the vJoy device shows in the Windows Game Controllers when BF 2042 starts. After the game starts, you can un-hide them back.
In order to do this, you will need the following software:
Here is how the devices should look like before starting the game (only vJoy should show)
Here is an example of using UCR to map from from a physical joystick X and Y axes, to the vJoy virtual device X and Y axes. This mapping will be seen by the game as the Controller's Left Stick X and Y axis respectively.
Finally, for all of this to work, the you will need to set the game Controller Schemes to "Custom"
@1i1il1 I used three different 3rd party to map my Logitech 3d Pro. but still it wasn't a fluent experience. (mouse mapping that didn't work any more when using joytokey) (No trottle when used Xbox emulator and another mapping program.)
I almost got so mad that wanted to throw my joystick out of the window. waisted 3 hours of figuring this * out.
And thinking that maybe EA will ban us for using these mapping programs and not really working like I want it to work.
I gave up and I am still waiting for a solution from DICE / EA
@1i1il1Your post that the game is looking for first connected device and presuming it's a controller was helpful. It turns out the game is not mapping joysticks to controllers when it presumes that the joystick IS the controller, so you have to map the joystick under custom controller instead of under joystick remappings. This means losing out on most buttons etc.
But more frustrating is that it looks like the game can see right through HidHide and completely ignores Vjoy if you're trying to combine your sticks.
This is weird because just a month ago I was using my Force Feedback 2 as a 'joystick' and the Thrustmaster 16000 as a 'joystick' and I didn't have to jump through all these hoops. Now I'm using VKB - an upgrade - and the game supports it less? It's bizarre.