BMS Device Setup Guide
BMS Device Setup Guide
33 MANUAL
CHANGE 1
Author: KOLBE
05. 2020
2-1
BMS Device Setup Guide
CHANGE 1
FOREWORD
PURPOSE AND SCOPE
This document shall give you a quick overview on how to set up your input devices with DX bindings
properly. It is addressed to the less experienced users. Experienced users who are familiar setting up their
devices will likely not find any valuable information here.
The main purpose is to help beginners to set up their device with ready to use profiles, so they don’t have
to mess around with the setup for too long.
We will guide you through the setup process and will explain what to do if you intend to edit your key file.
We also explain the functions used here.
Special thanks:
The following guys helped me a lot with testing this and giving me advices. Without your help this wouldn’t
be possible!
Ghostrider, Elmo, Floater, Kowalski, Snake, Cop, Buglar, xcom, vincent_dimicco, Red Beard, l3crusader and
Dunc
To save you some time; it is not needed to read every single line of this manual. However, you might want
to take a look at chapter 2 first, which contains an overall introduction along with some FAQs.
For each device we offer illustrated step by step instructions in chapter 3. Just read the chapter where your
input device is addressed. You will be guided through the setup process and referred to other chapters if
necessary.
If you need additional help you are referred to further instructions in chapter 4. This chapter contains
information applicable for all devices alike.
Specific Saitek related instructions can be found in chapter 5. You don’t need to read that chapter unless
you want to setup your own .pr0 file.
A function reference can be found in chapter 6. If you are not familiar with the functions / callbacks you
should take a look there.
Last but not least we have prepared a small checklist with tasks you should consider before flying. See
chapter 7.
2-2
BMS Device Setup Guide
CHANGE 1
TABLE OF CONTENTS
2 Introduction ......................................................................................................................... 2-7
2.1 Purpose Of The Provided Files ........................................................................................................ 2-7
2.2 Frequently Asked Questions ........................................................................................................... 2-8
2.2.1 What is a key file? ................................................................................................................... 2-8
2.2.2 What is a callback? .................................................................................................................. 2-9
2.2.3 How do I know which callback does what? ............................................................................ 2-9
2.2.4 Where do I find a complete callback list? ............................................................................... 2-9
2.2.5 How can I set up my own key file or make changes to the one I currently use? ................... 2-9
3 HOTAS Device Setup Guides............................................................................................ 3-10
3.1 TM Cougar (Dunc_DX) Setup ........................................................................................................ 3-11
3.1.1 Provided Files ........................................................................................................................ 3-11
3.1.2 Device Setup ......................................................................................................................... 3-11
3.1.3 Key File .................................................................................................................................. 3-12
3.1.4 BMS Setup ............................................................................................................................. 3-12
3.1.5 Axis Assignments................................................................................................................... 3-14
3.1.6 Test the device buttons ........................................................................................................ 3-16
3.1.7 Troubleshooting .................................................................................................................... 3-18
3.1.8 Notes about the Cougar Files ................................................................................................ 3-19
3.2 TM Warthog Setup ........................................................................................................................ 3-22
3.2.1 Provided Files ........................................................................................................................ 3-22
3.2.2 Device Setup ......................................................................................................................... 3-22
3.2.3 Key File .................................................................................................................................. 3-22
3.2.4 BMS Setup ............................................................................................................................. 3-23
3.2.5 Axis Assignments................................................................................................................... 3-25
3.2.6 Test the device buttons ........................................................................................................ 3-27
3.2.7 Troubleshooting .................................................................................................................... 3-29
3.3 Cougar Stick & TUSBA ................................................................................................................... 3-30
3.3.1 Provided Files ........................................................................................................................ 3-30
3.3.2 Device Setup ......................................................................................................................... 3-30
3.3.3 Key File .................................................................................................................................. 3-31
3.3.4 BMS Setup ............................................................................................................................. 3-31
3.3.5 Axis Assignments................................................................................................................... 3-33
3.3.6 Test the device buttons ........................................................................................................ 3-35
3.3.7 Troubleshooting .................................................................................................................... 3-37
3.4 WH Stick & Cougar ........................................................................................................................ 3-38
2-3
BMS Device Setup Guide
CHANGE 1
2-4
BMS Device Setup Guide
CHANGE 1
2-5
BMS Device Setup Guide
CHANGE 1
4.1 Select The Main Input Device: .................................................................................................... 4-105 hat gelöscht: 2 Introduction 2-7¶
2.1 Purpose Of The Provided Files 2-7¶
4.2 How Do I Load A Key File?........................................................................................................... 4-106 2.2 Frequently Asked Questions 2-8¶
2.2.1 What is a key file? 2-8¶
4.3 Assigning Axis: ............................................................................................................................. 4-107 2.2.2 What is a callback? 2-9¶
2.2.3 How do I know which callback does what? 2-9¶
4.4 What If I Can’t Select an Axis? .................................................................................................... 4-109 2.2.4 Where do I find a complete callback list? 2-9¶
2.2.5 How can I set up my own key file or make changes to the
4.5 Set Afterburner Detent ............................................................................................................... 4-110 one I currently use? 2-9¶
3 HOTAS Device Setup Guides 3-10¶
4.6 DX Device Sorting: ....................................................................................................................... 4-111 3.1 TM Cougar (Dunc_DX) Setup 3-11¶
3.1.1 Provided Files 3-11¶
4.7 How Do I Enter The Shifted Layer? ............................................................................................. 4-111 3.1.2 Device Setup 3-11¶
3.1.3 Key File 3-12¶
4.8 DX Device Buttons And Layers: ................................................................................................... 4-112 3.1.4 BMS Setup 3-12¶
3.1.5 Axis Assignments 3-14¶
4.9 How To Change DX Assignments? .............................................................................................. 4-112 3.1.6 Test the device buttons 3-16¶
3.1.7 Troubleshooting 3-18¶
4.10 What If I don’t Use The TM Cougar MFDs? ................................................................................ 4-113 3.1.8 Notes about the Cougar Files 3-19¶
3.2 TM Warthog Setup 3-22¶
4.11 Stuck Keys aka Can’t Release The Shifted Layer: ........................................................................ 4-114 3.2.1 Provided Files 3-22¶
3.2.2 Device Setup 3-22¶
4.12 What If I Don’t Have A TrackIR And Want Views On The POV Hat? ........................................... 4-115 3.2.3 Key File 3-22¶
3.2.4 BMS Setup 3-23¶
4.13 How to use the new Idle Detent Callbacks. ................................................................................ 4-116 3.2.5 Axis Assignments 3-25¶
3.2.6 Test the device buttons 3-27¶
5 Saitek Profile Specifics: .................................................................................................. 5-117 3.2.7 Troubleshooting 3-29¶
3.3 Cougar Stick & TUSBA 3-30¶
5.1 Clutch Button: ............................................................................................................................. 5-117 3.3.1 Provided Files 3-30¶
3.3.2 Device Setup 3-30¶
5.2 Mode Selector Switch: ................................................................................................................ 5-118 3.3.3 Key File 3-31¶
3.3.4 BMS Setup 3-31¶
5.3 Mouse Cursor / Ministick: ........................................................................................................... 5-120 3.3.5 Axis Assignments 3-33¶
3.3.6 Test the device buttons 3-35¶
5.4 Mouse Button / Wheel Button: .................................................................................................. 5-121 3.3.7 Troubleshooting 3-37¶
3.4 WH Stick & Cougar 3-38¶
5.5 Precision Slider (optional): .......................................................................................................... 5-121 3.4.1 Provided Files 3-38¶
3.4.2 Device Setup 3-38¶
5.6 Hats: ............................................................................................................................................ 5-122 3.4.3 Key File 3-39¶
3.4.4 BMS Setup 3-39¶
6 Callback Reference: ........................................................................................................ 6-123 3.4.5 Axis Assignments 3-41¶
3.4.6 Test the device buttons 3-43¶
6.1 The HOTAS Functions:................................................................................................................. 6-123 3.4.7 Troubleshooting 3-45¶
3.5 WH Stick & TUSBA 3-46¶
6.1.1 Stick functions ..................................................................................................................... 6-123 3.5.1 Provided Files 3-46¶
3.5.2 Device Setup 3-46¶
6.1.2 Throttle functions: .............................................................................................................. 6-128 3.5.3 Key File 3-46¶
3.5.4 BMS Setup 3-47¶
6.2 Miscellaneous functions: ............................................................................................................ 6-130 3.5.5 Axis Assignments 3-49¶
3.5.6 Test the device buttons 3-51¶
6.2.1 Cockpit Functions ................................................................................................................ 6-130 3.5.7 Troubleshooting 3-53¶
3.6 CH FS&PT Setup 3-54¶
6.2.2 Other Functions .................................................................................................................. 6-134 3.6.1 Provided Files 3-54¶
3.6.2 Device Setup 3-54¶
6.3 Device Assignment Overview: .................................................................................................... 6-136 3.6.3 Key File 3-55¶
3.6.4 BMS Setup 3-55¶
6.3.1 HOTAS – Stick: ..................................................................................................................... 6-136 3.6.5 Axis Assignments 3-57¶
3.6.6 Test the device buttons 3-59¶
6.3.2 HOTAS – Throttle: ............................................................................................................... 6-137 3.6.7 Troubleshooting 3-61¶
3.6.8 Notes about CH Files 3-62¶
6.3.3 Axes: .................................................................................................................................... 6-137 3.7 Saitek X-45 Setup 3-66¶
3.7.1 Provided Files 3-66¶
6.3.4 Miscellaneous: .................................................................................................................... 6-138 3.7.2 Device Setup 3-66¶
3.7.3 Key File 3-66¶
7 Prior Flight Checklist: ..................................................................................................... 7-139 3.7.4 BMS Setup 3-67¶
3.7.5 Axis Assignments 3-68¶
7.1 Before BMS Start:........................................................................................................................ 7-139 3.7.6 Test the device buttons 3-70¶
3.7.7 Troubleshooting 3-72¶
7.2 After BMS Start ........................................................................................................................... 7-139 3.8 Saitek X-52 Setup 3-73¶
3.8.1 Provided Files 3-73¶
3.8.2 Device Setup: 3-73¶
3.8.3 Control Panel Settings 3-73¶
3.8.4 Key File 3-74¶ ...
2-6
BMS Device Setup Guide
CHANGE 1
2 INTRODUCTION
As mentioned in the foreword the purpose of this guide is to get you in the air as quick as possible.
Depending on your device you should be able to set up your devices in less than 30 minutes. For each
device you’ll find illustrated instructions to guide you through the setup process.
The amount of work you need to do is minimal. In most cases you just have to load the corresponding key
file, set up your axis correctly and (if applicable) load a device profile via your vendor’s software (e.g.
T.A.R.G.E.T or Saitek’s Profile Launcher).
We will use DirectX (DX) as much as possible. However, for some devices we need other solutions in order
to make it work properly. But the amount of keyboard keys is minimal. Also, all devices use the same set of
functions. First, we aim a full real setup as much as feasible. Second, we use some other useful functions. In
case a device offers additional switches and buttons (like the TM Warthog) we add a couple of functions to
show the functionality. But this is just a proof of concept. It is up to you to change it to your liking once you
are more familiar with how DX works.
All key files are based on the Basic key file. This simply means that the amount of functions is limited as
most casual pilots don’t need everything in most cases.
This guide does not explain how to install drivers / programming software of your devices. Please refer to
the vendors installing instructions.
- A DeviceSorting_Example.txt
To make the key file (in specific: the DX code lines) work a specific order of the devices is necessary.
Otherwise you run into trouble. As we do not know which and how many devices you have installed
the DeviceSorting_Example.txt should give you a short overview how the first code lines in your
DeviceSorting.txt should look like.
- DX Code Lines.txt
This file contains the same code lines as the DX section in the key file. It is there for backup reasons
in case you accidently screwed things up.
2-7
BMS Device Setup Guide
CHANGE 1
In addition to that they contain also all DirectX bindings to control input devices. A DirectX input device
returns a button number which is recognized and interpreted by Falcon BMS. You can now say if I press
button “A” on the device bind that to a specific function (e.g. fire the gun).
Key files are located in the …/User/Config folder. We have five different standard key files in Falcon BMS.
There are four different key file profiles which use the same keystrokes layout.
However, there is a fifth one for the pitbuilders amongst us. This file has its own keyboard layout.
The standard key files above do not contain DX bindings. This is because there are too many different
devices with different button layouts out there. You need a specific solution for each device respectively.
2-8
BMS Device Setup Guide
CHANGE 1
A callback is simply a name of a function. There are quite a lot of them (roughly 1.000). Each callback
reflects a specific function or action to interact with the sim. To name a few examples there is a function to
pause the sim (corresponding callback: “SimPause”) or one to set a switch in the cockpit to a specific
position (e.g. Master Arm – On, callback: “SimArmMasterArm“).
Callbacks are invoked either by a physical device button directly via DirectX or a key binding on the
keyboard.
All cockpit related callbacks are addressed in the TO-BMS1F-16CM-1.pdf (in short: Dash-1).
The various view functions are covered in the Technical Manual (chapter 8) and the BMS Manual (chapter
9)
You can also have a look at chapter 6 of this manual where we describe the HOTAS and some other useful
functions.
There is also a text file in the same folder containing all callbacks in alphabetic order (Complete Callback
List.txt)
2.2.5 How can I set up my own key file or make changes to the one I currently use?
You’ll find a basic description in chapter 2. The HOTAS Issue in the BMS Technical Manual.pdf and in
chapter 4.9 and 4.12 of this manual.
Be advised that these instructions are just covering the very basics of this topic.
Full detailed instructions can be found in chapter 10. Key Files in the BMS Technical Manual.pdf.
2-9
BMS Device Setup Guide
CHANGE 1
It is likely that other ones will be added in the future. In the focus atm. are T.16000 series and Saitek X-56.
If your device is not listed here you may find a ready to use profile in the public forum.
If you have suggestions or even found bugs please don’t hesitate to give us an advice in the public forum
discussion here.
3-10
BMS Device Setup Guide
CHANGE 1
It is assumed that you already know how to setup your TM Hotas Cougar in general (i.e. performing
manual/automatic calibration, load and compile Foxy profiles). It only covers necessary steps to get the
provided files up and running.
This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever possible.
However, we will provide some examples of simultaneous DX / key use later on.
Apart from some minor changes (2 key settings, DX assignments on shifted layer, Foxy examples) this is
Dunc_DX.
CCP Settings:
Open the Falcon BMS.cfg file which is located in your BMS User\Config folder with a text editor. Find the
setting: set g_bHotasDgftSelfCancel. It’s set to 0 by default, please set it to 1. Additionally, verify that the
setting set g_nHotasPinkyShiftMagnitude is set to 256 (default).
3-11
BMS Device Setup Guide
CHANGE 1
Copy the file of your choice and paste it to the …/User/Config folder.
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
3-12
BMS Device Setup Guide
CHANGE 1
Select you main Input device from the drop down list. In this case “Thrustmaster HOTAS Cougar”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the TM Cougar key file you just pasted to the User/Config folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE.
More information about loading key files can be found in chapter 4.2 of this manual.
This opens the Advanced Option pages. You can ignore the AUDIO CONTROL page here. Instead we
focus on the VIEW CONTROL, FLIGHT CONTROL and AVIONICS CONTROL settings. In FLIGHT and
AVIONICS CONTROL we will do our axis assignments.
If you have no rudder device connected you should make sure that the “Enable Roll-linked NWS” checkbox
is active. This will allow you to steer your aircraft on ground with roll axis (left / right) inputs on the stick.
3-13
BMS Device Setup Guide
CHANGE 1
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-14
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-15
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roll axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-16
BMS Device Setup Guide
CHANGE 1
INPUT Button 2
INPUT Button 24
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 33
INPUT Button 84
3-17
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.1.7 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-18
BMS Device Setup Guide
CHANGE 1
Cougar_DX.tmm:
This macro file will only contain keyboard mappings. Everything that will be mapped by pure DirectX in the
BMS key file will not show up here.
2D_Cockpit = 2
3D_Cockpit = 3
Wheelbrakes = k
Note: To avoid side effects, it is good practice to use SINGLE keystrokes for macros only.
So whenever possible, avoid doing things like "Shift + Key" and use only "Key" instead.
Cougar_DX.tmj:
USE ZERO_MOUSE
DISABLE MOUSE
Map ALL Cougar buttons and hats to their default DirectX buttons:
USE ALL_DIRECTX_BUTTONS
By using ALL_DIRECTX_BUTTONS, the following DX values will get assigned: (this is purely Foxy functionality
and has nothing to do with BMS)
3-19
BMS Device Setup Guide
CHANGE 1
Now, BMS can handle exactly one function for each button/hat position for the unshifted position (without
Pinky/S3), and exactly one function for each button/hat position for the shifted position (with Pinky/S3).
So whenever we want to have only one function for each position, we don't need to do anything here in the
Foxy profile anymore, we will cover that completely in the BMS key file.
All that we still need to cover here are special cases where we want to have e.g.:
For example, if we only want to override e.g. a shifted position, we need to manually map the unshifted
position back to whatever DX mapping was there by default. See the TG1 below for a complete example.
Trigger 1st Detent shifted (/I) should be used to toggle between Snap (2D) and Pan 3D cockpit view. As BMS
cannot toggle, we need to create the toggle here as usual, using /I to indicate that this should be for the
shifted layer, and then add the two toggle positions with /T.
However, as we now did override TG1 for /I, TG1 for /O will be reset to "nothing" automatically by Foxy. But
we want to keep the default DX assignment, hence we need to add it back manually using /O /H and the DX
mapping from the list above.
Additionally, we will keep the state of TG1 unshifted in a logical flag for TG2 (see below).
/O /H {DX1 X1}
Trigger 2nd Detent shifted (/I) should do nothing to avoid firing the guns accidentally while toggling
between 2D and 3D cockpit view. Usually, we can map this in the BMS key file directly. However, as soon as
we release the pinky switch, BMS will immediately detect that TG2 is pressed and start firing. So what we
do here is make sure that BMS only sees TG2 when it has been reached by passing only over TG1 (and not
Pinky+TG1) before.
BTN TG2 ^
BTN X2 /H DX6
3-20
BMS Device Setup Guide
CHANGE 1
a) The normal AP override (which is done by BMS DX assignment, hence we just use the
default DX mapping from the list),
b) Wheelbrakes
To make sure that both commands are done at the same time, we use the curly brackets to tie them
together. Because we did not override /I or /O, we don't need to do anything else here, the rest will be in
the BMS key file.
Because we mapped the microstick (radar cursor) to use analog axis in the HOTAS CCP, the toe brake axis
can only be used with digital statements now. Hence we will simply issue and hold a "Wheelbrake"
keystroke whenever either of the toe brakes is pushed down more than 10%.
3-21
BMS Device Setup Guide
CHANGE 1
- BMS - BasicDX TM Warthog_MFD.key => BMS key file with TM Cougar MFDs
- BMS - BasicDX TM Warthog.key => BMS key file without TM Cougar MFDs
- DeviceSorting_Example.txt => example of the DX device order
- HOTAS Print Layout.pdf => printable overview of assigned functions
- DX Code Lines.txt => DX code lines only (with MFDs)
- Quick Setup Guide.txt => Short device setup instructions
Please make sure you have installed the latest drivers and software. We will not describe how to do this.
Please refer to Thrustmaster’s installing instructions.
It is assumed that you already know how to setup your TM Warthog in general. It only covers necessary
steps to get the provided files up and running.
This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever possible.
This TM Warthog profile doesn’t provide any .tmc files. All buttons are available via DX right away and we
will assign all functions via DirectX exclusively. BMS recognizes both devices (stick and throttle) as two
separate input devices. We don’t have to care about T.A.R.G.E.T. programming in any way.
If you need / want additional functions provided by T.A.R.G.E.T you have to work it out on your own. It is
way out of scope for what we try to achieve here.
Also note that not all switches on the throttle have functions assigned. This is by purpose to show the
concept of DirectX.
Copy the file of your choice and paste it to the …/User/Config folder.
3-22
BMS Device Setup Guide
CHANGE 1
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
Select you main Input device from the drop down list. In this case “Joystick - HOTAS Warthog”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the TM Warthog key file you just pasted to the User/Config folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE.
More information about loading key files can be found in chapter 4.2 of this manual.
3-23
BMS Device Setup Guide
CHANGE 1
This opens the Advanced Option pages. You can ignore the AUDIO CONTROL page here. Instead we
focus on the VIEW CONTROL, FLIGHT CONTROL and AVIONICS CONTROL settings. In FLIGHT and
AVIONICS CONTROL we will do our axis assignments.
If you have no rudder device connected you should make sure that the “Enable Roll-linked NWS” checkbox
is active. This will allow you to steer your aircraft on ground with roll axis (left / right) inputs on the stick.
3-24
BMS Device Setup Guide
CHANGE 1
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-25
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-26
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roil axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-27
BMS Device Setup Guide
CHANGE 1
INPUT Button 4
INPUT Button 47
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 65
3-28
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.2.7 Troubleshooting
I want to learn more about DX Device buttons and layers:
How to use the new Idle Detent callbacks? hat formatiert: Schriftart: Fett
Read chapter 4.13. hat gelöscht: ¶
3-29
BMS Device Setup Guide
CHANGE 1
It is assumed that you already know how to setup your TM Hotas Cougar and TUSBA R1/2 in general (i.e.
performing manual/automatic calibration, load and compile Foxy profiles). It only covers necessary steps to
get the provided files up and running.
This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever possible.
However, we will provide some examples of simultaneous DX / key use later on.
The setup is based on the TM Cougar (Dunc_DX) profile. It works for both, TUSBA R1 & R2.
CCP Settings:
Copy the Cougar_DX.tmm and Cougar_DX.tmj files to your Foxy files folder, open foxy, load the files,
compile and download to the Cougar. Please note that you will not see anything happen in the Foxy
keytester if you press Cougar buttons, as this profile uses DirectX buttons nearly exclusively.
For more information about the .tmm / .tmj files please refer to chapter 3.1.8 Notes about the Cougar Files.
3-30
BMS Device Setup Guide
CHANGE 1
Copy the file of your choice and paste it to the …/User/Config folder.
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
3-31
BMS Device Setup Guide
CHANGE 1
Select you main Input device from the drop down list. In this case “Thrustmaster HOTAS Cougar”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the Cougar Stick & TUSBA key file you just pasted to the
User/Config folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE.
More information about loading key files can be found in chapter 4.2 of this manual.
This opens the Advanced Option pages. You can ignore the AUDIO CONTROL page here. Instead we
focus on the VIEW CONTROL, FLIGHT CONTROL and AVIONICS CONTROL settings. In FLIGHT and
AVIONICS CONTROL we will do our axis assignments.
If you have no rudder device connected you should make sure that the “Enable Roll-linked NWS” checkbox
is active. This will allow you to steer your aircraft on ground with roll axis (left / right) inputs on the stick.
3-32
BMS Device Setup Guide
CHANGE 1
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-33
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-34
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roll axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-35
BMS Device Setup Guide
CHANGE 1
INPUT Button 2
INPUT Button 44
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 65
3-36
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.3.7 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-37
BMS Device Setup Guide
CHANGE 1
- BMS - BasicDX WH_Cougar_MFD.key => BMS key file with TM Cougar MFDs
- BMS - BasicDX WH_Cougar.key => BMS key file without TM Cougar MFDs
- DeviceSorting_Example.txt => example of the DX device order
- HOTAS Print Layout.pdf => printable overview of assigned functions
- DX Code Lines.txt => DX code lines only (with MFDs)
- Quick Setup Guide.txt => Short device setup instructions
Please make sure you have installed the latest drivers and software. We will not describe how to do this.
Please refer to Thrustmaster’s installing instructions.
It is assumed that you already know how to setup your TM Warthog Stick & TM Cougar in general. It only
covers necessary steps to get the provided files up and running.
This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever possible.
We don’t provide any profile files (.tmc/.tmm/.tmj). All buttons are available via DX right away and we will
assign all functions via DirectX exclusively. BMS recognizes both devices (stick and throttle) as two separate
input devices. We don’t have to care about T.A.R.G.E.T. / Foxy programming in any way.
If you need / want additional functions provided by T.A.R.G.E.T / Foxy you have to work it out on your own.
It is way out of scope for what we try to achieve here.
CCP Settings:
3-38
BMS Device Setup Guide
CHANGE 1
Copy the file of your choice and paste it to the …/User/Config folder.
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
3-39
BMS Device Setup Guide
CHANGE 1
Select you main Input device from the drop down list. In this case “Joystick - HOTAS Warthog”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the WH Stick & Cougar key file you just pasted to the User/Config
folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE. More information about loading key files can be found in chapter 4.2 of this manual.
This opens the Advanced Option pages. You can ignore the AUDIO CONTROL page here. Instead we
focus on the VIEW CONTROL, FLIGHT CONTROL and AVIONICS CONTROL settings. In FLIGHT and
AVIONICS CONTROL we will do our axis assignments.
If you have no rudder device connected you should make sure that the “Enable Roll-linked NWS” checkbox
is active. This will allow you to steer your aircraft on ground with roll axis (left / right) inputs on the stick.
3-40
BMS Device Setup Guide
CHANGE 1
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-41
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-42
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roil axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-43
BMS Device Setup Guide
CHANGE 1
INPUT Button 4
INPUT Button 56
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 65
3-44
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.4.7 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-45
BMS Device Setup Guide
CHANGE 1
- BMS - BasicDX WH_TUSBA_MFD.key => BMS key file with TM Cougar MFDs
- BMS - BasicDX WH_TUSBA.key => BMS key file without TM Cougar MFDs
- DeviceSorting_Example.txt => example of the DX device order
- HOTAS Print Layout.pdf => printable overview of assigned functions
- DX Code Lines.txt => DX code lines only (with MFDs)
- Quick Setup Guide.txt => Short device setup instructions
Please make sure you have installed the latest drivers and software. We will not describe how to do this.
Please refer to Thrustmaster’s installing instructions.
It is assumed that you already know how to setup your TM Warthog Stick & TUSBA R1/R2 in general. It only
covers necessary steps to get the provided files up and running.
This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever possible.
We don’t provide any profile files (.tmc/.tmm/.tmj). All buttons are available via DX right away and we will
assign all functions via DirectX exclusively. BMS recognizes both devices (stick and throttle) as two separate
input devices. We don’t have to care about T.A.R.G.E.T. / Foxy programming in any way.
If you need / want additional functions provided by T.A.R.G.E.T / Foxy you have to work it out on your own.
It is way out of scope for what we try to achieve here.
Copy the file of your choice and paste it to the …/User/Config folder.
3-46
BMS Device Setup Guide
CHANGE 1
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
Select you main Input device from the drop down list. In this case “Joystick - HOTAS Warthog”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the WH Stick & TUSBA key file you just pasted to the User/Config
folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE. More information about loading key files can be found in chapter 4.2 of this manual.
3-47
BMS Device Setup Guide
CHANGE 1
This opens the Advanced Option pages. You can ignore the AUDIO CONTROL page here. Instead we
focus on the VIEW CONTROL, FLIGHT CONTROL and AVIONICS CONTROL settings. In FLIGHT and
AVIONICS CONTROL we will do our axis assignments.
If you have no rudder device connected you should make sure that the “Enable Roll-linked NWS” checkbox
is active. This will allow you to steer your aircraft on ground with roll axis (left / right) inputs on the stick.
3-48
BMS Device Setup Guide
CHANGE 1
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-49
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-50
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roil axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-51
BMS Device Setup Guide
CHANGE 1
INPUT Button 4
INPUT Button 44
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 65
3-52
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.5.7 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-53
BMS Device Setup Guide
CHANGE 1
Please make sure you have installed the latest drivers and CH Control Manager software. We will not
describe how to do this. Please refer to CH’s installing instructions.
It is assumed that you already know how to setup your CH FS&PT in general (i.e. load profiles). It only
covers necessary steps to get the provided files up and running.
This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever possible.
Not all buttons are available as pure DX buttons right away, if you don’t tell the device to handle them like
that. In this case this is true for the POV hat on the throttle. So before the device can be set up with DX via
the key file some profile settings have to be done first.
We provide .cms / .map files which include all necessary changes to run your device with DirectX bindings.
Before you start BMS you must download the profile the BMS CH FS&PT_DX.cms & .map to the
devices.
If you want to learn more about the specific settings in this profile please have a look at CH Device Specifics
chapter later in this manual.
Important note:
CH Control Manager must be started and placed into mapped mode before starting Falcon BMS or Falcon
BMS will forget axis assignments.
So, make sure this option is active before starting Falcon BMS. The button should look like this:
Please keep in mind that both controllers will be identified as CH Control Manager Device 1 (Fighterstick)
and CH Control Manager Device 2 (Pro Throttle) rather than CH Fighterstick USB and CH Pro Throttle USB.
3-54
BMS Device Setup Guide
CHANGE 1
Copy the file of your choice and paste it to the …/User/Config folder.
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
3-55
BMS Device Setup Guide
CHANGE 1
Select you main Input device from the drop down list. In this case “CH Control Manager Device 1”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the CH FS&PT key file you just pasted to the User/Config folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE.
More information about loading key files can be found in chapter 4.2 of this manual.
If you have no rudder device connected you should make sure that the “Enable Roll-linked NWS” checkbox
is active. This will allow you to steer your aircraft on ground with roll axis (left / right) inputs on the stick.
3-56
BMS Device Setup Guide
CHANGE 1
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-57
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-58
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roil axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-59
BMS Device Setup Guide
CHANGE 1
INPUT Button 2
INPUT Button 48
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 65
3-60
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.6.7 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-61
BMS Device Setup Guide
CHANGE 1
There are two options for setting up the controllers. The recommended option is to use the CH Control
Manager to program the throttle so the POV hat may be used. The second option is to utilize the controllers
without programming them. The default setup uses CH Control Manager.
Using a CH Control Manager profile has both good and bad points associated with it. On the good side, it
makes the throttle POV hat available for use within Falcon BMS and this allows a more natural layout of
functionality. On the bad side, it requires the CH Control Manager be started and placed in mapped mode
prior to starting Falcon BMS. If this does not happen, Falcon BMS will forget the axis assignments for your
controllers and you will have to redefine them after starting CH Control Manager and setting mapped
mode.
It is quite possible to use the Fighterstick and ProThrottle without programming. On the good side, this is
the easiest solution and offers a reliable setup you can depend on every time you start Falcon BMS. On the
bad side, it has less buttons and hats that may be used to configure the throttle and some functionality will
likely need to be moved to other, less natural locations.
The choice of setup is yours, though the default DX assignments expect to use the POV hat.
There is very little configuration required of the Fighterstick and Pro Throttle in order to use them as a
HOTAS configuration in Falcon BMS. This section walks through the configuration.
If you do not already have CH Control Manager, it can be downloaded from the CH web site. As there is very
little required of this profile, we will create it from scratch.
3-62
BMS Device Setup Guide
CHANGE 1
2. Click the Map Wizard tool (sheet with the lightning bolt). Then select the Fighterstick and Pro
Throttle as your devices.
3. Click Okay
4. When asked about combining your controllers, click “No”.
5. When asked about including CMS capability in this map, click “No”. Scripting is not required, but if
you want to add it, it will not hurt.
6. Click “Finish”
The end result is a map for both devices. The DX Device for the Fighterstick should be CM Device 1 and the
Pro Throttle DX Device should be CM Device 2. Click the device tabs to validate this.
Stick:
3-63
BMS Device Setup Guide
CHANGE 1
Throttle:
Whether or not you add CH Pro Pedals to the profile is more or less irrelevant at this point. The only
noticeable difference will be the device name used in the BMS Setup GUI. If they are added, make sure the
Pro Pedals use the DX Device setting of CM Device 3.
Now, we need to program the POV hat on the throttle. Start by clicking the throttle POV hat right. It will
show the hat with “Use as POV” selected. You need to uncheck that box. Each direction of the POV hat will
need to be programmed as a separate DX button and we need to start with the up direction first.
Click the Throttle POV hat up. Set the DirectX Device to CM Device 2 (same as the other buttons on the
throttle). The first 16 buttons are already taken, so set DirectX Control to Button 17. It should now look like
this:
3-64
BMS Device Setup Guide
CHANGE 1
Now click the POV hat to the upper right. Set the DirectX Device to CM Device 2 again and the DirectX
Control to Button 18 (incrementing by one for each direction). Continue this process clockwise with each
direction, ending with the upper left being Button 24. The number and direction here is important. If you do
not get this right, it will not match the DX generation spreadsheet.
You can now save the profile as BMS HOTAS w POV.map. Save the map to your My Documents\CH Control
Manager\Maps directory for future use.
Once saved, click the download tool in CH Control Manager to download the profile to the devices. Once
the download has completed, place CH Control Manager in mapped mode before starting Falcon BMS.
Note: CH Control Manager must be started and placed into mapped mode before starting
Falcon BMS or Falcon BMS will forget axis assignments.
For the non-programmed option, the device names will be CH Fighterstick USB and CH Pro Throttle USB.
For the CH Control Manager option, the device names will be CH Control Manager Device 1 and CH Control
Manager Device 2. The CH Control Manager wizard will make the Fighterstick the first device (CH Control
Manager Device 1) and the throttle the second device (CH Control Manager Device 2).
3-65
BMS Device Setup Guide
CHANGE 1
Please make sure you have installed the latest drivers and SST software. We will not describe how to do
this. Please refer to Saitek’s installing instructions.
It is assumed that you already know how to setup your Saitek X-45 in general (i.e. load profiles). It only
covers necessary steps to get the provided files up and running.
This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever possible.
Not all buttons are available as pure DX buttons right away, if you don’t tell the device to handle them like
that. Instead some buttons come with predefined functions. So before the device can be set up with DX via
the key file some profile settings have to be done first.
We provide a .pr0 file which includes all necessary changes to run your device with DirectX bindings. Before
you start BMS you must load the BMS X-45_DX.pr0 with the Profile Launcher.
If you want to learn more about the specific settings in this profile please have a look at chapter 5 of this
manual.
Copy the file of your choice and paste it to the …/User/Config folder.
3-66
BMS Device Setup Guide
CHANGE 1
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
Select you main Input device from the drop down list. In this case “Saitek X45”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the X-45 key file you just pasted to the User/Config folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE.
More information about loading key files can be found in chapter 4.2 of this manual.
3-67
BMS Device Setup Guide
CHANGE 1
This opens the Advanced Options pages. You can ignore VIEW CONTROL and AUDIO CONTROL
pages here. Instead we focus on the FLIGHT CONTROL and AVIONICS CONTROL settings. Here we
will do our axis assignments.
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-68
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-69
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roil axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-70
BMS Device Setup Guide
CHANGE 1
INPUT Button 2
INPUT Button 5
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 33
INPUT Button 84
3-71
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.7.7 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-72
BMS Device Setup Guide
CHANGE 1
Please make sure you have installed the latest drivers and SST software. We will not describe how to do
this. Please refer to Saitek’s installing instructions. It is assumed that you already know how to setup your
Saitek X-52 in general (i.e. load profiles). It only covers necessary steps to get the provided files up and
running. This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever
possible.
Not all buttons are available as pure DX buttons right away, if you don’t tell the device to handle them like
that. Instead some buttons come with predefined functions. So before the device can be set up with DX via
the key file some profile settings have to be done first. We provide a .pr0 file which includes all necessary
changes to run your device with DirectX bindings. Before you start BMS you must load the BMS X-
52_DX.pr0 with the Profile Launcher. If you want to learn more about the specific settings in this profile
please have a look at chapter 5 of this manual.
3-73
BMS Device Setup Guide
CHANGE 1
Copy the file of your choice and paste it to the …/User/Config folder.
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
3-74
BMS Device Setup Guide
CHANGE 1
Select you main Input device from the drop down list. In this case “Saitek X52”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the X-52 key file you just pasted to the User/Config folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE.
More information about loading key files can be found in chapter 4.2 of this manual.
This opens the Advanced Options pages. You can ignore the AUDIO CONTROL page here. Instead
we focus on the VIEW CONTROL, FLIGHT CONTROL and AVIONICS CONTROL settings. Here we will
do our axis assignments.
This is optional.
The Saitek X-52 offers a precision slider on the throttle. As this is one not used to for any of the real HOTAS
axes you might want to assign it to something else. A good choice is the Field Of View. This offers you the
opportunity to change the field of view (FOV) with an axis. If you decide to use your precision slider to
change the Field Of View choose the slider axis from the dropdown menu and set it to “Reverse”.
3-75
BMS Device Setup Guide
CHANGE 1
Please note that all keyboard functions (e.g. “Look Closer” and FOV changes with the mouse wheel) are
inoperative when assigning an axis to FOV.
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-76
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-77
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roil axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-78
BMS Device Setup Guide
CHANGE 1
INPUT Button 5
INPUT Button 8
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 33
INPUT Button 84
3-79
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.8.8 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-80
BMS Device Setup Guide
CHANGE 1
Please make sure you have installed the latest drivers and SST software. We will not describe how to do
this. Please refer to Saitek’s installing instructions.
It is assumed that you already know how to setup your Saitek X-52pro in general (i.e. load profiles). It only
covers necessary steps to get the provided files up and running.
This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever possible.
Not all buttons are available as pure DX buttons right away, if you don’t tell the device to handle them like
that. Instead some buttons come with predefined functions. So before the device can be set up with DX via
the key file some profile settings have to be done first. We provide a .pr0 file which includes all necessary
changes to run your device with DirectX bindings. Before you start BMS you must load the BMS X-
52pro_DX.pr0 with the Profile Launcher.
3-81
BMS Device Setup Guide
CHANGE 1
If you want to learn more about the specific settings in this profile please have a look at chapter 5 of this
manual.
Copy the file of your choice and paste it to the …/User/Config folder.
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
3-82
BMS Device Setup Guide
CHANGE 1
Select you main Input device from the drop down list. In this case “Saitek X52pro”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the X-52pro key file you just pasted to the User/Config folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE.
More information about loading key files can be found in chapter 4.2 of this manual.
This opens the Advanced Options pages. You can the AUDIO CONTROL page here. Instead we focus
on the VIEW CONTROL, FLIGHT CONTROL and AVIONICS CONTROL settings. Here we will do our axis
assignments.
This is optional.
The Saitek X-52pro offers a precision slider on the throttle. As this is one not used to for any of the real
HOTAS axes you might want to assign it to something else. A good choice is the Field Of View. This offers
you the opportunity to change the field of view (FOV) with an axis. If you decide to use your precision slider
to change the Field Of View choose the slider axis from the dropdown menu and set it to “Reverse”.
3-83
BMS Device Setup Guide
CHANGE 1
Please note that all keyboard functions (e.g. “Look Closer” and FOV changes with the mouse wheel) are
inoperative when assigning an axis to FOV.
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-84
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-85
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roil axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-86
BMS Device Setup Guide
CHANGE 1
INPUT Button 5
INPUT Button 8
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 33
INPUT Button 84
3-87
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.9.8 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-88
BMS Device Setup Guide
CHANGE 1
Please make sure you have installed the latest drivers and SST software. We will not describe how to do
this. Please refer to Saitek’s installing instructions. It is assumed that you already know how to setup your
Saitek X-55 in general (i.e. load profiles).
It only covers necessary steps to get the provided files up and running. This profile uses BMS DirectX
shifting feature to avoid any emulated keyboard input whenever possible.
Not all buttons are available as pure DX buttons right away, if you don’t tell the device to handle them like
that. Instead some buttons come with predefined functions. So before the device can be set up with DX via
the key file some profile settings have to be done first.
We provide a .pr0 file which includes all necessary changes to run your device with DirectX bindings. Before
you start BMS you must load the BMS X-55_DX.pr0 with the Profile Launcher. Please note that you always
must use “Mode 1”!
If you want to learn more about the specific settings in this profile please have a look at chapter 5 of this
manual.
Copy the file of your choice and paste it to the …/User/Config folder.
3-89
BMS Device Setup Guide
CHANGE 1
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
Select you main Input device from the drop down list. In this case “Saitek X55”.
If you need help with that or for further information see chapter 4.1 of this manual.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE.
More information about loading key files can be found in chapter 4.2 of this manual.
3-90
BMS Device Setup Guide
CHANGE 1
This opens the Advanced Options pages. You can ignore VIEW CONTROL and AUDIO CONTROL
pages here. Instead we focus on the FLIGHT CONTROL and AVIONICS CONTROL settings. Here we
will do our axis assignments.
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-91
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-92
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roil axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-93
BMS Device Setup Guide
CHANGE 1
INPUT Button 6
INPUT Button 34
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 65
3-94
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.10.7 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-95
BMS Device Setup Guide
CHANGE 1
Please make sure you have installed the latest drivers and SST software. We will not describe how to do
this. Please refer to Saitek’s installing instructions.
It is assumed that you already know how to setup your Saitek X-65F in general (i.e. load profiles). It only
covers necessary steps to get the provided files up and running.
This profile uses BMS DirectX shifting feature to avoid any emulated keyboard input whenever possible.
Please note that you always must use “Mode 1”!
Not all buttons are available as pure DX buttons right away, if you don’t tell the device to handle them like
that. Instead some buttons come with predefined functions. So before the device can be set up with DX via
the key file some profile settings have to be done first.
We provide a .pr0 file which includes all necessary changes to run your device with DirectX bindings. Before
you start BMS you must load the BMS X-65F_DX.pr0 with the Profile Launcher.
If you want to learn more about the specific settings in this profile please have a look at chapter 5 of this
manual.
Copy the file of your choice and paste it to the …/User/Config folder.
3-96
BMS Device Setup Guide
CHANGE 1
Once in the setup screen hit the CONTROLLERS button. This opens the Controllers screen shown below:
1.
.
2.
3. .
Select you main Input device from the drop down list. In this case “Pro Flight X65 Control System”.
If you need help with that or for further information see chapter 4.1 of this manual.
Click on LOAD button and select the X-65F key file you just pasted to the User/Config folder.
You can verify that the correct key file is loaded on top of the key file content box next to CURRENT
KEYFILE.
More information about loading key files can be found in chapter 4.2 of this manual.
3-97
BMS Device Setup Guide
CHANGE 1
This opens the Advanced Options pages. You can ignore VIEW CONTROL and AUDIO CONTROL
pages here. Instead we focus on the FLIGHT CONTROL and AVIONICS CONTROL settings. Here we
will do our axis assignments.
Set the axis of the device as shown in the picture below. You just have to select them from the dropdown
list. After assigning an axis test it by moving the axis over its full range. Monitor the axis bar.
3-98
BMS Device Setup Guide
CHANGE 1
Next go to the Avionics Control page and set the axis as shown below and test them.
If all axes have been assigned successfully hit the OK button which brings you back to the Setup –
Controllers page.
If an axis is not available from the dropdown menu it is assigned somewhere else. In this case you have to
take a look at the other Control pages first. What to do in this case is described in chapter 4.4 of this
manual.
After all axes have been assigned successfully you should define the afterburner detent. Without doing so
you can’t use the afterburner in the sim.
Like shown in the screenshot on the next page you have two axis bars. The right one is for the throttle axis.
Move your throttle to a position where you want to set the afterburner detent. Then click on SET AB
button. This defines the position on the throttle axis where the afterburner kicks in.
3-99
BMS Device Setup Guide
CHANGE 1
It is a good habit to recenter your device by releasing the controller and pressing the CENTER button. The
pitch and roil axis of your main input device will then be centred to avoid unwanted shifts in the sim which
makes flying the aircraft much more difficult.
Once you press a button the result will be displayed below the key file content list next to INPUT.
3-100
BMS Device Setup Guide
CHANGE 1
INPUT Button 5
INPUT Button 7
If you don’t use the TM Cougar MFDs you can skip this part.
INPUT Button 33
INPUT Button 84
3-101
BMS Device Setup Guide
CHANGE 1
In case wrong button numbers / functions are shown it is likely that the device order is not recognized
correctly by BMS. You can fix that by editing the DeviceSorting.txt located in your …/User/Config folder.
Once the device sorting is done repeat the steps on the previous page. If everything works correctly you are
done here.
Test in 3d:
It is unfortunately not possible to test the shifted layer in the ui. You have to test them in 3d. The easiest
way is to simply open the training mission 2 (Navigation) as the jet is already airborne.
You can repeat the same steps as shown on the previous page but this time with the functions on the
shifted layer. In case you wonder how to activate the shifted layer please read chapter 4.7 of this manual.
Just open the HOTAS Print Layout.pdf look for the function CKPIT: Nightvision – Toggle and try it.
3.11.7 Troubleshooting
I want to learn more about DX Device buttons and layers:
3-102
BMS Device Setup Guide
CHANGE 1
In order to make the MFDs work you don’t have to install any software (e.g. T.A.R.G.E.T) or drivers. The
MFDs work right out of the box. Just plug them in and the rest is done via DirectX assignments in the key
file.
If have another input device not covered here but want to use the MFDs as well we offer two solutions:
1. Your main input device is one single unit with stick and throttle (e.g. TM Cougar, Saitek X-52)
We assume this device is the 1st DX controller in the DeviceSorting.txt (check chapter 4.6 if you
don’t know what that is).
If you have connected the MFDs make sure, they are the 2nd and 3rd controller in the list. All you
have to do is open your key file and paste the entire content of DX Code Lines 2&3.txt to the end of
that file. Now the DX code lines are included the MFDs should work with BMS.
2. You main input device is the stick and you have in addition another device as throttle (e.g. TM
Warthog, Saitek X-55)
In this case we assume that your stick and throttle are the first both controllers in the
DeviceSorting.txt. Make sure the MFDs are on the positions 3 and 4. Open your key file and paste
the entire content of DX Code Lines 3&4.txt to the end of that file.
3-103
BMS Device Setup Guide
CHANGE 1
This is what you should see: (the first number is for MFDs as 2nd and 3rd device, in brackets for 3rd and 4th)
3-104
BMS Device Setup Guide
CHANGE 1
4 GENERAL NOTES:
This chapter addresses some general information applicable for all DX devices. We will refer to this chapter
when necessary. So, in order to safe you some time you can skip it for now and instead read it if you need
to.
On the other hand there are also HOTAS systems which have two controller units (Stick and Throttle) like it
is the case for TM Warthog. In this case you must select the Stick.
4-105
BMS Device Setup Guide
CHANGE 1
This opens a select dialog where you can pick your key file from the list (In this case it is assumed you have
copied BMS – Basic TM Cougar_DX.key to the …User/Config folder).
4-106
BMS Device Setup Guide
CHANGE 1
Verify that the correct key file is loaded. You can see the currently loaded key file on top of the content list.
You can reach this screen by clicking the ADVANCED button located beneath the key mappings.
4-107
BMS Device Setup Guide
CHANGE 1
This window has 4 tabs (categories) named VIEW CONTROL, FLIGHT CONTROL, AVIONICS CONTROL and
AUDIO CONTROL.
Before these tabs are described in detail, however, some words about analogue axis handling in Falcon BMS
are in order.
Axes Properties
Axes in Falcon have three properties that may be configured in the UI by the user:
These tabs provide a list of all available in-game axes. Depending of the nature of the axis, each of these
axes may have one of the following controls:
• A dropdown box where you can select the physical axis you want to map it to. (1)
• A 'value bar' (located to the right of the axis name) that shows the current value of the analogue
axis. (2)
• A dead zone dropdown box with 4 options: 'None', 'Small', 'Medium' and 'Large'. (3)
A dead zone is a region around the centre position of the axis in which motion is ignored. The axis
always reports '0' in a dead zone. Dead zones are symmetrical around the centre point of an axis.
➢ 'None' means exactly that, no dead zone is applied to the physical axis.
➢ 'Small' applies a dead zone 1% the size of the physical travel to either side of the '0' point.
➢ 'Medium' enlarges that size to 5%.
➢ 'Large' applies a 10% dead zone.
4-108
BMS Device Setup Guide
CHANGE 1
• A saturation drop down box that contains 4 options: 'None', 'Small', 'Medium' and 'Large'. (4)
A saturation zone is a zone of tolerance at the minimum and maximum of an axis. An axis value
within this zone is reported as the minimum or maximum value. The purpose of this is to allow for
axes (usually of the cheaper ilk) that report values less (or greater) than their maximum (or
minimum) value, even if their physical 'throw' is already at the maximum (or minimum). An
example might be a throttle slider that just cannot report 100% thrust even at its maximum
possible travel. Saturation zones are always symmetrical, that is the zones at the maximum and
minimum ends of an axis are of the same size.
2
1 3 4 5
You want to assign the throttle axis of your input device by selecting it in the “Throttle Axis” drop down list.
4-109
BMS Device Setup Guide
CHANGE 1
You learn that your throttle axis is not available there. That means the throttle axis has been assigned
somewhere else. The only way to solve that is that you go through all four control setting pages and search
for the throttle axis.
If you want to exchange the mappings of two axes you will have to temporarily map one of them to the
keyboard, in order to be able to select it in the other list box.
By default no detents are set. Instead the markers are at the top (green) and bottom (red) of the axis as
shown in the screenshot above. This means basically that no detents are defined.
You will see that the green and red bars are now set accordingly on the throttle range.
Some devices have a hardware detent (you feel a little resistance when moving the throttle
up). You should aim to set the detent to that position.
The most important setting here is the afterburner (AB) detent. Without setting it you won’t be
able to use the afterburner!
The IDLE detent is optional. We recommend skipping it for now as this setting is not really needed and due
to hardware limitation of most devices very tricky to use.
4-110
BMS Device Setup Guide
CHANGE 1
For that reason you can define a fixed order via the DeviceSorting.txt. That file is located in your
…/User/Config/… folder. It can be edited with any text editor, like e.g. notepad.
Once you have plugged in your controllers and started BMS the DeviceSorting.txt will be filled with a list of
these controllers. After shutting down BMS you can edit the txt file.
In the key files we provide it is always assumed that you have connected (in order)
We also provide a DeviceSorting_Example.txt to show you how the order should look like in your
DeviceSorting.txt. However, depending on the controllers in use this may vary from user to user. For more
information about the DeviceSorting.txt please refer to the BMS Technical Manual, chapter 10.7.2.
BMS provides two DX layers: The unshifted and the shifted layer. This in fact doubles the amount of
possible function assignments to your device. Shifting is done via the ”SimHotasPinkyShift“ callback. It is
named as STICK: PINKY SWITCH (DX SHIFT) in the key files and the devices print layouts.
1. On a short button press (>200ms) it has the real functionality as the Pinky button on the stick.
2. On a long button press (<200ms) it gives you access to the shifted layer.
When shifting is active (the corresponding button is pressed and held longer than 200ms) it shifts all
connected devices simultaneously. So, if you have mapped that function to your stick it invokes the shifted
layer on other devices (like MFDs and such) as well.
For more information about device buttons and layer read the next chapter.
Note: Some users report having troubles using DirectX shifting. If this is the case please refer to chapter
4.11.
4-111
BMS Device Setup Guide
CHANGE 1
For the DX shifting to work properly, you have to make sure that the Falcon BMS.cfg file includes the
following setting:
The default value is 256. This simply means that the DX button number is shifted by that value.
Example: BMS DX 1 (unshifted layer) + 256 (Shift magnitude) = BMS DX 257 (shifted layer)
The shifted layer is accessed by using the callback ”SimHotasPinkyShift“. This callback has the same
functionality as ”SimHotasPinky“ on a short button press while offering the opportunity to access the
shifted layer on a long button press.
It is essential that ”SimHotasPinkyShift“ is set to the one and the same DX button in both, the unshifted and
the shifted layer. Otherwise you’ll end up being stuck in the shifted layer without a chance to get back to
the functions assigned on the unshifted layer.
Example:
If the callback ”SimHotasPinkyShift“ is assigned to BMS DX Btn. # 4 than you have to make sure it is assigned
to BMS DX Btn. # 260 as well!
Shifted buttons that should do the same as the unshifted ones do not need to be mapped at all.
Shifted buttons that should do nothing at all (hence only work as unshifted buttons) need to be mapped to
"SimDoNothing".
If you don’t need a shifted layer you could also use ”SimHotasPinky“ instead.
The following list shows all DX button numbers for the first 8 devices with a shifting magnitude set to
(default) 256:
Here, we want to focus on editing the key files directly. The example is shown for the TM Cougar but applies
to all other devices the same way.
4-112
BMS Device Setup Guide
CHANGE 1
In the DX section of the TM Cougar key file we find the following code lines for the shifted layer:
Let’s assume you want to change the yellow marked function to something else. The callback
SimTriggerFirstDetent is the same as on the unshifted layer. So pressing the button TG1 on the TM Cougar
does exactly the same in both layers, hence you want to change that.
All you need to do is to replace the first part of the code line, the callback, with another one. Let’s assume
you just want to recenter your joystick when pressing TG1 in the shifted layer.
Make sure to keep the space between the callback and the DX Btn. # (256 in this case).
However, this means that you have to do the programming of the devices not covered here yourself. Either
you use your vendors programming software or you go down the full DX path.
How DX devices are programmed via the key file is explained in depth in the chapter 10 and in short in
chapter 2 of the BMS Technical Manual.
We’d like to remind you that this is advanced stuff. On the other hand, if understood, it is really not a
difficult thing to do.
One tool to help you setting up your devices the full DX path is the Key File Editor, located in the …/Docs/01
Input Devices folder.
4-113
BMS Device Setup Guide
CHANGE 1
This issue has been seen quite often in the forum. A stuck key issue appears when you are using
shifted functions. In this case it doesn’t matter if you are using the shifted function with your
keyboard (key with modifier/s) or with your DX input device (Pinky Shift with DX button). A popular
example is the TRIM function.
The reason for a stuck key is a mishandling of the key press sequence. Here is the way how to do it
properly:
1. Press and hold modifier key (keyboard) / Pinky switch (DX Shift)
If you release #4 & #5 in the wrong order the key(s) / function will most likely stuck. To prevent this
either use the correct order stated above or try to avoid using shifted functions.
At this point this already reflects 99% of all causes. But in theory there is another one.
3. Hardware malfunction:
This is rare but can happen of course. In this case you should try to set the ”SimHotasPinkyShift“
callback to another button. Just to cross check.
If the issue persists and you can rule out #1, #2 and #3 please feel free to report your problem, preferable in
this public forum thread.
4-114
BMS Device Setup Guide
CHANGE 1
4.12 WHAT IF I DON’T HAVE A TRACKIR AND WANT VIEWS ON THE POV HAT?
If you want to change this (unshifted: POV / shifted: Trim) you should do the following:
Open your currently used key file located in the …/Users/Config folder with a text editor of your choice.
Search for the following code lines:
Delete the yellow marked part and replace it with the following code lines:
OTWViewUp 0 -1 -3 0 0x0 0
SimDoNothing 0 -1 -3 1 0x0 0
OTWViewRight 0 -1 -3 2 0x0 0
SimDoNothing 0 -1 -3 3 0x0 0
OTWViewDown 0 -1 -3 4 0x0 0
SimDoNothing 0 -1 -3 5 0x0 0
OTWViewLeft 0 -1 -3 6 0x0 0
SimDoNothing 0 -1 -3 7 0x0 0
Do the same for the shifted layer. Replace the yellow part
4-115
BMS Device Setup Guide
CHANGE 1
If you would like to add other functions just replace the bolded callbacks by other callbacks of your choice.
In most cases, the up-right, down-right, down-left and up-left positions of the 8-way POV hat are not
needed. The SimDoNothing callbacks are used to act the POV as a 4-way Coolie Hat AND to avoid unwanted
actions, because the POV may have some default functions for the up-right...etc. positions. So it is always a
good idea to set ALL unused DX buttons (shifted and unshifted) to SimDoNothing!
If you don’t need a shifted layer at all (aka unshifted and shifted layer should do the same) you can simply hat gelöscht: ¶
delete the POV code lines from the shifted layer section of the key file. hat formatiert: Hochgestellt
hat formatiert: Schriftart: Fett
Formatiert: Standard, Einzug: Links: 1,25 cm, Keine
Aufzählungen oder Nummerierungen
Formatiert: Einzug: Links: 1,27 cm, Keine Aufzählungen
oder Nummerierungen
4.13 HOW TO USE THE NEW IDLE DETENT CALLBACKS. hat formatiert: Schriftart: Fett
To supplement the existing SimThrottleIdleDetent function we have a set of new callbacks. Although they Formatiert: Standard, Keine Aufzählungen oder
are speficially designed for TM Warthog users they also may be used with other HOTAS devices as well. In Nummerierungen
the following examples the use of TM Warthog Throttle as 2nd DX Input device is assumed. Formatiert: Listenabsatz, Nummerierte Liste + Ebene: 1 +
Nummerierungsformatvorlage: 1, 2, 3, … + Beginnen bei: 1 +
Ausrichtung: Links + Ausgerichtet an: 0,63 cm + Einzug bei:
1,27 cm
1. SimThrottleIdleDetentForward / SimThrottleIdleDetentBack Formatiert: Einzug: Links: 1,25 cm
This is mainly for single engine jets but could also be used for dual engine jets. In case you fly a dual
Formatiert: Einzug: Links: 0,63 cm
engine jet please note that the second (right) engine is triggerd simultaneously. We need the special
Formatiert: Einzug: Links: 1,25 cm
Press / Release code (left engine) while the right engine is set to SimDoNothing.
hat gelöscht: ¶
¶
# IDLERON (Idle detent right - Back) (Win DX61 = BMS DX60) ¶
SimThrottleIdleDetentBack 60 -2 -2 0 0x0 314 Formatiert: Intensives Zitat
hat formatiert: Intensive Hervorhebung, Englisch
# IDLERON (Fwd from - Back) (Vereinigtes Königreich)
SimThrottleIdleDetentForward 60 -2 -2 0x42 0x0 314 hat gelöscht: ¶
¶
¶
# IDLELON (Idle detent left - Back) (Win DX62 = BMS DX61)
¶
SimDoNothing 61 -2 -2 0 0x0 -1 ¶
¶
¶
# IDLELON (Fwd from Back) ¶
SimDoNothing 61 -2 -2 0x42 0x0 -1 ¶
¶
¶
¶
2. SimThrottleIdleDetentLeft / SimThrottleIdleDetentRight ¶
¶
These are designed for dual engine jets. You can put both engines from cutoff to idle position and
¶
vice versa independently. This is how the code should look like: ¶
¶
¶
# IDLERON (Idle detent right) (Win DX61 = BMS DX60) ¶
SimThrottleIdleDetentRight 60 -1 -2 0 0x0 314 ¶
¶
¶
# IDLELON (Idle detent left) (Win DX62 = BMS DX61) ¶
SimThrottleIdleDetentLeft 61 -1 -2 0 0x0 314 ¶
¶
¶
¶
Note: We don’t use the specific press / release events here. ¶
¶
¶
¶
¶
¶
4-116
BMS Device Setup Guide
CHANGE 1
But be advised: If you program buttons manually (assigning keys to them) you will lose their DX
functionality. Keep that in mind when editing these files.
As we aim for a full DX setup we have to do some settings first. Not all buttons are available as DX buttons
right away, if you don’t tell the device to handle them like that. Instead some buttons come with predefined
functions. These buttons can’t be accessed with DX. How this can be changed is described below.
Note: All screenshots are taken using the Saitek X-52 but they apply to other Saitek products as
well.
The clutch (i) button, when pressed, temporarily deactivates all other buttons by default. For more info
about this feature please refer to Saitek’s manual. Unfortunately we can’t use the clutch button with DX as
long as it has its default behavior. To change this you have to open the control panel - MFD page - and
uncheck the “Enable Clutch Mode” option like shown in the image below.
5-117
BMS Device Setup Guide
CHANGE 1
Now we can use the clutch button as a DX button. Other settings are not mandatory and you can set them
to your own liking.
We have overall six modes by default. The Mode buttons 1 – 3 are greyed out; hence they are not available
as DX buttons. First enter the Programming page and select the Grid View.
To use the mode 1-3 selector as DX buttons we have to delete five of them first. Just click on the “X” on the
top right corner of each mode (We suggest to start with mode 2 and go to the right from there) and confirm
by clicking on “Yes”.
5-118
BMS Device Setup Guide
CHANGE 1
Now we have “freed” Modes 2 and 3 from its default behavior (acting as a mode selector).
What we need to do here is a right click on the blue “Mode 1” button and select “No Buttons”. This deletes
the last mode and we can use all three modes with DX.
5-119
BMS Device Setup Guide
CHANGE 1
As we can’t assign the ministick as an axis in BMS setup menu we have to assign them manually with
keyboard keys. On the left image below you see the default settings of the ministick. It is assigned as a
mouse. First, we have to assign both x- and y-axis as “Bands” (right image). This opens the option of
assigning keys to them.
The first third (0-33%) and the last third (67-100%) of the overall axis range of the ministick can be set to
keys now, while the middle part stays untouched. This is a dead zone, so to speak. In this example we
assigned the keys for the radar cursor with the arrow keys in combination with the SHIFT modifier.
SHIFT UP ARROW
5-120
BMS Device Setup Guide
CHANGE 1
By default they are assigned as left and right mouse buttons. To change this right click on both and select
“Fall Back”. Now you can assign DX functions to them.
We could also set keys to the precision slider here. It works the same way as described above by setting it
to “Bands” and then assigning keys to it.
You could also decide to use it as an axis. Setting it to Field Of View (FOV) in BMS setup menu would be an
adoptable option. In this case stay with the option “Fall Back” (default). If doing so you have to change the
default behavior of the scroll wheel. It is set to Scroll up / down which also changes the FOV. You can assign
keys to it by setting it to “Fall Back”.
5-121
BMS Device Setup Guide
CHANGE 1
5.6 HATS:
Applies to: Saitek X-55
The hats H1, H2 (both on stick), H3 and H4 (both on throttle) must be set to 4-way.
5-122
BMS Device Setup Guide
CHANGE 1
6 CALLBACK REFERENCE:
On the following pages you find some information about the functions / callbacks which are used in the
ready to use profiles and key files. Please note that we don’t get into detail here as the corresponding
callbacks are explained in other manuals as well. It’s just to give you a basic idea about what they do.
This chapter is divided into three parts. First, as we aim for a full real HOTAS setup, we will explain in short
the main HOTAS functions. Then step after step the other functions as well. Last not least you find a chapter
with an overview about how and which functions are assigned to the various input devices.
We will guide you to the corresponding chapters in other manuals as well, specifically to the TO-BMS1F-
16CM-1 (Dash-1) where the functions are explained in detail and the BMS Training Manual to guide you to
the practice lessons.
Please note that the chapters you are referred to are by no means a complete list of what to read about a
specific topic. They have to be understood as a quick reference to guide you to detailed information in case
you want to learn more.
Trigger:
The stick offers a two stage trigger with two detents. The 1st detent fires the laser in Air to Ground (AG)
mode. The 2nd detent fires the gun. It triggers also an ACMI (Air Combat Maneuvering Instrumentation)
record if the AVTR (Audiovisual Tape Recorder) switch is set to “Auto”.
6-123
BMS Device Setup Guide
CHANGE 1
Pickle:
The pickle button fires air to air / air to ground missiles and drop bombs. Depending on the weapon in use a
long or a short press is required. It also drops stores (Selected Jettison). It triggers also an ACMI record if the
AVTR switch is set to “Auto”.
Pinky Switch:
The pinky switch changes the FOV (Field of View) of the radar, HSD (Horizontal Situation Display), TGP
(Targeting Pod) and AGM-65 Maverick weapon depending on the master mode. It can be understood as a
zoom function.
6-124
BMS Device Setup Guide
CHANGE 1
Paddle Switch:
The paddle switch temporarily disengages the autopilot (if engaged) as long as the paddle is depressed. It
also interrupts / inhibits Flyup in TFR (Terrain Following Radar) operations.
MSL STEP: In air to ground mode it cycles through bomb delivery modes (CCIP, CCRP, DTOS) and cycles
through weapon stations for missiles of the same type (e.g. AGM-65 Maverick). In air to air
mode it cycles through the weapon stations on a short press (< 0.5 sec.) and steps to the
next missile type on a long press.
A/R DISC: Disconnects manually from the boom while air refueling.
6-125
BMS Device Setup Guide
CHANGE 1
Be warned. This is probably one of the most complicated input buttons in BMS as it includes so many
different functions depending on master modes, long / short press, weapons, SOI etc. So, we cover just the
easy and probably most interesting part for you: TMS up designates a target, TMS down drops it. Sounds
easy, no? Not at all, unfortunately. If we need one example why this is a study sim, here it is. Hence you
have to read and learn a lot.
The CMS switch controls the jammer and the release of counter measures (Chaffs / Flares). CMS right turns
the Jammer on, CMS down turns it off (assuming the jet is carrying a Jamming Pod).
There are 6 different release modes. Modes 1 to 4 are released with CMS up depending on the PGRM knob
position on the CMDS panel. CMS left releases program # 6.
6-126
BMS Device Setup Guide
CHANGE 1
The DMS switch manages the both MFDs (Multi Function Displays) and selects the SOI (Sensor of Interest).
It combines multiple functions depending on the master mode. DMS left cycles through the pages on the
left MFD, DMS right does that for the right MFD. On a long press (> 0.5 sec.) DMS down toggles HMCS
(Helmet Mounted Cueing System) symbology on / off (if the aircraft is equipped with that). DMS down
(short press) and DMS up are managing the SOI.
With the TRIM button you can apply trimming on the pitch (nose up / down) and roll (left / right wing
down) axis. This is especially necessary if you have an asymmetrical loadout (e.g. you dropped a single
bomb on a right wing station) or the fuel system is imbalanced. Note that trimming the jet via the stick is
only available when no autopilot is engaged and the TRIM/AP DISC switch on the Manual Trim panel is set
to the NORM position.
6-127
BMS Device Setup Guide
CHANGE 1
The MAN RNG knob includes a button (Uncage). When the button is depressed it can do a couple of things:
It removes the protective cover from Maverick seekers, toggles the seeker of an AIM-9 (Infrared air to air
missile) between Cage and Uncage (uncage allows the seeker to move and track targets) and it can
declutter the HUD in Nav (Navigation) master mode.
The knob changes the terrain intensity (gain) in A-G radar modes and the FoV in TGP TV mode.
The dogfight switch offers you a quick way to go to air to air combat no matter in which situation you are.
For example it is the fastest way to get from air to ground combat to air to air. The dogfight switch offers
two air to air master modes. On the aft position you get into the dogfight mode which is for close combat
situations. The forward position brings you into the MRM (Medium Range Missile) mode which is your
choice in medium to long range combat scenarios. The middle position cancels either of the both modes.
6-128
BMS Device Setup Guide
CHANGE 1
The RDR Cursor includes a button (Cursor Enable). When the button is depressed it toggles between AGM-
65 Maverick submodes or sets the air to air missile to Bore (Boresight = Weapon seeker) or Slave (radar).
The cursor slews the radar cursor and seekers (e.g. Maverick, TGP).
The Antenna Elevation tilts the radar elevation up / down. You can change the search altitude at the radar
cursor position defined by an upper and a lower elevation.
6-129
BMS Device Setup Guide
CHANGE 1
This simply opens (aft position) and closes (fwd position) the speedbrake boards on the jet. It takes about
two seconds to open and six seconds to close them.
When moving the switch to the up / down positions you transmit either on UHF (up) or VHF (down). The
left / right positions manage the datalink.
Reset Trim:
There is no such function in the cockpit. In real life you would have to set the trimming back manually (the
same way you trimmed the jet). However, this is a pure user convenience function to give you a quick way
to reset the trimming without much hassle.
6-130
BMS Device Setup Guide
CHANGE 1
Eject:
However, this function requires a long button press (>1 sec.) to trigger the event. You also have to verify
that your seat is armed. Happy parachuting!
Idle Detent:
The Idle detent puts your throttle position from Cutoff (engine off) to Idle (Engine idle) position and vice
versa. It is important to stick to the correct procedure to avoid problems while staring the engine.
ACMI Recorder:
ACMI (Air Combat Maneuvering Instrumentation) is an important tool to review your mission and your own
pilot performance. It records every detail of a flight and allows you to analyse it. ACMIs are stored in the
…/User/ACMI folder.
6-131
BMS Device Setup Guide
CHANGE 1
Wheel Brakes:
Unless you are not using decent rudder pedals which give you the opportunity of using differential breaking
you can use this callback for that. Note that differential breaking is not available then.
Slap Switch:
The slap switch runs countermeasures program 5. It sits next to the throttle.
When you slew the ground cursor it will also shift the position of all steerpoints. To reset that you have to
use Cursor Zero, this is usually done by pressing OSB #9 in the A-G FCR. However, you can do this also with
this callback.
This lowers (AFGearDown) and retracts (AFGearUp) the landing gear. There is also a toggle available to do
this.
6-132
BMS Device Setup Guide
CHANGE 1
This sets the parking break (discrete on/off or toggle) of the jet. The parking break is automatically released
above roughly 83% RPM (Rounds per Minute).
This switch in CAT III position stets an AOA (Angle of Attack) limit depending on the loadout (e.g. bombs,
wing tanks are carried) to prevent damages to the jet. CAT I is for pure A-A loadout and has no limits.
Refuel Door:
ICP Modes:
With these you can enter the A-A / A-G and Nav master modes.
6-133
BMS Device Setup Guide
CHANGE 1
In the “Pan” cockpit you can smoothly rotate the view while in the “Snap” pit you have fixed snapviews.
These are callbacks to rotate the view. It does work in 3d pit and in external views. Note that if you use a
TrackIR the view can’t be changed with these callbacks.
Nightvision Goggles:
Helmet Visor:
6-134
BMS Device Setup Guide
CHANGE 1
Look Closer:
This changes the FOV (Field of View) to 20°. It can be considered as a zoom function.
Recenter TrackIR:
Usually the TrackIR is recentered with the key “F12”. BMS offers you a callback which can be mapped to a
physical device button. It works independent from the default “F12” key.
SimDoNothing:
As the callback name suggests this does simply nothing. This can be used to avoid unwanted actions e.g.
suppress default device functions.
6-135
BMS Device Setup Guide
CHANGE 1
X = Callback assignment
6-136
BMS Device Setup Guide
CHANGE 1
6.3.3 Axes:
6-137
BMS Device Setup Guide
CHANGE 1
6.3.4 Miscellaneous:
hat gelöscht:
6-138
BMS Device Setup Guide
CHANGE 1
1. Verify that all devices are connected to your computer. In case you have to, power them up to
make sure they are detected as input devices.
2. Load profiles if applicable. E.g. you have to select and load the necessary profile files via Saitek’s
Profile Launcher.
3. Start additional tools or software, e.g. TrackIR, RTTServer, RTTClient and such. In case of TrackIR you
should also verify that your device is working properly.
4. Verify you have selected the right pilots profile in the logbook -> SETTINGS FOR: Callsign
6. Verify that the devices buttons are working as expected. Just press one button per device no matter
if they are two separate DirectX devices (e.g. the Warthog) or combined (e.g. Cougar). Do this for all
devices connected.
Once you have done this a couple of times you’ll see it is not much effort. As said before, it is a good habit
to do this before every flight. If you learn about things not working in 3d it is already too late. Especially if
you are doing some multiplayer flights online and you have to back out to fix it. This is simply annoying for
other pilots.
7-139