Warthog HOTAS Set-Up Help Please?

[malcolmt16]

I am new to BMS.
I have a TM Warthog T&S, and Saitek Combat Rudder Pedals and I am having no success at all in setting them up in BMS.

The app sees my Throttle as the rudder by default. I have gone into the flight controls page and re-assigned to where I believe they should be. However, when I click Apply and go into the sim, nothing. No throttle. When I go back to the Settings page, all the assignments I made previously have reset themselves.

Is there a definitive description somewhere which describes clearly how to set-up my controls please? I am tearing my hair out here!! :mad:

Thanks
malcolmt16

[bullseye2]

https://sites.google.com/a/hodderweb.com/warthog/falcon-bms/home

[l3crusader]

@malcolmt16:

I am new to BMS.
I have a TM Warthog T&S, and Saitek Combat Rudder Pedals and I am having no success at all in setting them up in BMS.

The app sees my Throttle as the rudder by default. I have gone into the flight controls page and re-assigned to where I believe they should be. However, when I click Apply and go into the sim, nothing. No throttle. When I go back to the Settings page, all the assignments I made previously have reset themselves.

Is there a definitive description somewhere which describes clearly how to set-up my controls please? I am tearing my hair out here!! :mad:

Thanks
malcolmt16

Check this post, you should be ok.

What are you using to config your Warthog ? Do you have a TARGET script ?

[malcolmt16]

Thanks for the help guys. I will read the posts you suggest.

I am using only BMS to config the Warthog and i am not (as far as I know) using a TARGET script.

Sorry to appear naive, but I just expected the WH to work off the bat like DCS!!

[l3crusader]

@malcolmt16:

Thanks for the help guys. I will read the posts you suggest.

I am using only BMS to config the Warthog and i am not (as far as I know) using a TARGET script.

Sorry to appear naive, but I just expected the WH to work off the bat like DCS!!

Ah, BMS is a bit less user-friendly, at least on this point :mrgreen:

Normally, if you plug your HOTAS in, you should see the throttle and stick axis on the Setup page -> controlers -> Flight/avionics.
Beware of something though, if an axis is assigned somewhere, you wont see it in the list for another function.

The post I linked will be useful to you to save the axis config. If you always start BMS if your devices plugged, normally, you dont need it ; but if once you dont have them plugged, you will lose the config.

[malcolmt16]

Thanks for the advice, but still having absolutely no success with this.
I have amended the Devices file, but to be honest I am not sure my entries are correct and I can find no guidance on this anywhere.

All I can manage now is either the throttle active OR the joystick, NEVER both together. No settings seem to save on the set-up pages no matter how many times I select apply/ save.

I just want to fly the aircraft, not configure or program controllers! Why is it so bloody complicated??!!

[Sarge55]

Try using Morphine’s profile (or one of the other great profiles). Why try re-inventing the wheel? I’m a noobie to BMS and it took me about 30 minutes to be up and running…

https://www.benchmarksims.org/forum/showthread.php?8147-Morphine-s-Profile

If you have any issues just search his thread, if that doesn’t help then post your question and you’ll get some help pretty quick.

[EggsNFries]

Why is it so bloody complicated??!!

Relax buddy, it actually isn’t. What did you try so far? What profile are you trying to use? bullseye2 pointed you to Morphine’s excellent profile. The readmes given by Morphine are succinct and make setting up the profile quite easy. Essentially, the steps for first setup are:

• open TARGET script editor and load the .tmc that comes along with the profile
• now run the script in TARGET script editor
• start BMS and load the keyfile in the controls options
• make all axis assignments as given by Morphine
• once everything is set, exit BMS
• now go to the ./user/config directory located in your BMS install
• there you’ll find two files: axismapping.dat and joystick.cal
• make these files read-only (BMS will otherwise overwrite your settings)

now all that needs to be done everytime before starting BMS is to start TARGET script editor, load the tmc, and run the script

