Warthog HOTAS keybinds randomly stop in flight

[wrd7105]

Hi all,

 

I have noticed a number of times and moreso when I fly the Mirage that some of the key binds on both throttle and joystick randomly stop working for a period of time during longer missions then spring to life again.

 

It's not main axis controls that are effected at all just things like activation of weapons, weapon selection, autopilot engagement, trim, map access etc.

 

All the secondary type functions.

 

My system is fairly high end i7 8700K OC to 4.7, 32G 3200 Ram, 1080Ti, Rift CV1, full Warthog HOTAS bundle so I wouldn't have thought it was a bottleneck in the PC.

 

When the binds stop working I am still able to control main axis inputs as mentioned and after 5 or so minutes the problem normally goes away.

 

Any suggestions?

 

It doesn't stop my playing just an annoyance more than anything.

[Jugdriver]

I think I am experiencing the same thing, but it is happening with the F-18 more for me.

 

 

Are you losing keyboard commands as well?

 

 

 

JD

 

 

AKA_MattE

[rockme]

Hi I have the same Problem with F18 sometimes there are no Problems at all and sometimes the Keybindings Seemed to be messed up. Like the Keybindings for TDC cursor if used opens suddenly the airbrakes or the Radiomenu etc. I Use the stable Version, after I Start the Mission again everything works as it should it is very annoying, just to mention I already doublechecked if keybindings or axis are Double but thats not the case! Hotas Warthog i7 6700k 16gbram Asus R290x gpu! Any ideas how to Solve this issua?

 

Rockme

[Malevolent]

Hi I have the same Problem with F18 sometimes there are no Problems at all and sometimes the Keybindings Seemed to be messed up. Like the Keybindings for TDC cursor if used opens suddenly the airbrakes or the Radiomenu etc. I Use the stable Version, after I Start the Mission again everything works as it should it is very annoying, just to mention I already doublechecked if keybindings or axis are Double but thats not the case! Hotas Warthog i7 6700k 16gbram Asus R290x gpu! Any ideas how to Solve this issua?

 

Rockme

 

 

Had a similar issue this summer. Check for a chafed wire in the right throttle, it will be around where the throttle rests on the cable at the pivot point. Be flying along, push to burner and my speed brakes would come out. TDC would randomly stop working

[macedk]

Keybinds are porked in new update

[Malevolent]

Keybinds are porked in new update

 

 

this post was pre-update

[Dutch Baron]

Hi,

 

You may want to check if you have the following lines filled in your DCS.log, basically your controllers (joytsticks and such) should initiate one time, but for still unclear reasons it could do it numerous times, the logs should look something like this:

 

2018-10-13 21:17:30.447 INFO INPUT: Device [Keyboard] created deviceId = -1

2018-10-13 21:17:30.447 INFO INPUT: Device [MFG Crosswind V2 {1AD0F3B0-11E3-11e8-8001-444553540000}] created deviceId = -1

