DX
-
Can anyone say whether or not Thrustmaster software assigns DX numbers to all the buttons, switches and knobs on the stick and throttle?
-
If it does I would be impressed. Isn’t there too many buttons?
-
Hey Jc1 Target software allows Keystrokes, USB assignments, or DX assignments to all buttons or switch, a combination of all modes allowed in profile.
Weaklink
-
If it does I would be impressed. Isn’t there too many buttons?
I think you would be impressed with CH Products. I got CH Products gear and its software enables all the buttons and POV to be assigned to a DX number Then, in my keyfile after all the Full.key entries, I just assign a callback to each button or POV. I’m somehow gonna get Thrustmaster Warthog and was wondering if it would be that easy to assign the callbacks.
-
Im guessing the throttle and stick are separate devices for CH gear? And thus each get 32 DX buttons?
-
@jc1:
Can anyone say whether or not Thrustmaster software assigns DX numbers to all the buttons, switches and knobs on the stick and throttle?
jc1, all the stick is covered, the two 4 way hats & Speed Break on the Throttle.
If you run a script and then use the Device Analyzer, it will show which controls are DX
-
Im guessing the throttle and stick are separate devices for CH gear? And thus each get 32 DX buttons?
Yep
-
Hey Blu3wolf, Shadow and Weaklink. I downloaded the TARGET software from Thrustmaster and I see what you mean. It looks somewhat more complex than the CH Products way of doing things, so it must offer something way better. I’m gonna give it a good read.
-
I like it, it’s easy I use BMS Full key assignments and about 3 delay actions to effect action within profile. It has I/O–U,M, and D so plenty of room for all quick action keys, the warthog with target software is easy to program.
WeakLink
-
I like it, it’s easy I use BMS Full key assignments and about 3 delay actions to effect action within profile. It has I/O–U,M, and D so plenty of room for all quick action keys, the warthog with target software is easy to program.
WeakLink
It looks like I’ll like TARGET, too. Got experience with C, C++, C#. Now I got to get the Warthog somehow. In the meantime, got to get better at being a pilot; still haven’t refueled yet.
-
I’ve looked at 4 tmc Profiles and key files, Mud, Morphine, Frederf and DonLduk. Each has different DX numbers for AirBrakes.
Morphine
AFBrakesIn 30 -1 -2 0 0x0 0
AFBrakesOut 31 -1 -2 0 0x0 0Mud
AFBrakesOut 26 -1 -2 0 0x0 0 “Airbrakes Out”
AFBrakesIn 27 -1 -2 0 0x0 0 “Airbrakes In”Frederf
AFBrakesIn 4 8 -2 0 0x0 -1
AFBrakesOut 5 8 -2 0 0x0 -1DonLduk
AFBrakesIn 30 -1 -2 0 0X0 0 “”
AFBrakesOut 31 -1 -2 0 0X0 0 “”Where do the DX numbers come from?
-
If those have associated tmc files to go with them, then there is not necessarily a connection. You can associate any DX number on the cougar to any physical button on it, so the number can be irrelevant if it is programmed.
-
If those have associated tmc files to go with them, then there is not necessarily a connection. You can associate any DX number on the cougar to any physical button on it, so the number can be irrelevant if it is programmed.
I checked their tmc file and in it they say reference the key file or use the DX number in their tmc file. I just got this Warthog throttle so I’m not that familiar with it, yet. So I copied
//Copied from Mud
MapKey(&Throttle, SPDF, DX28 );
MapKey(&Throttle, SPDB, DX27);//Copied from Frederf
MapKey(&Throttle, SPDF, DX5);
MapKey(&Throttle, SPDB, DX6);but neither of these activates the airbrakes. There must be something else I’m missing, plus I’m wondering how did they come up with different numbers.
-
because they picked different numbers?
If Im not mistaken, those entries you pasted above tell the TM to make the speedbrakes to be DX button 27 and 28 for Mud, or button 5 and 6 for Frederf. To get that to actually do something in the game, the keyfile to accompany it would need to have the speedbrakes there assigned to either buttons 27 and 28 (for Muds TMC file) or 5 and 6 (for Frederfs file).
-
because they picked different numbers?
If Im not mistaken, those entries you pasted above tell the TM to make the speedbrakes to be DX button 27 and 28 for Mud, or button 5 and 6 for Frederf. To get that to actually do something in the game, the keyfile to accompany it would need to have the speedbrakes there assigned to either buttons 27 and 28 (for Muds TMC file) or 5 and 6 (for Frederfs file).
Mud had 26 and 27 in his key file. Frederf had 4 and 5 in his key file.
Mud’s key file
AFBrakesOut 26 -1 -2 0 0x0 0 “Airbrakes Out”
AFBrakesIn 27 -1 -2 0 0x0 0 “Airbrakes In”Frederf’s key file
AFBrakesIn 4 8 -2 0 0x0 -1
AFBrakesOut 5 8 -2 0 0x0 -1I know that BMS = DX-1, so if I look at posts #11 and #13 above, I get their numbers (Mud 28-1, 27-1 and Frederf 5-1, 6-1) , but I don’t know WHY they chose those numbers. More importantly, when I use their key file and tmc entries, it don’t work for me.
So I :rtfm::) the Thrustmaster manual and came up with this, which works for me because CTL+b and SHIFT + b are the entries on the BMS keyboard layout, and I didn’t need Mud’s or Frederf’s key file entries.MapKey(&Throttle, SPDF, CHAIN(DOWN+L_CTL+‘b’, D(), UP+L_CTL+‘b’)); //Close Airbrakes
MapKey(&Throttle, SPDB, CHAIN(DOWN+L_SHIFT+‘b’, D(), UP+L_SHIFT+‘b’)); //Open Airbrakes -
There doesnt have to be a reason to pick those numbers specifically. When using the .tmc format you can assign whatever numbers you like.
-
The numbers being a middle man are arbitrary. There are no default DX bindings by default in any of the supplied key files. You have to bind them anyway so what number is speedbrake close doesn’t matter. You click speedbrake close in Falcon, you press the switch on the handle, life goes on. The process of going from a default key file to binding all of the buttons and axes on a Warthog is a 15 minute ordeal if you’re slow. Most people supply their key files as well (although mind device order as it shifts the numbers around).
If you count all the bottoms on the Warthog throttle even 32 DX buttons doesn’t cover it all if you want to map every switch position to a number. What I’ve found lately is that the key file is capable of generating an event on a DX release. Now I can use one DX number for EAC ON and the same DX number with the release context for EAC OFF. So I bind ON to master lights on and OFF to master lights off and I only use one number for two callbacks. Using this technique I’ve gotten my script down to using only 25 DX numbers but with more workload writing the key file.
The upside of this is now I have some more DX numbers to play with. I think I’m going to bind the pinky lights switch to both change the backlighting and toggle on and off the F-16 instrument lighting (say center dark, aft flood, forward backlight).
You can program a target script to do the keyboard dance with virtual keyboard but I’ll say this now. Someday you’ll be sorry. A key will get stuck or you’ll accidentally eject or something bad will come of it. With a DX bind there’s no chance of SHIFT and CTRL andn ALT doing something funny, plus you can use the keyboard for other stuff. For example I type straight into the ICP with numpad, “F” is my fault acknowledge key, “H” is my RWR Handoff key. Space bar is master caution reset.
-
I had always assumed that the DX assignments sequence for a input device were determined by the firmware of the controller chip or its rom.
-
For TM (and I think CH?) hardware, you can set the DX numbers as you like. Saitek stuff just thinks it is programmable, but it has nothing compared to the Cougar…
And yet, its far more customizability than I forsee myself needing. I just use the DX functions within BMS, without programming the stick. No need really.
-
for the “warthog” only 32 numbers when the HOTAS works in “combined” mode. When it operates in “normal” mode the “coolie switch” of the throttle has no number because there are already 32 buttons on the throttle (the maximun for one device) and the “coolie switch” is seen as a POV
