HAT switches on g940
-
Hi
Had some trouble programming the hat-switches on my g940 hotas.
After selecting the blank BMS-keyfile, and then set up the stick, the DMS, TMS and CMS works as intended. A bit of Work, but it pays off.
And be sure DMS commands are single key only.
Hope this will help someone.
Happy hunting
-
Hi Again.
Have to make an update:
DMS and TMS should be one key commands only. I use Alt + num 8,6,2,4 for CMS, num 8,6,2,4 for DMS and Home, End Pgdn, Delete for TMS, and it Works fine. Could be a keybord issue, so try different keys and combos if yoy have trouble.
Also turned out I did not have to make a keyfile from scrathc.Now off for some serious simming8-)
-
I’m having this exact same issue now. Any chance you could help out a fellow Scandinavian with the keyfiles or logitech profile you use?
-
I give up! The Logitech software just won’t work with bms 4.33.1
-
I agree with those discoveries.
Since the update I also came across a difference in the behaviour of the logitech software. It seems to ignore (or not) key combinations depending on which executable you choose as target for the logitech software (launch.exe vs falconbms.exe). -
Going back to bms 4.32. But only up to update 6, as I discovered some problems with update 7 too. No problems with G940 there.
Sad. So much work has been put into this latest version, and it really looks great. But it seems a little “buggy”, or perhaps it is just a hardware issue, I don’t know.
Anyway, keep up the good work BMS team
-
Just gave it a new chance. Can get it to Work in the setup menu, where everything is recognised as programmed. In game however, the radio makes a crack when I touch a Hat switch. ?
Does not make sense. -
U got two commands for the same thing… i guess thats your problem.
-
Running into the same issue here. Falcon recognises the keystrokes i assigned to the hats but in game refuses to respond. Also checked. Nothing is double mapped.
-
Guys,
When checking your key assignments in the BMS GUI be sure to have the NUM LOCK off. -
The numlock seems to have no effect. BUT I did just notice… Double shifting causes errors.
Example: I have my RDR cursor mapped to (shift + Throttle hat 1), the shift being a throttle button.
The RDR cursor is mapped to (SHIFT + arrow keys) by default.
When using this combo, what I’m essentially pressing is: “SHIFT + (SHIFT+arrow)”.
THIS causes an obvious error.I swapped the radar cursor keys with the ICP switch keys.
That now lets me control the cursor. Ironically by still pressing (Shift + arrows)…but now on the throttle.
Yet this doesn’t seem to affect the ICP switch, which is now ALSO (Shift + arrows)…but on the keyboard.EDIT (#2):
Assigned ICP switch to different unused key combo’s now. This leaves the RDR cursor and the ICP out of eachothers way just to be safe. Both work fine now.
What remains unsolved:
-Stick top HAT switch unassignable. Probably because it’s an axis instead of a button. Not sure how to work around this.
-HOTAS keybinds not recognised depending on which exe you start BMS from.All other issues seem to be related to double bindings or impossible key combo’s.
-
I give up! The Logitech software just won’t work with bms 4.33.1
Yes it does. You have to map keys for the G940 and make sure you DO NOT have ANY double keystrokes in bms. Also make sure you have the G940 set in “Global Profiler” to use “Apply Persistent Profiles”.
-
I agree with those discoveries.
Since the update I also came across a difference in the behaviour of the logitech software. It seems to ignore (or not) key combinations depending on which executable you choose as target for the logitech software (launch.exe vs falconbms.exe).See previous post.
-
Running into the same issue here. Falcon recognises the keystrokes i assigned to the hats but in game refuses to respond. Also checked. Nothing is double mapped.
See previous post.
-
The numlock seems to have no effect. BUT I did just notice… Double shifting causes errors.
Example: I have my RDR cursor mapped to (shift + Throttle hat 1), the shift being a throttle button.
The RDR cursor is mapped to (SHIFT + arrow keys) by default.
When using this combo, what I’m essentially pressing is: “SHIFT + (SHIFT+arrow)”.
THIS causes an obvious error.I swapped the radar cursor keys with the ICP switch keys.
That now lets me control the cursor. Ironically by still pressing (Shift + arrows)…but now on the throttle.
Yet this doesn’t seem to affect the ICP switch, which is now ALSO (Shift + arrows)…but on the keyboard.EDIT (#2):
Assigned ICP switch to different unused key combo’s now. This leaves the RDR cursor and the ICP out of eachothers way just to be safe. Both work fine now.
What remains unsolved:
-Stick top HAT switch unassignable. Probably because it’s an axis instead of a button. Not sure how to work around this.
-HOTAS keybinds not recognised depending on which exe you start BMS from.All other issues seem to be related to double bindings or impossible key combo’s.
Umm, wrong way to go about it. You can map the throttle axis (POV or rotational axis) to specific keystrokes. In the Logitech software, map your throttle POV or rotational axis by changing the 8 point inputs to 4 point inputs (1st person POV movement). Then assign each position of the axis with your bms keystroke. You can use combination keystrokes as well, but when recording them just be careful to do it properly (when recording, hit the “shift, alt or control” key first then your final keystroke). Don’t depress them too long or you will double (or more) that combination (i.e. you will move your mini stick axis and it will repeat the command over and over, and over).
Hope this helps you guys with using the G940. It is a fantastic HOTAS, with twin throttle quads (dual engine jets are now awesome to control each engine) and rudder pedals that are fully adjustable! Had mine for many years. I also had a lot of trouble when I first got mine, but realized it needs to be mapped carefully.
-
Jhook, continuing our discussion from “ff you could have one thing in the next update it would be…” thread, I just wanted to tell You, that on the TeamSpeak server where I usualy spend evenings, I’ve found guy who claims to have extensive experience about DX combination mapping and BMS in general and he declared help for me in that subject. So as long as his knowledge will be sufficient, I’ll try not to bother You with that subject.
-
Jhook, continuing our discussion from “ff you could have one thing in the next update it would be…” thread, I just wanted to tell You, that on the TeamSpeak server where I usualy spend evenings, I’ve found guy who claims to have extensive experience about DX combination mapping and BMS in general and he declared help for me in that subject. So as long as his knowledge will be sufficient, I’ll try not to bother You with that subject.
No bother at all. It is that I come here at irregular times. Also, be very cautious about playing around with the DX code in bms. Real easy to screw things up.
-
Just gotta change the controller from the scroll down menu, by default in BMS is shows the joystick, scroll down to the others to map from within game if you don’t want to use the profiler.
-
My bad, I guess the update drops that from working anymore…
