Help me provide the ultimate T.16000M FCS HOTAS T.A.R.G.E.T. profile!
-
You might be able to code a macro with delayed modifier+key and then the reverse on release. That only half-improves things. There’s still the problem with stray modifiers interfering between virtual keyboard strokes and not having those key strokes usable for other things. The default key file has some default DX binds for 28 functions which isn’t half bad but a custom included key file is the right move.
-
Frederf and BlueRaven,
Thank you both for replying. I’m going to admit I’m getting a little lost on the particulars of modifying the .key file so, if you have a link to a reference, that would be much appreciated. To give you an idea of what I would like to do: First- I need to clear the current button command associations BMS recognizes with my TWCS and T16000. Like you said, I’ll have to learn how to manipulate the .key file. Second, I would like to be able to use a button on the TWCS (button 2 and 3) as “modifiers” so that when I hold down button 2 on the TWCS and push up on the T16 hat, it gives one command (different than if I just push up on hat without the modifier). When I say “modifier” I’m using the term as it is used in DCS controller configuration. I would like to use button 2 on TWCS to make a whole set of function assigned to any other button on the stick or throttle. I would then like button 3 to shift yet another set of commands. Lastly, I would like buttons 2 and 3 held together to render yet another set of commands to any button. This way imagine that the 4 way hat on the stick could be used to control TMS, DMS, CMS, and even COMS all by just holding one or a combination of the button modifiers. Hope that make sense. If you just look at how modifiers are used in DCS it should make sense.
Much appreciation in advance for any feedback given! So far, I love Falcon and just want to get the most out of it!
-
Most of the “key file manipulation” is to go into BMS, load the key file, scroll to the desired command, highlight, and press the joystick button. The only time you have to get out Notepad is doing anything special like on release (0x42) and SimHotasPinkyShift numbering (256) and even in those cases it’s usually small edits to lines that started life the first way.
Docs\BMS Key File Manual.pdf is the best reference I know of.
Modifiers you can do a few ways: TARGET layers, TARGET conditional code, and SimHotasPinkySwitch. Layers or S.H.P.S. make sense if you’re doing a lot of shifting, like every button. If it’s just a button or two getting multi-function then conditional is better as you can be selective (layers are global changes). I would go for probably S.H.P.S. and conditional shifting and no TARGET layers. The small details matter in layering, like if you are holding down button A and shift B to C is A’s state interrupted or not? It can be annoying if for example you are holding the AP paddle and want to shift a button to a different function and it drops your AP paddle hold by applying the shift.
Here’s an example of a conditional button:
MapKey(&Joystick, S2, EXEC( "if(Throttle[APUON]) ActKey(KEYON+DOWN+DX18);" )); //Bomb Release MapKeyR(&Joystick, S2, UP+DX18); ```Obviously this does something if a button is on and nothing if it isn't but the other cases (!APUON, APUON&&EACON, APUON&&!EACON, etc.) accessible. The annoying thing about layers if you quickly run out of buttons and since you want to include both controllers in your programming you'll have to combine them so the budget of 32 buttons runs out fast. You might have to do some keyboard emulation but if you keep it to simple key taps for rarely used functions it's no big deal. The nice thing about S.H.P.S. is it doesn't cut into your 32-button budget.
-
my goal is to provide something that works with the default “BMS - Full.key” keyfile and, as such, can be easily kept up to date and used as a template for further modified versions in the future.
I have gone for the same Idea when I made a profile for Warthog.
https://www.benchmarksims.org/forum/showthread.php?29003-Chihirobelmo-s-Profile-Never-Disappearing-Warthog-Setup-Script
YES. BMS - Full.key already has DX numbers assigned for HOTAS COUGAR and only matching device DX order to that works without editing stock keyfile.When you see “Thrustmaster Virtual Game Controller (root)” it is failing to build “Thrustmaster Combined”. It is also falling to disconnect Throttle and Stick virtually. That seems making unexpected DX order changing. Have you ever edited any TARGET system file? one of my friends did that because TARGET at the time had a problem with disconnecting devices and he changed the file not to allow TARGET to miss disconnecting devices, but that made this “Thrustmaster Virtual Game Controller (root)” problem.
-
I have gone for the same Idea when I made a profile for Warthog.
https://www.benchmarksims.org/forum/showthread.php?29003-Chihirobelmo-s-Profile-Never-Disappearing-Warthog-Setup-Script
YES. BMS - Full.key already has DX numbers assigned for HOTAS COUGAR and only matching device DX order to that works without editing stock keyfile.When you see “Thrustmaster Virtual Game Controller (root)” it is failing to build “Thrustmaster Combined”. It is also falling to disconnect Throttle and Stick virtually. That seems making unexpected DX order changing. Have you ever edited any TARGET system file? one of my friends did that because TARGET at the time had a problem with disconnecting devices and he changed the file not to allow TARGET to miss disconnecting devices, but that made this “Thrustmaster Virtual Game Controller (root)” problem.
I would love to know if someone has a solution to this, I recently got a T16000M FCS and am experiencing these issues with a fresh install.
-
Here is a profile for the 16000m+TWCS+t.flight pedals that I have been working on. Its not complete but it does have most of the major functions mapped
https://drive.google.com/file/d/0Bz8I4-5A7YFub0dYWC16RzFYZms/view?usp=sharing
-
I have gone for the same Idea when I made a profile for Warthog.
https://www.benchmarksims.org/forum/showthread.php?29003-Chihirobelmo-s-Profile-Never-Disappearing-Warthog-Setup-Script
YES. BMS - Full.key already has DX numbers assigned for HOTAS COUGAR and only matching device DX order to that works without editing stock keyfile.Thanks mate, your thread was very useful: I didn’t know you can make default assignments for axes inside DeviceDefaults.txt, good to know, I will no longer need to backup axismapping.dat.
And yes, as you say the only way to use the stock keyfile is having a DX match with the default assignments for HOTAS Cougar… unfortunately, as pointed out by Frederf, virtual keyboard emulation does not work well and it was the only chance I had to realize my original idea.I have gone for the same Idea when I made a profile for Warthog.
When you see “Thrustmaster Virtual Game Controller (root)” it is failing to build “Thrustmaster Combined”. It is also falling to disconnect Throttle and Stick virtually. That seems making unexpected DX order changing. Have you ever edited any TARGET system file? one of my friends did that because TARGET at the time had a problem with disconnecting devices and he changed the file not to allow TARGET to miss disconnecting devices, but that made this “Thrustmaster Virtual Game Controller (root)” problem.I see you have a WH: so, when you run TARGET, does it disconnect your physical devices and you only see “Thrustmaster Combined”?
I ask for a confirmation because in your thread you say that starting with U3 there is stock setup for it in DeviceDefaults.txt, but I haven’t it in mine; instead, there are a LOT of lines like this one:# Thrustmaster Virtual Game Controller (root) #GUID = {FFFF044F-0000-0000-0000-504944564944} # Now please add the axismappings for this controller here and REMOVE the '#' before the GUID inr order to activate them ! You may remove this line then.
so I think it could be an auto-generated thing; moreover, note that the GUID is the same.
So this “Thrustmaster Virtual Game Controller (root)” thing could be the way it’s meant to be for the T.16000M after all, I’ll try to engage TM tech support again in order to get a confirmation before messing with TARGET system files.Thanks again for your help!
-
With warthog it depends what controllers are not excluded. If both are included then both are hidden and the virtual device only is seen. If joystick is excluded then throttle is hidden and virtual and joystick are seen. This is true for any number. If you have 7 tm devices, included are hidden and replaced, excluded are normal.
This last way is how I do it because joystick needs no special programming and then throttle programming can have all resources.
I have seen tm combined having the wrong name (root) but there is no problem with function.
-
OK guys, I finally managed to build something working. :drink:
It’s a sort of a trick, because I exploit a TARGET “malfunction” that fails to disconnect the physical devices by using them directly via DX mappings in addition to the virtual device.
The latter is set as the third one via DeviceSorting.txt, so to easily distinguish mappings belonging to it into the keyfile; in fact they start from 64, which is exactly the first button on the third DX device.In this way I managed to use both the POV hats on the stick and the throttle - I expose them as DX buttons - and to remap the throttle rudder rocker (redundant, as you can use the stick rotation as rudder axis) for use as brakes.
This is not optimal and maybe not elegant, but it works and I think this is what matters. :mrgreen:Just follow this steps:
- Download the attached .zip archive and decompress it
- Put the .tmc TARGET script and .ttm macros file (unused at the moment, but I already had it and it can be useful as additional reference) somewhere
- Start TARGET Script Editor and run the .tmc script
- Put both DeviceSorting.txt and BlueRaven.key into your BMS config folder
- Start BMS and select BlueRaven.key as your keyfile
- Map the axes in the advanced setup options; use “Thrustmaster Virtual Game Controller (root)” entries
- Enjoy :woohoo:
The files have plenty of comments, so they should be self-explaining; should you need some clarification do not hesitate to ask.
I hope someone will try the thing out and let me know his thoughts, thanks again for your help and happy T.16000M’ing! -
This last way is how I do it because joystick needs no special programming and then throttle programming can have all resources.
+1, that’s exactly what I did (see my previous post).
In fact, I used some resources for the stick POV hat too, it seemed more logical to me to treat both with TARGET… but hey, it’s me, my mind works like this. :mrgreen:I have seen tm combined having the wrong name (root) but there is no problem with function.
I can confirm, it’s working with no hassle in my experience… so who minds the cosmetics?
Thanks again for your precious help, my friend!!! -
Hi guys, I made some minor changes to the configuration (different throttle assignments and fixed some typos here and there); please find the new 1.1 version attached.
Enjoy! -
I just ordered the throttle, but for joystick I use a microsoft ffb2. The buttons on the joystick is basically the same as the t16000. Can I still use your profile to set up the joystick, and if not I am very intressed in how your keymapping looks like.
-
I just ordered the throttle, but for joystick I use a microsoft ffb2. The buttons on the joystick is basically the same as the t16000. Can I still use your profile to set up the joystick, and if not I am very intressed in how your keymapping looks like.
Hi, I can’t tell for sure, it depends on how the FFB2 joystick exposes its buttons in terms of numbering, e.g. does the trigger match DX button 1?
If yes it will work, if not when you push the trigger another function could be activated or it could simply do nothing at all.
Apart from this, the layout of the FFB2 looks quite different from T.16000M’s one to me (far fewer buttons), so probably you’ll have just the basic stick buttons working.
In any case, my keyfile is included in the archive above, so feel free to use it as reference and modify it for your needs… should you need help do not hesitate to ask. -
Thanks for all your hard work. As a total beginner both in BMS AND the t16000 fcs I am about to give up the whole thing. Your Solution isn’t working for me somehow, most of my buttons aren’t recognized in BMS and my Windows doesn’t show “Thrustmaster Virtual Game Controller (root)” but “Thrustmaster Combined” and nothing else, wherein lies the problem I’d guess. If any of you t16000 fcs users got the damn thing working and wouldn’t mind guiding a total noob to success feel free to add me in discord “Eidolon#9207”
-
Thanks for all your hard work. As a total beginner both in BMS AND the t16000 fcs I am about to give up the whole thing. Your Solution isn’t working for me somehow, most of my buttons aren’t recognized in BMS and my Windows doesn’t show “Thrustmaster Virtual Game Controller (root)” but “Thrustmaster Combined” and nothing else, wherein lies the problem I’d guess. If any of you t16000 fcs users got the damn thing working and wouldn’t mind guiding a total noob to success feel free to add me in discord “Eidolon#9207”
Hi, you are right: you see “Thustmaster Combined”, so on your PC TARGET is working as it should and is hiding physical devices… ironically, my solution is based on it not working correctly on my PC (see this post).
So the entire DX programming in the keyfile won’t match your device and nothing will work.
I will contact you on Discord as soon as I have some spare time, feel free to ping me via PM should I forget. -
So I have the same “problem” as Eidolon in that I see Thrustmaster combined so your profile doesn’t work. What I can’t quire figure out is which POV hat you were not able to get to work before?
ETA: Looking at your files I think I can map it the same under my setup, I’ll mess around with it tonight and if it works I’ll report back. My main problem right now is figuring out which controls I should be worried about mapping, so your setup serves as a handy guide for that.
-
It’s funny. My target software suddenly decided to not hide the devices anymore, same as for BlueRaven. But the virtual device still shows as Thrustmaster Combined. For now I ditched TARGET completely and just have to live without the throttle pov.
-
So I have the same “problem” as Eidolon in that I see Thrustmaster combined so your profile doesn’t work. What I can’t quire figure out is which POV hat you were not able to get to work before?
Hi, I could not make the throttle POV hat working, because it was not on the primary device and DX isn’t able to manage it.
ETA: Looking at your files I think I can map it the same under my setup, I’ll mess around with it tonight and if it works I’ll report back. My main problem right now is figuring out which controls I should be worried about mapping, so your setup serves as a handy guide for that.
I tried to map as much of the functions you find on the real F-16 HOTAS as I could… I had to leave MAN RANGE KNOB/UNCAGE and IFF IN/OUT (comms switch left/right) out but all the rest that matters is there… hope you’ll find it useful.
It’s funny. My target software suddenly decided to not hide the devices anymore, same as for BlueRaven. But the virtual device still shows as Thrustmaster Combined. For now I ditched TARGET completely and just have to live without the throttle pov.
Sorry for your inconvenience, but then my setup should work now: have you tried it?
I was also thinking we could try to “combine” the throttle only, in order to be able to remap the POV hat and the rudder rocker so they are mere buttons (as I do now) and let BMS use the joystick as primary physical DX device… it should work, you just have to ensure that “Thrustmaster Combined” is the second one in DeviceSorting.txt.
Then we would just need to renumber the assignments in the keyfile. -
I tried to map as much of the functions you find on the real F-16 HOTAS as I could… I had to leave MAN RANGE KNOB/UNCAGE and IFF IN/OUT (comms switch left/right) out but all the rest that matters is there… hope you’ll find it useful.
So what I did was map all the keys you did to the “combined” stick TARGET provides. Instead of using the DX keys I mapped directly to the default keyboard keys from the Full keyfile. It’s probably a pretty fragile way to do it but I just wanted to see if the way I was doing it even worked. Seems to work and I’ll test it out some once I learn what the keys actually do.
Oh and I mapped the break the same way you did.
-
After many trials and tribulations I managed to get confident with the Keyfile Editor AND the Target Software. What I did was just map all buttons in Target as DX Keys, including the Throttle POV Hat and then map as usual in the Keyfile Editor. Somehow Target creates the Thrustmaster Combined again and hides everything else. Granted I reinstalled the drivers first, one for the stick and one for the throttle (which may have been the problem, initially I only installed the Stick drivers, the throttle has a different one, might wanna look into that BlueRaven).
If anyone is interested, here is my Layout, shifted functions designated with #:
http://i.imgur.com/9ekMk7l.png
and a link for the fillable pdf template:
https://www.reddit.com/r/hotas/comments/5n6kb3/tm_t16000m_fcs_hotas_tfrp_config_sheet_fillable/