Mapping TM WH hat switch?
-
My pov on th warthog:
SimTransmitCom1 1 -1 -3 0 0x0 -1
SimCommsSwitchRight 1 -1 -3 2 0x0 -1
SimTransmitCom2 1 -1 -3 4 0x0 -1
SimCommsSwitchLeft 1 -1 -3 6 0x0 -1 -
@jc1 said in Mapping TM WH hat switch?:
@Icer What is the advantage of using DX assignments instead of TARGET script?
I’ll try to be more clear.
The TARGET script I use simply gives a DX# to each and every hat/switch position on the Warthog Throttle and renames it “THRUSTMASTER COMBINED DX128” (which I could change if I wanted) . The “stock” setup uses only DX#1-DX#32, which are simply not enough numbers to cover every possible switch/hat position. The TARGET script allows DX#1-DX#128 and assigns a DX# for everything (I believe about 46 are used). That’s all it does.In the past I would not use TARGET for BMS as BMS simply didn’t allow for anything above DX#32 and Alt Launcher has a “Release” function that can be used to cover the “dead” switch position. Works great, but as I use the TARGET script for many other sims (IL-2 and DCS are two) it was a minor inconvenience to shut down TARGET every time I switched to BMS.
With AL 2.1 and 4.36’s allowing for DX# up to 128 this is no longer an issue, and with 5 minutes of re-assignments in AL 2.1 I was up and running .
So to your question, there is no “advantage” to using DX assignments vs. the DX128 TARGET script, as you ARE using DX assignments with the TARGET script, all it does is make more DX# numbers available to the throttle… HTH
-
@Icer Following up. Are you using the DX128 script as your TARGET tmc, executing TARGET, and then allowing AL to make your key assignments?
-
@jc1 said in Mapping TM WH hat switch?:
@Icer Following up. Are you using the DX128 script as your TARGET tmc, executing TARGET, and then allowing AL to make your key assignments?
Yes, it’s WarthogThrottleALLSwitchPos.tmc file (and you need targetdx128.tmh in the folder also). I have the script running all the time now (Start script editor, Open WarthogThrottleALLSwitchPos.tmc , hit “run”, minimize, done) and simply use AL’s simple assignment procedure to assign each switch/hat/button position as they ALL now have a DX# set… I do nothing in BMS Setup or anywhere else.
-
@Icer I tried “DCS DX128.tmc” and targetdx128.tmh from github. AL will not assign any key to my Warthog joystick POV. Nor will it assign a throttle idle position on my Warthog throttle although it does assign the AB detent to the throttle. Got any clues why I’m having these issues?
-
@jc1 said in Mapping TM WH hat switch?:
@Icer I tried “DCS DX128.tmc” and targetdx128.tmh from github. AL will not assign any key to my Warthog joystick POV. Nor will it assign a throttle idle position on my Warthog throttle although it does assign the AB detent to the throttle. Got any clues why I’m having these issues?
I really know next to nothing about setting up a TARGET script, though when I first got this I had to modifiy it slightly and figured it out pretty quick (and don’t remember what I did). I still have the original “targetdx128.zip” file , and I would be happy to zip what I use up (Icerdx128.zip") and send it… both will contain the .tmc and .tmh files you need. I have no knowledge of the DCSDX128 script, but I can say this works perfectly for ALL hats/buttons/switches in BMS/DCS/and IL-2. Here is the original and the one I use for your convenience. Rememeber, it only acts upon the throttle, nothing else is touched…
Try Here - https://www.dropbox.com/s/i49cm8txa4kubiw/Targetdx128.zip?dl=0
and Here - https://www.dropbox.com/s/95tfa8cnjh4juu5/IcersTargetdx128.zip?dl=0 -
Greetings from Michigan!
Are you talking about using the hat switch on the back of the throttle? Not the one accessed with the thumb but the one accessed with the fore finger?
I add this to my con fig file:
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0
(I added it to both falcon BMS user.cfg and falcon bms.cfg not knowing which one I should add it too)
My joystick and throttle are 1 and 2 in my device sorting file. And I am able to program any button to it using the UI. I use the BMS keyfile editor to program the other switches on my HOTAS, I find it very simple to use. -
Hi Atlas, I have the exact setup as you. I recovered the use of the HAT switch you speak of by using Voice Attack. If you want I will try to help.
-
@Carbide yes, the one that the forefinger will rest on. See above for my config file, my devices are listed as throttle, rudder, and then joystick hence using 2 and 4.
@Kerfuffle thanks but I’d like to be able to use it even without having to use VA.
-
You could try and edit your device sorting file and put your stick 1st, throttle 2nd then rudders, mfds, and what have you and try my config setting or try:
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 1
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0I’m not sure what the “3” is in the line ‘set g_nPOV2DeviceID 3’ in my config. But if I had to guess I would say it designates the number of the hat switch. 1 would be the stick hat, 2 would be the thumb hat on the throttle, and 3 would be the index hat on the throttle. (my rudder pedals are number 3 in my device sorting list so I know it is not a reference to that) But that is a just a guess. (if someone knows what it means that info would be helpful) Also try and change that number to 2 or 1. If it is a designation of hat switches having your throttle in the 1st position in your device sorting might change what that number should be.
But I think if you change your device sorting file and use my config setting you will have success. There is an old post about this, that I can’t find, but I remember that was part of getting it to work. -
@Carbide The POV1DeviceID is the order the device as it appears in the dropdown menu inside the game, e.g. Keyboard, Joystick, Throttle, Pedals. In this case Keyboard = 1, Joystick = 2, Throttle = 3, Pedals = 4, and so on. POV1ID is which POV from that device to use. In that case the 0 is the first POV, 1 is the second POV, 2 is the third POV, and so on.
For the Warthog Joystick as second in the list (after Keyboard) and Warthog Throttle as third in the list to be assigned as POV1 and POV2 respectively you want the following:
0th POV from the 2nd device is assigned to POV1
0th POV from the 3rd device is assigned to POV2set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0 -
@Frederf said in Mapping TM WH hat switch?:
@Carbide The POV1DeviceID is the order the device as it appears in the dropdown menu inside the game, e.g. Keyboard, Joystick, Throttle, Pedals. In this case Keyboard = 1, Joystick = 2, Throttle = 3, Pedals = 4, and so on. POV1ID is which POV from that device to use. In that case the 0 is the first POV, 1 is the second POV, 2 is the third POV, and so on.
For the Warthog Joystick as second in the list (after Keyboard) and Warthog Throttle as third in the list to be assigned as POV1 and POV2 respectively you want the following:
0th POV from the 2nd device is assigned to POV1
0th POV from the 3rd device is assigned to POV2set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0 -
Thanks to the info in this thread, I got my second POV working without needing Joytokey.
-
-
@Atlas
Hi, for what it is worth, I simply use the Alternative Launcher which makes it very easy to set up a Warthog hotas - you simply use the AL program and don’t touch the in-game HOTAS screens and you don’t touch the BMS keyfile.I found I could not bind the throttle POV out-of-the-box with Alternative Launcher 2.1.0, however I have seen no one else with complaints on this, so it appears to be just me.
I then installed and used Alternative Launcher 2.0.0 and I could bind the throttle POV and the stick POV out-of-the-box with no problems.
-