2018-10-13 21:17:30.447 INFO INPUT: Joystick created[MFG Crosswind V2 {1AD0F3B0-11E3-11e8-8001-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.450 INFO INPUT: Device [Joystick - HOTAS Warthog {7B9A4200-572D-11e5-8002-444553540000}] created deviceId = -1

2018-10-13 21:17:30.450 INFO INPUT: Joystick created[Joystick - HOTAS Warthog {7B9A4200-572D-11e5-8002-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.469 INFO INPUT: Device [Throttle - HOTAS Warthog {7ADB85E0-572D-11e5-8001-444553540000}] created deviceId = -1

2018-10-13 21:17:30.469 INFO INPUT: Joystick created[Throttle - HOTAS Warthog {7ADB85E0-572D-11e5-8001-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.504 INFO INPUT: Device [Keyboard] created deviceId = -1

2018-10-13 21:17:30.505 INFO INPUT: Device [MFG Crosswind V2 {1AD0F3B0-11E3-11e8-8001-444553540000}] created deviceId = -1

2018-10-13 21:17:30.505 INFO INPUT: Joystick created[MFG Crosswind V2 {1AD0F3B0-11E3-11e8-8001-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.507 INFO INPUT: Device [Joystick - HOTAS Warthog {7B9A4200-572D-11e5-8002-444553540000}] created deviceId = -1

2018-10-13 21:17:30.507 INFO INPUT: Joystick created[Joystick - HOTAS Warthog {7B9A4200-572D-11e5-8002-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.526 INFO INPUT: Device [Throttle - HOTAS Warthog {7ADB85E0-572D-11e5-8001-444553540000}] created deviceId = -1

2018-10-13 21:17:30.526 INFO INPUT: Joystick created[Throttle - HOTAS Warthog {7ADB85E0-572D-11e5-8001-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.539 INFO INPUT: Device [Keyboard] created deviceId = -1

2018-10-13 21:17:30.540 INFO INPUT: Device [MFG Crosswind V2 {1AD0F3B0-11E3-11e8-8001-444553540000}] created deviceId = -1

2018-10-13 21:17:30.540 INFO INPUT: Joystick created[MFG Crosswind V2 {1AD0F3B0-11E3-11e8-8001-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.542 INFO INPUT: Device [Joystick - HOTAS Warthog {7B9A4200-572D-11e5-8002-444553540000}] created deviceId = -1

2018-10-13 21:17:30.542 INFO INPUT: Joystick created[Joystick - HOTAS Warthog {7B9A4200-572D-11e5-8002-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.560 INFO INPUT: Device [Throttle - HOTAS Warthog {7ADB85E0-572D-11e5-8001-444553540000}] created deviceId = -1

2018-10-13 21:17:30.560 INFO INPUT: Joystick created[Throttle - HOTAS Warthog {7ADB85E0-572D-11e5-8001-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.596 INFO INPUT: Device [Keyboard] created deviceId = -1

2018-10-13 21:17:30.597 INFO INPUT: Device [MFG Crosswind V2 {1AD0F3B0-11E3-11e8-8001-444553540000}] created deviceId = -1

2018-10-13 21:17:30.597 INFO INPUT: Joystick created[MFG Crosswind V2 {1AD0F3B0-11E3-11e8-8001-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.599 INFO INPUT: Device [Joystick - HOTAS Warthog {7B9A4200-572D-11e5-8002-444553540000}] created deviceId = -1

2018-10-13 21:17:30.599 INFO INPUT: Joystick created[Joystick - HOTAS Warthog {7B9A4200-572D-11e5-8002-444553540000}], ForceFeedBack: no

2018-10-13 21:17:30.618 INFO INPUT: Device [Throttle - HOTAS Warthog {7ADB85E0-572D-11e5-8001-444553540000}] created deviceId = -1

2018-10-13 21:17:30.618 INFO INPUT: Joystick created[Throttle - HOTAS Warthog {7ADB85E0-572D-11e5-8001-444553540000}], ForceFeedBack: no

 

 

If you have multiple instances of similar looking text in a single sortie, you may have the same issue I have been having for more than a year.

If yes, then your PC is basically registering your controllers multiple times, instead of just once as it should do. It will cause a specific set of buttons to be reinitiated and basically activated, causing certain things to go off in your plane.

 

@malevolent

When you had the issue with your chafed wire, did you have mutliple instances of all your controllers being reinitiated in your dcs.log? Also having TrackIR plugged/unplugged message at that same time?

[wrd7105]

Hi all, this problem has been at times a painful one. This was posted pre update and the latest update created havoc with the F/A 18 key Hotas binds and I had to do them again. Now on another note and post my first post, I was flying multiplayer on one of the servers over the weekend and after over an hour of flying the Gazelle was about to land when the controls just totally froze up again.

 

So not only is this happening off line but online as well. I like the most recent post before I wrote this so my question is, how do we fix it if the PC is registering multiple instances ?