Buttons on my G940

[brettt777]

I have a Logitech G940 FFB stick, dual throttle and pedals. I can get the axis to assign and tune no problem. But I can't get all the buttons to work, on any aircraft. In fact, all but a few of them don't come up at all when I try to assign (they all work in other sims). Is there a trick to this? I know in other sims, I have to go into the Logitech Profiler software and assign each button to a command, etc. and I have tried that but it still doesn't work. how do I make the buttons on my G940 show up in DCS?

[Dudikoff]

I have a Logitech G940 FFB stick, dual throttle and pedals. I can get the axis to assign and tune no problem. But I can't get all the buttons to work, on any aircraft. In fact, all but a few of them don't come up at all when I try to assign (they all work in other sims). Is there a trick to this? I know in other sims, I have to go into the Logitech Profiler software and assign each button to a command, etc. and I have tried that but it still doesn't work. how do I make the buttons on my G940 show up in DCS?

 

If the buttons are assigned to some functions in the Profiler, they probably won't be available in the game. So, perhaps try to set the Logitech Profiler to use a global profile (rather than being application dependent) and then clear all the button assignments in it (the Profiler) and see if that helps.

[zaelu]

I also have G940 and I observed this behavior since first 1.54 patch. Most of the times I have to press repeatedly a button until it is "sensed" by the game.

 

In my opinion this appeared at the same time with introduction of hot pluggin and multiplayer input editing capability and somehow at least for the G940 it has a bit o lag.

 

Workaround solution for buttons that simply refuse to appear even after multiple presses is to go to a different module and see the name (number) of that button already assigned and then pick it up from the list in the new module or where the user wants to edit. Worst case... pick by trial and error the buttons and test if they work. Once assigned the buttons react normally in the controls interface... meaning pressing them will make the list jump to the line where they are in use.

 

I add a screenshot with the place the list is for picking the buttons in case someone didn't see it:

 

 

Edited July 24, 2016 by zaelu

[Nascar]

Make sure you are in the right column, Joystick or Throttle. I screw this up on occasion. If you have a racing wheel I would suggest disconnecting it. I have had conflicts with my wheel.

[Sokol1_br]

If the buttons press are not detect in GUI try select then by number in the list - this workaround work OK for axis - like in Zaelu picture

 

http://i.imgur.com/Wqx88ql.jpg

 

Leave Windows Games Controllers (joy.cpl) opened when do this to identify buttons numbers help.

Edited July 24, 2016 by Sokol1_br

[wormeaten]

I think this will solw your problem.

For multiple planes you need multiple profiles or always use default profile and everything set up true the game.

 

[1Sascha]

This isn't exclusive to the G940.

 

I'm using a combination of

1. CH Pro Throttle

2. MS SW FF2

3. CH Pro Pedals (gameport)

 

..and my throttle's buttons sometimes fail to get read by the game, too. Sometimes it's just in the keymapper where it'll take lots of pushes until the mapper "sees" the button. Sometimes it also happens in-game when certain functions won't work (while others do). Just last night I tried to do the "counter-measures" training in the Su-25, only to find that both my chaff and flare functions weren't working (I have them mapped to 0° and 180° on the same hat-switch). ECM, mapped to the same hat's 90° position, also didn't work, while "Center TrackIR" on the hat's 270° position still worked fine.

 

I tried to narrow this behavior down and found that (weirdly enough) the buttons in question also didn't work in the CH Control Manager "test/calibrate"-screen. They worked fine in the actual mapping-part of the CH software (meaning pushing the button would correctly display the mapping dialogue for that button).

 

Only way to solve this so far was to re-load the CH profile into the throttle and/or restart the game. Had to quit DCS, quit TrackIR, then reload my CH profile, restart TrackIR then restart DCS.

 

 

I also noticed that I will sometimes lose Force Feedback while in-game. One mission it works fine and on the next my stick will go completely "limp". I tried to fix this by changing the FF-value in the keymapper (like from 98 to 99 ) - that worked before to activate FF, but not this time. Usually I have to re-plug the stick to get FF back in this situation.

 

I don't see what could be causing this. I'm using the throttle's buttons as buttons - not to send out keyboard-commands. The only function that does send out keys is the ministick, which I use to control the Su-25's optical sensor. For some reason, the axis-function for this thing can't be mapped to the stick (blacked out in the key-mapper). I guess since it's labeled "mouse axis", the game will only let me map my mouse to it ...? *shrug*

 

Note: I'm using this setup and CH profiles in a number of other sims, too. And I never had that kind of behavior in any of them. It's just in DCS that the throttle will start to act up on occasion.

 

S.

Edited July 25, 2016 by 1Sascha