Plane going bazerk with Logitech G940

[Pilotasso]

Hi guys.

 

Im having a bit of trouble here. While using G940 on MP sessions sometimes the plane starts making uncommanded turns, radar goes all over the place, trim goes crazy etc.

 

 

As a matter of note, this is similar to what I got from X52 that had a bug where it got a ming of its own sometimes, but once I reloaded the profile it resumed normal behaviour, only with my G940 that doesnt work.

 

If I tab to windows it responds in CAPS mode all the time, no matter how many times you press it.

 

Ulnloading (either by leaving or terminate in the task manager) the game restores everything to normal.

 

Anyone having issues?

 

cheers

Edited November 15, 2009 by Pilotasso

[bengo]

Dp you use a profile for your HOTAS ? Looks like a shift-keypress isn't terminated properly. Obviously the keypress shift-down is executed, but one of your keypresses in your profile is missing a keypress shift-up somewhere.

By reloading the profile everything is reset and the problem seems to be gone, until you press that button again.

Only in MP ? Do you have a push-to-talk key (for Teamspeak or Ventrilo) in your profile ? Maybe that's not programmed properly ?

Maybe it's a slider or a turning knob that's not centered properly and keeps pumping out keypresses ?

[Pilotasso]

I see bugs due to the lack of key releases but my problems is a persitent one, more like something keeps being pressed. Since it continues when Im not pressing anything I think this is a driver issue. And I could not get a work arround yet but terminate the game (when I am able to tab the game to windows, sometimes I cannot).

[bengo]

There's a little utility called StickTest to see if or what keypresses get generated. I use it all the time to see if my CH- and Touchbuddy-profiles send out correct keypress-sequences. It not a big file, so if you need it, PM me with your details and I'll send it over.

[Pilotasso]

I apreciate, I will search for it but as I said, even if the stick did give wrong commands, they would only last as fast as the buttons are pressed/depressed.

 

What Im seeing is different, keyboard seases to respond and the game acts like a mind of its own. Something is getting stuck, not a simple button command me thinks.

[bengo]

If a shift-key gets stuck in the "down-position", each other button you press, will generate "shift-down" in front of it. For example, if you got a button on your stick programmed to send out "g", in this situation it will send out "shift-g".

Try to hold your shift-button on the keyboard down, and see if everything returns back to normal.

[JG14_Smil]

I know if my stick is not loaded, it will send funky commands like joystick movment sometimes. Sounds like your controller may be dropping in and out.

 

Try windows game controllers and look for the same symptoms.

 

Guys, he knows it is not a stuck Shift key as it was never pushed.

[bengo]

I'm not saying he pushed the shift-key phisically. I'm thinking a buttonpress on his HOTAS is sending out an incomplete keypresssequence. And apparently it's one that requires a press of a shift button.

Let's just say he has programmed the keypresssequende "shift-a" to a HOTAS-button. The complete sequence would be: 'shift-down/a-down/a-up/shift-up"

But somehow the shift-up command is dropped from the keypresssequence, and thus the shift-key is "stuck" in the "down"-position software-wise. That's why he sees all CAPS when he tabs out.

Edited November 15, 2009 by bengo

[emenance]

What did logitech say about it? Sounds like a bad stick to me.

[Pilotasso]

Almost sure its a software issue, because it works fine in all other apps, and my X52 did much the same except the G940 software seems to be less cabale of letting me go arround its problems.

[emenance]

I am still interested in THEIR opinion.

[Scarecrow]

If you have axis commands or zone commands programmed they may be constantly held down due to deadzone issues. I had the same thing in LOFC when I had wheel breaks on a zone command that was active all the time due to me not putting in a deadzone for my toe break axis. Once I made a small 5% deadzone they were fine. Try making the profile persistant and opening notepad to see if there are any unwanted command being sent.