Hope that helps!
Eggs

P.S.: sometimes Windows likes to reassign the order of USB devices. This seems to be a rather rare occassion, but if it happens the DX key assignments are shifted as well. But I guess this isn’t your problem. However, if you encounter the key assignments to be all mixed up, Windows is doing what it likes to do from time to time: being somewhat of a PITA every now and then.

[malcolmt16]

Apologies gents for being a little frustrated, but I spent a couple of hours getting no where earlier. :neutral: Many thanks for your help.

I will give your suggestions a try tomorrow now as it is late.

Regards
malcolmt16

[malcolmt16]

Success! Thanks everyone for your help and patience.

[l3crusader]

Good to know

Did you use Morphine’s file ?

If yes, dont hesitate to get used to TARGET script functions, this way, you can fine tune your script to your needs.

Here’s the guide for TARGET scripting, everything is explained here :
http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_Script_Editor_Basics_v1.5_ENG.pdf

[EggsNFries]

Great!

Happy hunting!

[Vctpil]

Hi,

I also have so much problems to configure BMS with the Warthog.

In BMS, if I use the BMS.key, I can’t program the datalink, and if I use Keystroke.key, I can’t program the NWS ! In the both cases, I can’t program the MRM/DF Override Cancel function.

Yes, it is so ****ing complicated. I don’t know know how many hours I spend trying to program correctly my Warthog already;

Thanks to Morphine for the profile, but some functions show on the BMS Dash-1 pages 26-27 and pages 51-52 are not on the profile (IFF instead of Datalink on the throttle for example). And I have no idea how to program the Warthod with a script (I tried already, but I don’t understand anything about it).

Anyone has a profile corresponding to the BMS Dash-1 book ?

Thanks,
Vincent

[Gearbox]

What the mic switch is labeled as doesn’t matter, it’s left and right instead of IFF in and out (or the reverse, I forget)

I was recently going through exactly what you are, here is what got me working 100%.

You have to use the Warthog_DX.key file or whatever it is called that comes with Morphine’s profile, or adjust your own keyfile to match its assignments.

You have to verify your DX assignments. The stick has to be device 1 and the throttle has to be device 2. Pedals can be whatever but I have them as device 3.

You can use the JoyIDs utility to view dx number assignments and re-assign them. I have the utility in a stack of icons on my desktop that serve as my falcon launch checklist.

So to get working:

1. Use JoyIDs to fix your assignments first. Stick 1, Throttle 2, Pedals 3.

2. Run the target script in the target script editor. You should hear some usb device plugging and unplugging sounds, and in JoyIDs the stick and throttle will vanish and Thrustmaster Combined should appear as #1

3. Launch falcon and go the controls section. Set it to use the warthog_dx keyfile.

4. Go to the avionics and flight controls pages and set them to match the screen shots supplied with the profile

5. Test everything. If it’s all working to your satisfaction, there are a couple of files in the config folder that should be set to read-only to prevent the axis assignments from getting busted if you open falcon without having run the target script. I don’t remember their names offhand though, I can add them later.

[Gearbox]

Oops, you can download JoyIDs here: http://theairtacticalassaultgroup.com/forum/showthread.php?t=13009

[Shadow]

@Vctpil:

Hi,

I also have so much problems to configure BMS with the Warthog.

In BMS, if I use the BMS.key, I can’t program the datalink, and if I use Keystroke.key, I can’t program the NWS ! In the both cases, I can’t program the MRM/DF Override Cancel function.

Yes, it is so ****ing complicated. I don’t know know how many hours I spend trying to program correctly my Warthog already;

Thanks to Morphine for the profile, but some functions show on the BMS Dash-1 pages 26-27 and pages 51-52 are not on the profile (IFF instead of Datalink on the throttle for example). And I have no idea how to program the Warthod with a script (I tried already, but I don’t understand anything about it).

Anyone has a profile corresponding to the BMS Dash-1 book ?

