ANyone ever have the problem where a switch splashed over into another switch?

[chief]

What I mean is this. Lets say I have my APU START ON. In joystick gremlin I have this assigned as button B. Now lets say I have my ENG OPER switch MOTOR assigned as button C. In theory if I moved my ENG OPER MOTOR switch (right one btw) to MOTOR I should only get a "C" stroke input. But sometimes when I have my APU START to ON (B) and I hold my ENG OPER at MOTOR ©, I will get an input as C+B when it should only be C. If I turn the APU START to OFF it functions normally. The APU START is splashing over into the ENG OPER MOTOR switch as well. I also get this when operating the A10 (No joystick gremlin). Sometimes when the APU is running in the A10 I got to start my right engine and bring the thrust lever to idle, it will shut down my APU. It splashes over into another assignment. I'm at a total loss why this is happening

[Supmua]

Is the APU switch assigned as hold, press or pulse in your case? If it is the first two then it could cause problem with continuous input as long as the switch isn’t flipped back to off position since that switch is the toggle type.

 

I used to use joystick Gremlin a lot but have since switched to RS Mapper since it is much simpler (albeit less powerful) and doesn’t require vjoy running in the background.

 

You can test this in Notepad or similar app (I think joystick Gremlin also has something built in), just assign a generic keyboard command to the switch (for example a letter c) and check the output behavior in Notepad when you flip it.

[Drakoz]

As Supma says, make sure it isn't related to how you programmed it using a hold or press function, but since you also say it happens when flying the A10, and I assume that is not using Joystick Gremlin, it may indicate a problem with your Warthog Throttle.

 

Do you ever see an issue with "splashed" outputs when looking at these buttons in the Windows Joystick control panel program. Or what about using the Thrustmaster TARGET Device Analyzer (run from the TARGET Script editor, or you can find it at "C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETDeviceAnalyzer.exe"). Either should show you all buttons, but of course they only show you the DirectX version of those buttons (i.e. you won't see a positive "ON" for a button that is off like the APU Start in the OFF position). But this is good enough to tell if something is doing what it shouldn't be because it bypasses any possible programming you may have applied.