Unbind Controls in Battlefield: Bad Company 2
Battlefield: Bad Company 2 for the PC is a mess, the shipped product had issues that were pointed out in the Beta, but alas…
Update: I think the only item that needs to be removed to fix the spinning and not being able to move left right, is the mouse look right, left and look up, down. It appears that there is a conflict with the mouse action and the shared joystick command.
My focus here is about removing the Joystick input from game options. I had originally dug through the files in the beta trying enable the throttle and trigger for my Logitek 2.4 wireless joystick, since there is apparently no way to remove (or add some joystick buttons) from the in-game option, I started digging through the input files to add or remove unwanted lines. The problem seems to be caused by the controls being designed for console game pads.
Then when I went to play the retail version, my player would not strafe or turn right or left in vehicles, (and I could type in game using those keys). I was messing with the mouse axis “look left, right” and the “look up, down” I think I switched them and the problem went away, so I was able to play. My clan-mate would go in game and spin in circles uncontrollably, with no joystick ever have been installed on the machine. He was also unable to set or unbind keys in game. This procedure fixed his problem.
They are no longer simple lines like this one from Battlefield 2 “ControlMap.addButtonToTriggerMapping c_PIFire IDFGameController_0 IDButton_0 0 0″ which would point to the joystick trigger button.
This is the section pointing to the pad input “joystick” in the air.dbx file.
<instance guid=”D7E8198E-FAD3-4F50-AE79-8574A4460AC1″ type=”GameSharedResources.InputActionsData”>
<field name=”ConceptIdentifier”>ConceptFire</field>
<array name=”InputActions”>
<item>GUIDC5A60A57-965B-408A-98A9-A38F1A095665</item>
<item>GUID4D787188-5A01-42B6-8888-3898E48F4613</item>
<item>GUID78CFF6B2-E920-43E6-91E5-7714EB651E2B</item>
~ trimmed area pointing to mouse and keyboard~
<instance guid=”78CFF6B2-E920-43E6-91E5-7714EB651E2B” type=”GameSharedResources.PadInputActionData”>
<field name=”IsAnalog”>false</field>
<field name=”NegateValue”>false</field>
<field name=”Axis”>IDA_Undefined</field>
<field name=”NormalizeInput”>false</field>
<field name=”ScaleValue”>1</field>
<field name=”UseSquareInput”>false</field>
<field name=”Button”>IDB_Rdown</field>
<field name=”Pov”>IDP_POV_Undefined</field>
</instance>
Plain english eh?
Okay, so here is a detailed breakdown of removing the joystick options from Battlefield Bad Company 2. Any reference to “pad input,” will mean “joystick.”
First game is not running, locate the BFBC2 folder in your documents, open input folder, you will see four files, air.dbx, infantry.dbx, land.dbx, shared.dbx, (you might not be able to see the .dbx extension of the files). Select the four files, copy and paste to the same folder, this will make a copy of the originals.
This will remove all the joystick bindings from in game so if you still want to use the stick to fly and keys other than the throttle and trigger, that will take more detailed removal of some inputs.
You will repeat this procedure for each of the four files. For these examples I will be using the air.dbx, click file to open, select what to open with, choose to open with notepad, un-check make default for this file type. Starting from the top we will be looking for “<field name=”ConceptIdentifier”>Action</field>,” there will be many in each of the four files. From that we start our search to identify which “<item>GUID” line to remove. In the example above, we see that “<instance guid=”78CFF6B2-E920-43E6-91E5-7714EB651E2B” type=”GameSharedResources.PadInputActionData”>” matches the third item in the “concept identifier” paragraph. Now that we identified which item line refers to pad action, we will delete the line from the “concept identifier” paragraph. If there is three of the item GUID’s you will be removing one. If there is six, you will be removing two, so find both of the items that point to the pad input. Here is pictures of the above file before and after.
The numbers will be different for each install so don’t be looking for ones that match mine. After you have removed all the pad inputs lines from each of the four files, you should be able to start the game and play! (EA, Dice you can contact me to find where to send the check for my emergency fix). Good luck, and don’t forget to make copies of the files before you start!
Let me know if this is not clear enough I might be able to elaborate more on the subject.
Did I mention the annoying part when launched from Steam you get a pop-up, instead of the game launching, oh well must be Valve wanting to be more EA like, (those that have played Battlefield games, know of the multiple clicks, log in, select soldier, select clan tag, select… you get the point).