Thanks,
Vincent

You need to program some/many of the functions using a direct in game method not the Target “virtual keyboard” it just wont work.

These will be controls like Missile step/NWS com sw & TMS, anything that has advanced functionality.
I use a modified keystroke I carried over from AF, and have continued to move much over to DX utilization.

[Frederf]

@Vctpil:

Hi,

I also have so much problems to configure BMS with the Warthog.

In BMS, if I use the BMS.key, I can’t program the datalink, and if I use Keystroke.key, I can’t program the NWS ! In the both cases, I can’t program the MRM/DF Override Cancel function.

Yes, it is so ****ing complicated. I don’t know know how many hours I spend trying to program correctly my Warthog already;

Thanks to Morphine for the profile, but some functions show on the BMS Dash-1 pages 26-27 and pages 51-52 are not on the profile (IFF instead of Datalink on the throttle for example). And I have no idea how to program the Warthod with a script (I tried already, but I don’t understand anything about it).

Anyone has a profile corresponding to the BMS Dash-1 book ?

Thanks,
Vincent

First thing I notice is using BMS.key or keystroke.key. What you really want is Vctpil.key. The default .key files are like huge reference books like a dictionary or encyclopedia. In the end you want a personal diary, a key file that belongs to you and only you. It won’t have to be the 1000+ lines (mine is <150 lines) of the reference .key files and you can label commands to your preference. Second is that .key files are as personal as the people who wrote them and BMS.key and keystroke.key are no exceptions. The exact same callback will have different text labels in different key files. “IFF Out” and “Comm Switch Left” are both the exact same function with different names. “Missile step” and “Nose wheel steering” are the same thing too. To even further complicate matters there are even callbacks which are functional duplicates of each other due to the development history of BMS.

You’re not going to find a TARGET script that does the default keyboard keystrokes emulated or if you do find one, you won’t like it. The default keyboard commands use all manner of shift this and ctrl that which would easily conflict. With TARGET scripting being so powerful that it’s a shame to throw away that amazing potential to make the control link between the physical controls and the game engine as direct, robust, and natural as it can be. What you want out of a TARGET script is the best outputs possible as if you had the perfect joystick controller before you make the first control setting.

My suggested arrangement is to run the Throttle controller through TARGET and leave the Joystick controller as a “naked” device. The reason is due to the 8-axis, 32-button limit for DirectX so you can get the maximum out of the throttle controller. When you enter the BMS setup screen, the controller you select from the drop down menu is the primary controller. This must be the controller that has your pitch-bank axes on it. The other functions like throttle and rudder won’t work at this stage. Don’t worry about it! They will work in this summary display after they are configured in the advanced tab. Do not change the controller in this drop down menu in an attempt to get the rudder and throttle working.

Before you begin binding anything, load up BMS.key and then save it as a new filename, Vctpil.key for example. From now on only work on Vctpil.key. Let BMS.key be a backup reference file. Feel free to open Vctpil.key in Notepad.exe and delete entire lines and rename text labels (between quote marks). It’s your key file and butcher, edit, screw up, repair it all you want. I recommend deleting lines you know you’ll never do anything but click on in the 3D cockpit. Be brutal, you can always add them back in later if you make a mistake. It’s a lot easier to work on a .key file that’s shorter. Another tip is every time you save your .key file, increment the number at the end Vctpil2 Vctpil3 Vctpil4, etc. This way if you screw up you can revert to the last version that worked. It also helps you verify that you’re using the latest edit.

OK, so bind the joystick. Find the line entry for trigger first detent, highlight to blue, and then press the trigger slightly to bind it. Repeat for fire gun, weapon pickle, missile step, CMS left-right-up-down, etc. You can test each function by pressing the button and the text label for that command will appear at the bottom.

[Gearbox]

@Frederf:

