Thrustmaster T.16000M + TWCS Keyfile
-
I think there are a couple of these floating around for the Thrustmaster T.16000M, but I wanted to create a profile which did not require any T.A.R.G.E.T. scripts to work.
This keymap utilises BMS4.34 U1’s new POV hat override functions allowing you to map both the T.16000M and TWCS POV hats to functions. It includes a shifted layer for TMS and DogFight settings with plenty of free keys for remapping if so desired. Button 11 is used for OpenTrack (or TrackIR) centering.
The file is formatted to match the files included with BMS in the Docs\01 Input Devices\03 HOTAS Setup folder, so there are plenty of comments included to help. I’d love to see this entry-level stick included in the BMS download - devs, please feel free to do so or let me know if clean-up is required.
To install:
- Go to your Falcon BMS 4.34\User\Config folder
- Edit falcon bms.cfg and add the additional lines from my add to falcon bms.cfg file
- Copy the .key file to the same folder
- Load the .key file in Falcon BMS under Setup -> Controllers
- Jump into 3D to verify all bindings (the 2D interface doesn’t show any shifted bindings)
Download here. The zip file includes PDF layout files for both the functions and the callbacks, and the required falcon bms.cfg changes to enable POV hat override.
Version 11 updates:
- Merged BMS Basic 4.36 keyfile changes
Version 10 updates:
- Added bindings for Toggle Pilot Model (B15) and Center View (shifted B11)
- Moved Visor to B14 and Night Vision to shifted layer B14
Version 9 updates:
- Updated keybindings for Falcon BMS 4.35.1
Version 8 updates:
- Added Falcon BMS 4.35 .key files and moved BMS 4.34 to another folder in the zip file
- Don’t forget the config file changes for both 4.35 and 4.34.1+!
Version 7 updates:
- TMS functions are now on the non-shifted POV hat; TRIM has moved to the shifted POV hat as it’s used less often than TMS
- Added another .key file which retains the original mappings (TRIM unshifted, TMS shifted)
Version 6 updates:
- Added dogfight cancel to shifted TBTN3
Version 5 updates:
- Added CMDS program knob step up/down to shifted layer CMS forward/aft
Version 4 updates:
- Added slap switch to shifted TBTN1 (handily next to CMS)
- Reversed dogfight and speedbrake bindings to closer match F-16 HOTAS
Version 3 updates:
- Tweaked the 3rd Party bindings to remove conflicts with BMS FLAPS and ANT ELEV Knob bindings
Version 2 updates:
- Added curve configs for falcon bms.cfg for the cursor (was too sensitive) - I recommend you disable all deadzones in both Falcon BMS and in the USB Controllers control panel in Windows
- Added MAN RANGE Knob mappings (SimRangeKnobUp/SimRangeKnobDown) to shifted layer THAT1R/THAT1L
-
Thank you, will def. take a look at it!
-
Version 2 updates:
- Added curve configs for falcon bms.cfg for the cursor (was too sensitive) - I recommend you disable all deadzones in both Falcon BMS and in the USB Controllers control panel in Windows
- Added MAN RANGE Knob mappings (SimRangeKnobUp/SimRangeKnobDown) to shifted layer THAT1R/THAT1L
-
Version 3 updates:
- Tweaked the 3rd Party bindings to remove conflicts with BMS FLAPS and ANT ELEV Knob bindings
-
Version 4 updates:
- Added slap switch to shifted TBTN1 (handily next to CMS)
- Reversed dogfight and speedbrake bindings to closer match F-16 HOTAS
-
Could not get the TWCS POV to recognize with your .cfg file settings. I copied and pasted your settings into falcon bms cfg file as is in my screenshot upload. Does it matter if I’m using Alternate Launcher to setup my controls?
Thanks,
-
Could not get the TWCS POV to recognize with your .cfg file settings. I copied and pasted your settings into falcon bms cfg file as is in my screenshot upload. Does it matter if I’m using Alternate Launcher to setup my controls?
Thanks,
I don’t think the Alternate Launcher has been updated to work with POV hat override yet, so it won’t map the second POV hat. It was one of the main reasons I did all this mapping by hand with Notepad++
The mapping is pretty straightforward - if you take a look at my .key file, you should be able to copy/paste my mappings and then just change the callbacks as you’d prefer using a text editor. I have comments all through the file which explain which button is which, the shifted layer etc. Also keep the Technical Manual on hand in case any callbacks don’t work.
-
Ok, thanks for the reply. I am a 3 day old noob to falcon bms lol. After struggling with mapping my own in the dated software, I found your mappings and was relieved lol. I will take another look at your file.
Thanks,
Miller
-
Got it to work!
-
-
I am trying to map a ‘shift key’ to the outermost red button on the throttle and am using the alt launcher. Is there a simple way to map the ‘shift’ key?
Thanks
Dave -
Sorry if I am missing something but do i simply copy the .cfg file to somewhere and as well the .key file?
thanks
Dave -
I am trying to map a ‘shift key’ to the outermost red button on the throttle and am using the alt launcher. Is there a simple way to map the ‘shift’ key?
Thanks
DaveMy .key file already has this mapped
A new version of the Alternate Launcher was just released which fixes a few issues with mapping Pinky Switch (DX SHIFT). Try with the latest version.
Sorry if I am missing something but do i simply copy the .cfg file to somewhere and as well the .key file?
thanks
Dave- Go to your Falcon BMS 4.34\User\Config folder
- Edit falcon bms.cfg and add the additional lines from my add to falcon bms.cfg file
- Copy the .key file to the same folder
- Load the .key file in Falcon BMS under Setup -> Controllers
- Jump into 3D to verify all bindings (the 2D interface doesn’t show any shifted bindings)
-
Thanks. I am using v1.5…like many just trying to get back into BMS now 4.34 so some things are odd to me and trying to remember lol. I am trying to map the top POV button on the throttle to be the views and use the POV hat on the stick for trim but it says BMS only recognizes the POV on the stick. That is why i found your post on your mapping and noticed the SHIFT button. I could use the stick POV hat for Trim and TMS as you show but can’t get the darn SHIFT to work arghh!
I will follow your instructions and fingers crossed!
thanks so much,
Dave -
Thank you. From what I read above I did the following. I went to:
Falcon BMS 4.34\User\Config folder (opened it in notepad)
I opened your add to_falcon bms.cfg file and copied the few lines of code and pasted them into the config folder.
I opened your .key file in notepad, copied all items and pasted them into the cfg. folder. ( or should i have just pasted the .key ‘folder’ into the cfg file?)
Do i need to go through autolauncher to load .key file (your #4) or directly into falcon thru it’s setup?
sorry but struggling a bit.
Dave -
I think I’ve got it (or at least a hybrid lol). Will do more testing tonight.
Thanks
Dave -
Thank you. From what I read above I did the following. I went to:
Falcon BMS 4.34\User\Config folder (opened it in notepad)
I opened your add to_falcon bms.cfg file and copied the few lines of code and pasted them into the config folder.
I opened your .key file in notepad, copied all items and pasted them into the cfg. folder. ( or should i have just pasted the .key ‘folder’ into the cfg file?)
Do i need to go through autolauncher to load .key file (your #4) or directly into falcon thru it’s setup?
sorry but struggling a bit.
DaveYou’d need to add the lines to the Falcon BMS 4.34\User\Config\falcon bms.cfg file at the end.
The .key file should be copied straight into the Falcon BMS 4.34\User\Config folder.
You don’t need to do anything in the Alternative Launcher - instead load my .key file directly in Falcon BMS.
The Alternative Launcher overwrites and uses the BMS - Full.key file. I’m not sure, but I think it will also update/change falcon bms.cfg to load that key file on launch.
If you want to use my mappings, I’d suggest going back to the vanilla launcher, then follow the steps in the first post.
If you want to use the Alternative Launcher, I’d suggest just manually mapping everything through there.
-
Version 5 updates:
- Added CMDS program knob step up/down to shifted layer CMS forward/aft
-
I have the T.16000M + TWCS and Saitek Rudder Pedals, installed and loaded the keyfile and edited the config as described.
However none of the key or axis bindings are configured in the way those PDFs describe?
-
I have the T.16000M + TWCS and Saitek Rudder Pedals, installed and loaded the keyfile and edited the config as described.
However none of the key or axis bindings are configured in the way those PDFs describe?
You’ll need to configure the axes yourself within BMS (they’re not saved in the keyfile) - Setup > Controls > Advanced.
