Mapping TM WH hat switch?
-
The pov hat number (second part of the line -> 0 after the callback) must be one. See chapter 10.5.3, Second part: POV Hat number
-
@Kolbe-49th you mean like this?
SimTransmitCom1 1 -1 -3 0 0x0 0 # Up UHF SimCommsSwitchRight 1 -1 -3 2 0x0 0 # Right SimTransmitCom2 1 -1 -3 4 0x0 0 # Down VHF SimCommsSwitchLeft 1 -1 -3 6 0x0 0 # Left
I tried it and it still does not work for the throttle, however, those commands now work when using the stick hat (trim). I tried using 2 in case it was seen as a shifted layer hat (throttle hat) but still does not work.
-
I did some tests myself but without a second pov device. I am too lazy to dig through all my stuff in the garage
Try to set g_nPOV1DeviceID to 1 and 2nd POV to 3.
I don’t know why that is atm. but it seems the manual could be wrong here. What is strange is that I know that I tested it properly back than and it worked as described. I need to investigate this.Please report back.
-
@Kolbe-49th Okay, here’s what I’ve tried now:
set g_nPOV1DeviceID 1 // TM WH Throttle set g_nPOV1ID 0 set g_nPOV2DeviceID 3 // VPC Stick set g_nPOV2ID 0
On my .key file:
SimTransmitCom1 1 -1 -3 0 0x0 0 # Up UHF SimCommsSwitchRight 1 -1 -3 2 0x0 0 # Right SimTransmitCom2 1 -1 -3 4 0x0 0 # Down VHF SimCommsSwitchLeft 1 -1 -3 6 0x0 0 # Left
On the .key file, I’ve tried [callback] 0, [callback] 1, and [callback] 2 options and none of them work.
-
OK, I’ll try to make some serious test myself tomorrow
-
A solution for this would be great for me too. When I switched to win 11 target GUI stopped working so I spent a lot of time changing my set up to all dx buttons. I too could not get the second POV too work and rem’d the lines out.
I ended up using joy to key as a work around for the second POV. But I’d rather have the second POV work with the dx and shifted dx numbers.
-
@Kolbe-49th said in Mapping TM WH hat switch?:
OK, I’ll try to make some serious test myself tomorrow
Thanks, I look forward to your results and a possible fix.
-
@Atlas - I believe I have the same setup as you but use Alt Launcher and have had 0 issues assigning that hat (or any other one) and have added nothing to the .key file. Until today I had it assigned using the box-stock Warthog assignments and with AL 2.1 I now use a TARGET DX128 script (which I had been using in IL-2 and DCS) which assign a DX# to EVERY switch/hat/button position. Just checked and it is now DX19/20/21/22… which I assign to radar scan changes, but should be easily assigned to any keypress bind… am I misunderstanding the issue?
-
@Icer I just use the standard launcher, perhaps I should check out the alternative launcher?
Still, the manual says what I want to do is possible but unless I’m following the instructions wrong, it doesn’t seem to work.
-
@Atlas said in Mapping TM WH hat switch?:
@Icer I just use the standard launcher, perhaps I should check out the alternative launcher?
Still, the manual says what I want to do is possible but unless I’m following the instructions wrong, it doesn’t seem to work.
Personally I would get Alt Launcher and check it out, worst case you will be back scratching your head, but I doubt it. I would also advise running the TARGET script to give your Throttle a DX# for every switch position but you can use the Alt Launcher “Release” function to get around it (but why?)… The script I use ONLY programs the Throttle, nothing else, and has performed flawlessly for well over a year despite what the TARGET haters say…
-
@Icer What is the advantage of using DX assignments instead of TARGET script?
-
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.