DX
-
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
-
Indeed the normal DX limits apply of 1 POV, 32 buttons, and 8 axes for the “Thrustmaster Combined” device. How many real controllers you stuff into the TARGET device determines how crowded it is. You can put in the joystick and throttle, throttle only, joystick only, or even the joystick+throttle+cougar+TM1600+LMFD+RMFD. I guess technically you could exclude all controllers and just make it do scripted actions at random times :P.
All devices not included (or not not excluded) in TARGET behave au naturale as whatever config the drivers has for them. If you challenged me to use Falcon BMS without TARGET (Foxy is the Cougar equivalent) I could but I would miss the flexibility to make the friction slider axis into the gear lever and stuff like that.
-
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.
+1
No software is best if possible. -
Finally got the airbrakes working. But a new problem. Below I’ve included a part of my keyfile and tmc file. Why can’t I change the steerpoint when I press H3U on the joystick? Nothing happens.
Here’s a picture of my BMS Controller setup screen showing that DMS Up is set.
keyfile:
SimTriggerFirstDetent 32 8 -2 0 0x0 -1
SimPickle 33 8 -2 0 0x0 -1
SimHotasPinkyShift 35 8 -2 0 0x0 -1
SimMissileStep 36 8 -2 0 0x0 -1
SimTMSUp 38 8 -2 0 0x0 -1
SimTMSRight 39 8 -2 0 0x0 -1
SimTMSDown 40 8 -2 0 0x0 -1
SimTMSLeft 41 8 -2 0 0x0 -1
SimDMSUp 42 8 -2 0 0x0 -1
SimDMSRight 43 8 -2 0 0x0 -1
SimDMSDown 44 8 -2 0 0x0 -1
SimDMSLeft 45 8 -2 0 0x0 -1
SimCMSUp 46 8 -2 0 0x0 -1
SimCMSRight 47 8 -2 0 0x0 -1
SimCMSDown 48 8 -2 0 0x0 -1
SimCMSLeft 49 8 -2 0 0x0 -1
AFBrakesIn 62 8 -2 0 0x0 -1
AFBrakesOut 63 8 -2 0 0x0 -1tmc file:
MapKey(&Joystick, TG1, DX1);
MapKey(&Joystick, S2, DX2);
MapKey(&Joystick, S4, DX4);
MapKey(&Joystick, S1, DX5);
MapKey(&Joystick, H2U, DX7);
MapKey(&Joystick, H2R, DX8 );
MapKey(&Joystick, H2D, DX9);
MapKey(&Joystick, H2L, DX10);
MapKey(&Joystick, H3U, DX11);
MapKey(&Joystick, H3R, DX12);
MapKey(&Joystick, H3D, DX13);
MapKey(&Joystick, H3L, DX14);
MapKey(&Joystick, H4U, DX15);
MapKey(&Joystick, H4R, DX16);
MapKey(&Joystick, H4D, DX17);
MapKey(&Joystick, H4L, DX18 );
MapKey(&Throttle, SPDF, DX31); //Close speedbrake
MapKey(&Throttle, SPDB, DX32); //Open speedbrake -
SimDMSUp changes the steerpoint? I did not know that.
-
@jc1:
Finally got the airbrakes working. But a new problem. Below I’ve included a part of my keyfile and tmc file. Why can’t I change the steerpoint when I press H3U on the joystick? Nothing happens.
Here’s a picture of my BMS Controller setup screen showing that DMS Up is set.
keyfile:
SimTriggerFirstDetent 32 8 -2 0 0x0 -1
SimPickle 33 8 -2 0 0x0 -1
SimHotasPinkyShift 35 8 -2 0 0x0 -1
SimMissileStep 36 8 -2 0 0x0 -1
SimTMSUp 38 8 -2 0 0x0 -1
SimTMSRight 39 8 -2 0 0x0 -1
SimTMSDown 40 8 -2 0 0x0 -1
SimTMSLeft 41 8 -2 0 0x0 -1
SimDMSUp 42 8 -2 0 0x0 -1
SimDMSRight 43 8 -2 0 0x0 -1
SimDMSDown 44 8 -2 0 0x0 -1
SimDMSLeft 45 8 -2 0 0x0 -1
SimCMSUp 46 8 -2 0 0x0 -1
SimCMSRight 47 8 -2 0 0x0 -1
SimCMSDown 48 8 -2 0 0x0 -1
SimCMSLeft 49 8 -2 0 0x0 -1
AFBrakesIn 62 8 -2 0 0x0 -1
AFBrakesOut 63 8 -2 0 0x0 -1tmc file:
MapKey(&Joystick, TG1, DX1);
MapKey(&Joystick, S2, DX2);
MapKey(&Joystick, S4, DX4);
MapKey(&Joystick, S1, DX5);
MapKey(&Joystick, H2U, DX7);
MapKey(&Joystick, H2R, DX8 );
MapKey(&Joystick, H2D, DX9);
MapKey(&Joystick, H2L, DX10);
MapKey(&Joystick, H3U, DX11);
MapKey(&Joystick, H3R, DX12);
MapKey(&Joystick, H3D, DX13);
MapKey(&Joystick, H3L, DX14);
MapKey(&Joystick, H4U, DX15);
MapKey(&Joystick, H4R, DX16);
MapKey(&Joystick, H4D, DX17);
MapKey(&Joystick, H4L, DX18 );
MapKey(&Throttle, SPDF, DX31); //Close speedbrake
MapKey(&Throttle, SPDB, DX32); //Open speedbrakeSimDMSUp changes the steerpoint? I did not know that.
It did when I used CH Products joystick. Here’s the relevant code from my keyfile when I used CH stick.
Hat 2
SimDMSUp 8 -1 -2 0 0x0 0
SimDMSRight 9 -1 -2 0 0x0 0
SimDMSDown 10 -1 -2 0 0x0 0
SimDMSLeft 11 -1 -2 0 0x0 0Just got Thrustmaster and want to write my own tmc file. Anyway what joystick button on Thrustmaster changes the steerpoint?
-
DMS shouldn’t change the steerpoint. TMS up with the HSD cursors over a flight plan dot does though.
-
@jc1:
…. what joystick button on Thrustmaster changes the steerpoint?
Dunno. I’m not saying that you’re wrong …. I’m saying ‘I did not know that.’ I’ve never used DMS Up to change steerpoints and did not know it could be done.
Now, to be persnickety, ‘buttons’ do not change steerpoints, or anything else. Buttons call commands; commands change things (steerpoints or whatever). In the end, it’s not ‘what button’ that is important, but ‘what command’.
-
DMS shouldn’t change the steerpoint. TMS up with the HSD cursors over a flight plan dot does though.
When I used CH, I could change steerpoints with DMS Up. So what does Thrustmaster DMS Up do? And, I thought TMS up targeted, at least it did with CH and still does for me with Thrustmaster. BTW, Frederf, do you use a Cougar or a Warthog. I use Warthog.
-
@jc1:
What does DMS Up do? And, I thought TMS up targeted.
x:\Falcon BMS 4.33\Docs\Falcon BMS Manuals\TO-BMS1F-16CM-1.pdf Page 54.
-
Dunno. I’m not saying that you’re wrong …. I’m saying ‘I did not know that.’ I’ve never used DMS Up to change steerpoints and did not know it could be done.
Now, to be persnickety,
Who cares?
-
JC1;
Maybe you used the wrong key command for DMS. Up/DN/L/R should change what page your MFD is on or what display is the system point of interest. CH allows you to have 32 buttons mapped on the stick or throttle device each, I use the Fighterstick usb. I can change the mode of the stick which allows me to access all 32 buttons, even though the stick only has 20 buttons & 3 axis. 4 of those buttons I leave to be my view;so I don’t have the trim portion set up. They claim it’s possible to have ~128 buttons on the stick but you need to script them. I have my hands full with 20 as it is, there is a rocker switch on the ICP that would allow you to change the steerpoint, perhaps that is what happened or maybe you pushed the keyboard command for steerpoint increase while using your stick. DMS up should make the HUD the SOI & give you an * in the HUD, showing you that it is the display of interest at the time. -
@jc1:
Who cares?
Sorry? Who cares about which?
If you mean my nit-picky comments about buttons vs commands, it’s hugely important to your question. “What joystick button on Thrustmaster changes the steerpoint?” There is NO answer to that question except in a single, specific context …. that is as it relates to one single keyfile. You can assign the ‘steerpoint changing command’ to many/any different button on the HOTAS. No one knows what button that might be for you or me as we might choose to put that command on different buttons.
The ‘better’ question is, “What command changes steerpoints and how do I assign that to button x on my HOTAS?”
Or, perhaps, I’ve misunderstood? Maybe I’m not ‘getting it’ and not adding value to the conversation. ??
-
x:\Falcon BMS 4.33\Docs\Falcon BMS Manuals\TO-BMS1F-16CM-1.pdf Page 54.
That didn’t help. I was not returning from VIP or VRP. My SOI was HUD.
-
I can make any button on my joystick raise or lower my landing gear if I want to. SimDMSUp should never change the current steerpoint. If a button did do that it probably wasn’t configured as SimDMSUp, but if it was then a reproduction case should be discovered as that would be a bug.
I have a Warthog.
-
I can make any button on my joystick raise or lower my landing gear if I want to. SimDMSUp should never change the current steerpoint. If a button did do that it probably wasn’t configured as SimDMSUp, but if it was then a reproduction case should be discovered as that would be a bug.
I have a Warthog.
I just got Warthog last week. Before that I use CH Products stuff and still use their pedals. With CH I could always change the steerpoint with DMS Up. My CH keyfile had the “Full” file with this at the end.
Hat 2
SimDMSUp 8 -1 -2 0 0x0 0
SimDMSRight 9 -1 -2 0 0x0 0
SimDMSDown 10 -1 -2 0 0x0 0
SimDMSLeft 11 -1 -2 0 0x0 0The bug must still be in CH. That’s why I’m still shocked that DMS Up on the Warthog doesn’t change steerpoint, and apparently is not supposed to, change steerpoints.
-
@jc1:
I just got Warthog last week. Before that I use CH Products stuff and still use their pedals. With CH I could always change the steerpoint with DMS Up. My CH keyfile had the “Full” file with this at the end.
Hat 2
SimDMSUp 8 -1 -2 0 0x0 0
SimDMSRight 9 -1 -2 0 0x0 0
SimDMSDown 10 -1 -2 0 0x0 0
SimDMSLeft 11 -1 -2 0 0x0 0The bug must still be in CH. That’s why I’m still shocked that DMS Up on the Warthog doesn’t change steerpoint, and apparently is not supposed to, change steerpoints.
Frederf, I’ll just accept it, since I don’t have CH any more.
@jc1:
That didn’t help. I was not returning from VIP or VRP. My SOI was HUD.
Agave_Blue, Given that Frederf insists that CH Products should never have allowed me to change steerpoints, and I still can’t believe it allowed me to do that for such a long time, your reference to x:\Falcon BMS 4.33\Docs\Falcon BMS Manuals\TO-BMS1F-16CM-1.pdf Page 54. helps out.
-
@jc1:
….your reference to x:\Falcon BMS 4.33\Docs\Falcon BMS Manuals\TO-BMS1F-16CM-1.pdf Page 54. helps out.
That reference (and the TQS one around Page 27) should come close to defining what the RL HOTAS buttons do, and which BMS commands apply.
There are couple of fairly minor exceptions. For example, the HSD and TMS Up on a planned steerpoint that Frederf mentioned, is not shown. Or, for example, having cage/uncage work to declutter the HUD when gear is down.
-
That reference (and the TQS one around Page 27) should come close to defining what the RL HOTAS buttons do, and which BMS commands apply.
There are couple of fairly minor exceptions. For example, the HSD and TMS Up on a planned steerpoint that Frederf mentioned, is not shown. Or, for example, having cage/uncage work to declutter the HUD when gear is down.
Thanks, I’ll give those diagrams more scrutiny now. The person who gave me the CH keyfile must have had something changed for the SimICPnext/SimICPPrevious, SimDMSUp/SimDMSDown callbacks in order to be able to use DMS Up to change steerpoints. Since I got used to using the stick buttons to send electrical signals to the computer chips that contain the software that access the in-memory commands that drive Falcon:D, I wanted that capability in my new Warthog. I’m writing my own Thrustmaster tmc file, getting guidance from the ones put out there by Frederf, Mud, Morphine and DonLduk (thank you, guys). I now can change steerpoints with the TMS Up/TMS Down keys on my Warthog with code like this:
//Steerpoints
MapKey(&Joystick, H2U, USB[87]); //Next Steerpoint, SIMICPNext, 0x4E, ‘NumberPad +’
MapKey(&Joystick, H2D, USB[86]); //Previous Steerpoint, SIMICPrevious, 0x4A,‘NumberPad -’
in the shifted layer for the TMS keys, of course -
@jc1:
When I used CH, I could change steerpoints with DMS Up. So what does Thrustmaster DMS Up do? And, I thought TMS up targeted, at least it did with CH and still does for me with Thrustmaster. BTW, Frederf, do you use a Cougar or a Warthog. I use Warthog.
I can see where this is going…
Then just use Target to assign key strokes for what ever you think (or wont) the Stick/Throttle inputs should do.
OK your using shifted layers.
Except are are going to lose out on much of the advanced capability of a modern HOTAS ?
Im not much for shifted layers & have never used Target scripting.