First thing I notice is using BMS.key or keystroke.key. What you really want is Vctpil.key. The default .key files are like huge reference books like a dictionary or encyclopedia. In the end you want a personal diary, a key file that belongs to you and only you. It won’t have to be the 1000+ lines (mine is <150 lines) of the reference .key files and you can label commands to your preference. Second is that .key files are as personal as the people who wrote them and BMS.key and keystroke.key are no exceptions. The exact same callback will have different text labels in different key files. “IFF Out” and “Comm Switch Left” are both the exact same function with different names. “Missile step” and “Nose wheel steering” are the same thing too. To even further complicate matters there are even callbacks which are functional duplicates of each other due to the development history of BMS.

You’re not going to find a TARGET script that does the default keyboard keystrokes emulated or if you do find one, you won’t like it. The default keyboard commands use all manner of shift this and ctrl that which would easily conflict. With TARGET scripting being so powerful that it’s a shame to throw away that amazing potential to make the control link between the physical controls and the game engine as direct, robust, and natural as it can be. What you want out of a TARGET script is the best outputs possible as if you had the perfect joystick controller before you make the first control setting.

My suggested arrangement is to run the Throttle controller through TARGET and leave the Joystick controller as a “naked” device. The reason is due to the 8-axis, 32-button limit for DirectX so you can get the maximum out of the throttle controller. When you enter the BMS setup screen, the controller you select from the drop down menu is the primary controller. This must be the controller that has your pitch-bank axes on it. The other functions like throttle and rudder won’t work at this stage. Don’t worry about it! They will work in this summary display after they are configured in the advanced tab. Do not change the controller in this drop down menu in an attempt to get the rudder and throttle working.

Before you begin binding anything, load up BMS.key and then save it as a new filename, Vctpil.key for example. From now on only work on Vctpil.key. Let BMS.key be a backup reference file. Feel free to open Vctpil.key in Notepad.exe and delete entire lines and rename text labels (between quote marks). It’s your key file and butcher, edit, screw up, repair it all you want. I recommend deleting lines you know you’ll never do anything but click on in the 3D cockpit. Be brutal, you can always add them back in later if you make a mistake. It’s a lot easier to work on a .key file that’s shorter. Another tip is every time you save your .key file, increment the number at the end Vctpil2 Vctpil3 Vctpil4, etc. This way if you screw up you can revert to the last version that worked. It also helps you verify that you’re using the latest edit.

OK, so bind the joystick. Find the line entry for trigger first detent, highlight to blue, and then press the trigger slightly to bind it. Repeat for fire gun, weapon pickle, missile step, CMS left-right-up-down, etc. You can test each function by pressing the button and the text label for that command will appear at the bottom.

I think the reason Morphine’s profile combines the stick and throttle into a virtual controller is so that you can pinkie-shift items that are on the throttle. Can you still do that if they are two separate devices?

[Frederf]

Pinky shift using TARGET or SimHotasPinkyShift? I honestly don’t know if you can use the naked controller’s input into your TARGET script or not so I’ll say no with a question mark for the first one. For SimHotasPinkyShift, absolutely.

But honestly a TM WH has more button’s than Allah has beard. What in Vishnu’s name would anyone be doing adding a shift layer to a TM WH in the first place?

[Morphine]

@Gearbox:

I think the reason Morphine’s profile combines the stick and throttle into a virtual controller is so that you can pinkie-shift items that are on the throttle. Can you still do that if they are two separate devices?

Yes you can still use the Pinky Shift to a second device if you set them up as separate controllers. It’s all controlled in the key file.

The reason I combined them on the original version was that I thought I might need to use some of the deadzone and curve control capabilities that TARGET has. Also, since I was using Dunc’s profile as a starting point it made it easier to make the conversion as the Cougar was also seen as one device by Windows as well.

However, I’ve also now converted my profile and keep the devices separate by only using TARGET to control the Throttle (for my Idle Cutoff code, etc.) and leave the Joystick as a pure DX device controlled by the key file.