Controllers

Learning objectives

1. Understand how to configure your joystick
2. Understand how to configure your HOTAS
3. Understand how to configure your head tracking device

Setting up controls

Buttons

Controls you absolutely need to know, and (as far as possible) should bind to your joystick:

Function	Default (from BMS.key)
Trigger (Cannon)	"/" on english keyboards, "-" on most other european keyboards
Pickle (Fire missiles/bombs)	Space
TMS Up	Ctrl+Up arrow
TMS Down	Ctrl+Down arrow
DMS Down	Ctrl+Alt+Down arrow
Cursor slew	Arrow keys
Run countermeasure program	Z or X
Comm 1 and 2 transmit	Alt+1 and Alt+2
Wheel brakes	K
Nose wheel steering	Shift+/ or Shift+- (same difference as Trigger)
Gear up/down	G
Speed brakes out/in	B
Dogfight mode enable/cancel	D and C
Antenna tilt down/up	F5 and F7. F6 centers.

Binding to joystick can be done via profiling software, or via in-game/DirectX assignments. See this thread.

Axes

Beyond the normal pitch, roll, throttle, and rudder axes, if your joystick has extra wheels or sliders, it’s recommended to assign them to the Radar antenna elevation and Range knob under advanced control settings.

Thrustmaster Warthog

The Thrustmaster Warthog is a replica of the HOTAS used in the A10-C aircraft. It is basicaly a F16 stick combined with a F15-E throttle.

The best way to configure BMS is to use the directX input. (this way you're keeping all the advantages of the F16 mastermodes (AA-AG-SRM as well as the short and long push functions etc)
You can use the HOTAS directly in game without any software using directX input but be advised that BMS will pick up the first 32 buttons of each controllers (32 buttons for the sticks and 32 for the throttle) due to a DirectX limitation and only ONE hat (the one from your primary input device that you have set in the CONTROLLER drop down menu). This means that if you have your joystick set as primary input device BMS will not recognize the hat of your throttle (coolie switch)

Anyway we can use a workaround using the Warthog software suite called TARGET. (There is two different version of TARGET. You can either use a GUI version or a more complicated but more powerfull Script version.)
Here what you should do:

- As the warthog stick have less than 32 buttons you should use it in-game without TARGET as your primary input device.

- Then you should use the throttle but as it does have more than 32 buttons if you're using it without TARGET you will not be able to use the coolie switch and you're will not be able to choose the 32 directX buttons. They will be designated by windows.

To avoid this my best advice is to make a TARGET profile (with the script editor) to be able to choose what buttons on the throttle will have a directX output (this way you can use your coolie switch) When you've affected all the 32 directX buttons you can still use what you have left using the script to emulate any keyboard keybinds.

There is several other good reasons to use the script editor.
For example, you can use the LED lights of the throttle (i.e lights ON when master ARM ON etc ...) You may also manage axes with any kind of button (this way I'm using 2 buttons to move my antenna elevation like an axis) and you can also make some chains of command that gives you the ability to have multiple outputs by pressing a button once. (very useful for turning ON or OFF all the lights with one button only)

Saitek X52 Pro

X52 Pro has customization MFDs among a couple other features. I have the regular and am fine with it but those with the Pro say it improves there experience by a lot

Saitek X65F

I refuse to buy an X-65 because it has no second trigger detent. That means you can't have the proper switchology to engage the TGP laser or ACMI recording in auto mode, and in DCS PAC doesn't work.

You could do some workarounds to fix these issues - for instance, designate a button or keypress for the first trigger detent in BMS and use that to trigger the TGP. I just find it highly annoying that saitek's top-end stick doesn't have something that is now common on sticks.

Otherwise, I've heard good things from the BMS crowd regarding the X-65's force sensing, it's apparently really enjoyable to fly.

Track-IR

BMS supports TrackIR and other head tracking systems natively. Enable TrackIR for 3D cockpit and TrackIR vector in the advanced control settings.

Free Track

Cheap Track-IR alternative.

The purple lights coming from the LED's is Infrared light that is invisible to the naked eye. However, these LED's have a little red light indicating that they are powered.

All the wiring for the bottom two LED's is modular and is constrained in the tube.

Same kind of thing, the LED and wiring are constrained in the tube.

The whole thing is wired in parallel so if any of the LED's burn out (I have not had a single LED failure in 5 years), I know which one is the problem. Also, the parallel wiring allows me to put all the positives and negatives together when I connect it with the power supply, making it look cleaner than random wires everywhere in a series circuit.

You can use the TrackClip PRO with this.

Specifications

• 5 Volt, 2000mA power supply ("PlayStation Portable [PSP]" charger with male/female connector)
• Copper Wiring
• 3x IR LED's (OSRAM SFH485P or equivalent), 1.5 volts each, 60 degree FOV
• 1x 27 Ohm resistor
• Webcam: Microsoft VX 3000 (with IR filter removed), incredibly reliable with no failures in 5 years.

{{#invoke:Navbox|navbox}}