Thrustmaster T.16000M + TWCS Keyfile
-
Is there a button mapped that will allow the radio to follow the preset ladder? For example starting with Ground on UHF 2, then click a button to cycle up through the presets to UHF 3 and so on and then click a button to cycle down through the same presets. Mainly for take-off and landing so you don’t have to take your hand off the joystick to use the ICP?
I don’t use a TrackIR or microphone so I have to use mouse or keyboard but I think by using COMMS UP-UHF seems to be the one but I can’t seem to get it to follow the presets…just gives me a Mike transmit sound?Thanks
dave -
Is there a button mapped that will allow the radio to follow the preset ladder? For example starting with Ground on UHF 2, then click a button to cycle up through the presets to UHF 3 and so on and then click a button to cycle down through the same presets. Mainly for take-off and landing so you don’t have to take your hand off the joystick to use the ICP?
I don’t use a TrackIR or microphone so I have to use mouse or keyboard but I think by using COMMS UP-UHF seems to be the one but I can’t seem to get it to follow the presets…just gives me a Mike transmit sound?Hey Dave. COMMS UP is actually the HOTAS COMMS hat moving “up” - it activates transmit on the UHF radio.
To move up the comms ladder, you normally use the SimICPNext/SimICPPrevious keybindings (Numpad keys + and -). That’s assuming the UHF radio field is selected on the DED.
If you’d like to bind this on your HOTAS, you could do so by editing the .key file in a text editor. Scroll down to the bottom and find the bindings you want to change (will probably have to be the SHIFTED layer).
For example, to set THAT1U and THAT1D (see the PDFs in the zip) to ICP Next/Previous, you’d add that to the lines like below:
# THAT1U (Win DX39 = BMS DX 38+256 = BMS DX294) SimICPNext 294 -1 -2 0 0x0 -1 # THAT1D (Win DX41 = BMS DX 40+256 = BMS DX296) SimICPPrevious 296 -1 -2 0 0x0 -1
Explanation:
- The lines beginning with # are comments to help understanding the .key files (they are ignored by BMS and removed it you bind any keys through the BMS interface - not recommended as it cannot handle the shifted layer)
- On the mapping lines, the first item is the callback to map (SimICPNext or SimICPPrevious in this case)
- Then the key to map to that callback (see the comments line for an explanation on the calculation)
- Then the rest of the line for my mappings is always: -1 -2 0 0x0 -1 (see the technical manual for an explanation of all of these values if curious)
Hope that helps!
-
Ahh I get it - thank you so much for your time and concise answer. I will give that a go tonight - fingers crossed lol.
One more if you have time;
I did a fresh install and I used your files as I did originally but there is one item I can’t for the life of me figure out. I had it set prior to fresh install but now it’s a pain for me. I am trying to set the small rotary wheel on the throttle (by the pinky - I believe TANT) to be the zoom for the TGP targeting pod. I had it set to zoom in for the Wide View and then as well when Narrow Selected it would allow zoom in picture in the MFD TGP mode. I am at a loss for how I set that. Might you offer a suggestion? is it in the avionics?
Thanks again very much, Stay well with all the world in a bit of turmoil…
Dave -
No problem.
That’s under Setup > Controllers > Advanced > Avionics, and the Range Knob axis. You’ll have to change the view zoom axis to Keyboard to be able to change this.
On my HOTAS setup, I have shifted THAT1R/THAT1L for the Range Knob because I use the rotary to zoom view - if you wanted to you could remap shifted THAT1R/THAT1L to the FOVIncrease/FOVDecrease buttons, or set one to FOVToggle (“VIEWGEN: Look Closer - Toggle”).
-
Thank you very much, I do appreciate your help.
I truly hope everything in your part of the world is as good as it can be and you and your family and friends are safe and healthy.
I am located in North Bay, ON Canada which is about 220 miles straight North of Toronto.
Cheers,
Dave -
And the same to you and yours. Stay safe and fly some Falcon
-
Thank you…but more importantly I have also lost the ability to rotate the course pointer and heading bug on the HSI with my mouse wheel. I get the ‘rotate arrows’ over the buttons but as I use the mouse wheel to zoom in and out, i have to right click or left click now to move the nav. pointer (one degree at a time). I used to be able to hover over either button and just rotate the wheel one way or the other to move the heading bug…
-
Hey there. My TWCS POV hat input does not get recognized using the current 1.51 alternative launcher. Anything else I need to edit for the pov hat to work?
-
Hey there. My TWCS POV hat input does not get recognized using the current 1.51 alternative launcher. Anything else I need to edit for the pov hat to work?
You’ll have to check with the Alternative Launcher developer. My keyfile and settings are not guaranteed to work with the Alternative Launcher (it uses the Falcon BMS - Full.key file I believe). I don’t know if it supports the multiple hat options.
-
Hey there. My TWCS POV hat input does not get recognized using the current 1.51 alternative launcher. Anything else I need to edit for the pov hat to work?
Mine does - maybe start off with a fresh new keyfile? ALT launcher only uses the BMS full.key file.
Make sure that in game that your using the full keyfile too by default and it’s not loading another custom one associated with your saved settings.
-
Okay thank you guys. Will check it out. I was using the profile here but modified it a little in the alternative launcher to my personal liking.
-
I tried to use the Alt launcher until I found Orffen’s work and just did as he said and my controls are bang on…search back to the messages in this post for the how-to’s…you won’t be disappointed.
dave -
Thanks Orffen! I’d struggled for ages trying to get my controls set up but your config has given me a leg up. It’s a shame the axes aren’t defined (not your fault) as this foxed me when I first started and it seems like you have to set them up in a specific order (stick before throttle) otherwise you end up with the throttle mini stick controller pitch and roll!
This should be rolled into the next patch so that it’s there for other folks who might have been burned trying to set up their controllers.
-
Version 6 updates:
- Added dogfight cancel to shifted TBTN3
-
Version 7 updates:
- TMS functions are now on the non-shifted POV hat; TRIM has moved to the shifted POV hat as it’s used less often than TMS
- Added another .key file which retains the original mappings (TRIM unshifted, TMS shifted)
-
Version 7 updates:
- TMS functions are now on the non-shifted POV hat; TRIM has moved to the shifted POV hat as it’s used less often than TMS
- Added another .key file which retains the original mappings (TRIM unshifted, TMS shifted)
Do you ever find trim gets stuck when using it as a shifted state. This used to happen to me in 4.33 a lot… Don’t know if 4.34 it works better with shifted states.
In 4.33 if you didn’t “unshift” in the correct order then the trim would be stuck “running” to maximum, which got pretty funky.
-
Thank you for continuous efforts!
when I first started and it seems like you have to set them up in a specific order (stick before throttle) otherwise you end up with the throttle mini stick controller pitch and roll!
Have you tried swapping the devices in the DeviceSorting.txt and putting the Stick on top and the throttle below?
That fixed all the issues I had with getting it to work.
-
Hoping someone can point me in the right direction. After loading the BMS-BasicDX TM Warthog.key and pasting it into user/config file, loading the keyfile, I am unable to takeoff. Either my stick works or my thrust works depending on what is selected in the drop down in Setup. After selecting advanced, I’ve set Flight Control Throttle Axis to Warthog Throttle, Pitch Axis to Joy Y, and Roll Axis to Joy X. Both inputs in advanced DO respond to my inputs, but once I back out to the setup page, the x/y axis thrust only works if the thrust is selected in the drop down, at which point I get no stick movement and vice versa.
-
Do you ever find trim gets stuck when using it as a shifted state. This used to happen to me in 4.33 a lot… Don’t know if 4.34 it works better with shifted states.
In 4.33 if you didn’t “unshift” in the correct order then the trim would be stuck “running” to maximum, which got pretty funky.
I haven’t noticed it recently, but I think this is still the case. When I first created the .key file, I had miscalculated the shifted DX numbers, so the pinky shift mapping came on when the button was pressed, but didn’t come off. As a result the shifted layer got stuck on.
-
Hoping someone can point me in the right direction. After loading the BMS-BasicDX TM Warthog.key and pasting it into user/config file, loading the keyfile, I am unable to takeoff. Either my stick works or my thrust works depending on what is selected in the drop down in Setup. After selecting advanced, I’ve set Flight Control Throttle Axis to Warthog Throttle, Pitch Axis to Joy Y, and Roll Axis to Joy X. Both inputs in advanced DO respond to my inputs, but once I back out to the setup page, the x/y axis thrust only works if the thrust is selected in the drop down, at which point I get no stick movement and vice versa.
I see the same behaviour - electing a different controller in the drop down removes the axis mappings for my throttle.
Re-map your axes in Advanced, then don’t touch that dropdown - the pitch/roll and thrust axis should all respond as you’d expect.