Thrustmaster T-Flight Hotas X
-
Hi, sorry for your incident… I never experienced this behavior, but will do some testing.
As for your question, AFAIK there’s no way to remap a shifted button using the UI - you can remap unshifted layer only - so you’ll have to stick with an editor.
Nothing complicated, anyway: just search for the SHIFTED LAYER section at the end of the keyfile and modify this binding:SimEmergencyJettison 257 -1 -2 0 0x0 0 “GEAR: EMER STORES JETTISON Button - Hold”
Just change the SimEmergencyJettison call with the one you want.
Should you need further help, let me know.That’s just what I needed, thanks!
-
Glad to know you solved your problem.
An alternative approach - sorry, it just jumped back into my mind - could be adjusting the pinky tapping time, here is how to do it (extracted from the “Direct X Shifting Facility” article you can find here–- BEGIN —
Specifying the Pinky Tapping Time
The maximum pinky tapping time in milliseconds that is used to determine whether the pinky button should execute EXPAND or act as shift button can be configured within the falconbms.cfg file:
set g_nHotasShiftQuickPressTimeLimit n
The parameter value defaults to 200. If the pinky button is tapped and released within n milliseconds, EXPAND is executed. If it is not released within n milliseconds, shift is executed instead.
— END —
-
Am I missing something or does this profile lack speed brakes mapped?
-
Am I missing something or does this profile lack speed brakes mapped?
You’re right, speed brakes are not mapped because there are too few buttons and I prefer having what I consider more useful features on my HOTAS… it’s no matter for me to hit ‘b’ on my keyboard when I need them.
-
Absolutely LOVE your profile Blue Raven. I recommend it to anyone who has this stick. With clever positioning of your keyboard and some memorization, You’ll barely be hands off the controls for more than 2 seconds.
-
Absolutely LOVE your profile Blue Raven. I recommend it to anyone who has this stick. With clever positioning of your keyboard and some memorization, You’ll barely be hands off the controls for more than 2 seconds.
Thanks mate!!!
-
Blue Raven thank you so much!!! With some small changes BMS is back for me! Thank you Sir!!
-
Blue Raven thank you so much!!! With some small changes BMS is back for me! Thank you Sir!!
I am so happy my profile is helping many people enjoy BMS even with a non high-end stick… thank you all!
Just out of curiosity, which modifications did you make? -
I miss button 8 from a break in the plastic socket so I have to compromise with it. I also own an Logitech game pad with its precise axes I can move the cursor pretty well. TMS on hat switch and button 5,6 cms function. Button 7 is first trigger. 10 is NWS and 11 air brake. Your profile rly boosted the experience for me! Thumbs up!
Mig-21 Headbutter
-
how do i use this
-
how do i use this
Just put it the profile file in User\Config folder of your installation - you can name it as you like, e.g. <your callsign=“”>.key - and load it from the Controllers section of your BMS setup… did I got your question or did you mean something else?</your>
-
Hi BlueRaven,
Do you think you could modify yours so it is without TrackIR? I don’t have TrackIR and would like the views back on the POV HAT. I am also new to BMS and find the programming too confusing. Thanks.
Regards
-
Hi BlueRaven,
Do you think you could modify yours so it is without TrackIR? I don’t have TrackIR and would like the views back on the POV HAT. I am also new to BMS and find the programming too confusing. Thanks.
Regards
I still must have somewhere an old 4.32 keyfile I set up when I did not have TrackIR, too… if I am able to find it, it should not be a great effort to port the callbacks to the 4.33 keyfile.
I’ll have a look as soon as possibile, please be patient as for sure I can’t handle it before next week… but feel free to remind it to me - via PM, too - should I give you no news after a reasonable time (my memory sometimes faults these days ). -
I still must have somewhere an old 4.32 keyfile I set up when I did not have TrackIR, too… if I am able to find it, it should not be a great effort to port the callbacks to the 4.33 keyfile. I’ll have a look as soon as possibile, please be patient as for sure I can’t handle it before next week… but feel free to remind it to me - via PM, too - should I give you no news after a reasonable time (my memory sometimes faults these days ).
Thanks Raven for your help.
Btw, I tried using JoytoKey - an external HOTAS programmer which is easy to use. But the problem is, in BMS Controller Menu, I still need to select either a Full or Basic or Minimum key which contains inbuilt Hotas commands. And that kind of conflicts with the JoytoKey commands (seems like I’m getting both the keyfile and JoyToKey commands plus the Shift (pinky) command doesn’t work with Radar Cursor slewing on the POV Hat switch). I’m thinking maybe I should blank out the Hotas commands in the above key files (save under a diff name) and use it so that the HOTAS inputs come only from JoyToKey (in theory). Alternatively, maybe I should not select my T.Flight Hotas in the Controller menu and leave it all to keyboard. Then the Hotas commands will come solely from JoyToKey (in theory). I will experiment tonight. Any thoughts on this?
I’ve also used the free Keyfile Editor by SourceForge but it was designed for BMS 4.32 and seems to report many “errors”. So I think it needs to be updated before it will work with BMS 4.33U1.
I haven’t figured out how to use the included BMS Excel Keyfile Editor. It’s just too complicated. There are instructions but they assume you are familiar with the technicalities and jargon.
I’ve played F4, FF6, DCS before but never BMS. Being new to BMS, I find it complicated with confusing instructions/jargon. The biggest hurdle to getting into the sim has simply been programming my T.Flight Hotas as I think the key files were designed for better systems like the Warthog/Cougar, plus, the in-game Hotas programmer is far too basic for such a sim. BMS is definitely not a retail product but a niche sim product for the serious flight enthusiast who has kept up with BMS. I think FF6 was the sweet spot. Just my thoughts.
Cheers
-
Hi BlueRaven,
I hope you don’t mind but I have modified your BlueRaven.key file as I do not have TrackIR and came up with 6 versions (see below/attached) for non TrackIR users.
Basically, I’ve put back POV HAT panning in all 6 versions. The ‘MP’ (multiplayer) versions keep the original VHF/UHF mapping on the throttle while the ‘SP’ (single player) versions replace them with DMS functions. The ‘v2’ versions differ from ‘v1’ in that they also change the shifted Trigger and shifted Pickle buttons to SRM and MRM Overrides respectively.
SP v3 maps the antenna elevation up/down to the throttle (shifted buttons 5 and 6 respectively). The reason is that button 5 is for locking targets and a DMS left on button 5 (shifted) tends to result in an unintended change to the left MFD page. Padlock and glance forward have also been added to button 3 on the stick to improve target tracking and situational awareness in DF mode.
I also found the following posts helpful in understanding the DX mapping functions:
DirectX Shifting Facility
DX NumberingCheers!
BlueRaven POV.key
Same as original BlueRaven.key except:
- POV HAT (Unshifted) = Panning (default)
- POV HAT (Shifted) = Slew Radar Cursor // Replaces and loses the 4 DMS positions
BlueRaven POV MP v1.key
Same as BlueRaven POV.key except:
- Throttle Button 7 (Shifted) = DMS Down (change MFD SOI) // Replaces and loses CMS Down
- Throttle Button 8 (Shifted) = Toggle Jammer (J) // Replaces and loses CMS Right
BlueRaven POV MP v2.key
Same as above (BlueRaven POV MP v1.key) but adds these changes:
- Stick Button 1 Trigger (Shifted) = SRM (DF) Override // Replaces MRM Override
- Stick Button 2 Pickle (Shifted) = MRM Override // Replaces and loses Emergency Stores Jettison
BlueRaven POV SP v1.key
Same as BlueRaven POV.key except:
- Throttle Button 5 (Shifted) = DMS Left (cycle Left MFD) // Replaces and loses Commns Switch Up (UHF)
- Throttle Button 6 (Shifted) = DMS Right (cycle Right MFD) // Replaces and loses Commns Switch Down (VHF)
- Throttle Button 7 (Shifted) = DMS Down (change MFD SOI) // Replaces and loses CMS Down
- Throttle Button 8 (Shifted) = Toggle Jammer (J) // Replaces and loses CMS Right
BlueRaven POV SP v2.key
Same as above (BlueRaven POV SP v1.key) but adds these changes:
- Stick Button 1 Trigger (Shifted) = SRM (DF) Override // Replaces MRM Override
- Stick Button 2 Pickle (Shifted) = MRM Override // Replaces and loses Emergency Stores Jettison
BlueRaven POV SP v3.key
=== STICK: 8-WAY POV HAT ===
UNSHIFTED LAYER: Default POV HAT
SHIFTED LAYER: Slew radar cursor=== STICK: BUTTON 1 (TRIGGER / R1) ===
UNSHIFTED LAYER: Second trigger detent (i.e. fire gun)
SHIFTED LAYER: SRM (DF) override mode=== STICK: BUTTON 2 (PICKLE / L1) ===
UNSHIFTED LAYER: Weapon release (pickle)
SHIFTED LAYER: MRM override mode=== STICK: BUTTON 3 (under your right index finger / R3) ===
UNSHIFTED LAYER: Padlock view
SHIFTED LAYER: Glance forward=== STICK: BUTTON 4 (to the right of the pickle / L3) ===
UNSHIFTED LAYER: CMS up
SHIFTED LAYER: CMS left=== THROTTLE: BUTTON 5 ===
UNSHIFTED LAYER: TMS up
SHIFTED LAYER: Radar antenna elevation up=== THROTTLE: BUTTON 6 ===
UNSHIFTED LAYER: TMS right
SHIFTED LAYER: Radar antenna elevation down=== THROTTLE: BUTTON 7 ===
UNSHIFTED LAYER: TMS down
SHIFTED LAYER: DMS down=== THROTTLE: BUTTON 8 ===
UNSHIFTED LAYER: NWS / aerial refuelling disconnect / missile step switch
SHIFTED LAYER: Jammer on/off=== THROTTLE: BUTTON 9 (under your left index finger / R2) ===
UNSHIFTED AND SHIFTED LAYER: Hotas pinky shift=== THROTTLE: BUTTON 10 (lower under your left index finger / L2) ===
UNSHIFTED LAYER: Manual range knob - uncage
SHIFTED LAYER: Cancel DF/MRM override mode=== THROTTLE: BUTTON 11 (on the throttle basement / SE) ===
UNSHIFTED LAYER: Cursor enable
SHIFTED LAYER: Does nothing=== THROTTLE: BUTTON 12 (on the throttle basement / ST) ===
UNSHIFTED LAYER: Cursor zero
SHIFTED LAYER: Does nothingEnjoy!
-
Hello mate, I was going to look at porting the POV hat back to my keyfile but I think you anticipated me… and what a kind of anticipation, great work!!! :drink:
I absolutely don’t mind, on the contrary I encourage everyone to use my work as a basis of improvement for the whole community of Hotas X users as you did, thanks very much for your highly useful mods (I immediately stored them in my personal BMS useful stuff archive).
I’m glad of having been helpful for your understanding of how DirectX shifting works in the “DX Numbering” thread, too, it’s really fulfilling for me to give back something from the great body of knowledge that I received from this community.
Enjoy your flying and have a nice life! -
Hi BlueRaven,
I couldn’t wait as no Hotas programmed = no flying, haha. So I had to read up and try. But thanks to you - your key file was a good help.
One question. I couldn’t find the answers on the net. During Instant Action or Furball, my Wingman Commands (W) are greyed out. If I radio the Tower (not greyed out), there is no response. What am I missing?
I know BMS uses VHF/UHF and all those channels for realistic commns. I’ve read the manual but not entirely sure what the UHF/VHF buttons mapped on the throttle do. Still new to it. I don’t fly MP, not yet at least as I am not ready.
Cheers
-
Hi BlueRaven,
I couldn’t wait as no Hotas programmed = no flying, haha. So I had to read up and try. But thanks to you - your key file was a good help.
One question. I couldn’t find the answers on the net. During Instant Action or Furball, my Wingman Commands (W) are greyed out. If I radio the Tower (not greyed out), there is no response. What am I missing?
I know BMS uses VHF/UHF and all those channels for realistic commns. I’ve read the manual but not entirely sure what the UHF/VHF buttons mapped on the throttle do. Still new to it. I don’t fly MP, not yet at least as I am not ready.
Cheers
If your wingman menu is greyed out, it basically means you don’t have a wingman …. shot down maybe, or crashed, or maybe was never in the flight. You’re not getting a tower response because you’re on the wrong frequency, or, maybe, too far away.
UHF/VHF buttons are used for player-to-player communication (on the same freq). The menu system is used to ‘communicate’ (give orders, or make requests) with AI pilots, ATC, AWACS, etc.
-
If your wingman menu is greyed out, it basically means you don’t have a wingman …. shot down maybe, or crashed, or maybe was never in the flight. You’re not getting a tower response because you’re on the wrong frequency, or, maybe, too far away.
UHF/VHF buttons are used for player-to-player communication (on the same freq). The menu system is used to ‘communicate’ (give orders, or make requests) with AI pilots, ATC, AWACS, etc.
Hi AgaveBlue,
In Furball, I added a Wingman. When it starts, I seem to issue an automatic call to the Wingman to go Spread. But the W menu is still greyed out.
Are the UHF/VHF buttons only used in MP IVC chat - I mean like you click it and then speak into the mic?
-
…
Are the UHF/VHF buttons only used in MP IVC chat - I mean like you click it and then speak into the mic?Yes.
…. In Furball, I added a Wingman. When it starts, I seem to issue an automatic call to the Wingman to go Spread. But the W menu is still greyed out.
I hear you, but if the menu is greyed out, he’s not there. Another possibility, you might be in the #2 seat. You can’t give commands to lead from #2.