Odd problem with UHF volume knob and HOTAS (Pilot seat)

[Hootman9104]

I have an odd problem that has popped up.

I have my Logi X-56 Pinky Switch set as a "modifier" to use with other buttons/switches on the stick and throttle. Works fine for the most part.

But I just noticed that now whenever I engage the pinky switch, the UHF volume snaps over to minimum volume.

I searched my entire profile, including the CP/G and George profiles, paying particular attention to the COMM PANEL, and nowhere to I see the pinky switch assigned to affect the UHF volume at all.

On my voiceattack profile I do use some keybinds for that alone to do some things like run little scripts that you can't do in DCS, but didn't find anything there either. In addition, I shut down VoiceAttack and it still happens in the pilots seat.

I removed the pinky switch as a modifier, and it stopped doing that. Added it back in, and it started again, pinky switch snaps the UHF volume to minimum.

I've been using that for the longest time as a modifier, and I just noticed this happening. 

Could someone else try this? Would be interesting to know if this is an X-56 problem, or a problem across the board with assigning a HOTAS pinky switch as a modifier.

[Smashy]

One possibility is you have a modifier+axis bound to UHF volume.  Did you check your axis bindings?

[Sacarino111]

27 minutes ago, Smashy said:

One possibility is you have a modifier+axis bound to UHF volume.  Did you check your axis bindings?

A was about to say the same...

[Hootman9104]

Nope. I covered all that in the original post. Nothing is bound to any volume switch anywhere.

Volume knob turning is one of the few things that I have NOT bound in my extensive Voiceattack and DCS profiles. I've been using the mouse in cockpit for that.

I do have some knobs bound, as it CAN be done in Voice attack by having the command press the assigned key down, hold for x amount of seconds, and then release.

For instance, I have a command script that I execute that sets every one of my instrument lighting and external lighting settings for night flight, like the panel flood lights and MPD brightness, to a preset level with one command. All I say it "Night Flight" and voiceattack adjusts every knob and gives me a text to speech confirmation for each one, i.e "Left MPD....set".

So yeah nothing bound in profile, and I double checked voice attack, and even checked with voiceattack not running. 

HOWEVER, TONIGHT IT IS WORKING JUST FINE. BUT THIS WENT ON FOR DAYS. I'LL HAVE TO KEEP AN EYE ON IT, BUT FOR NOW, IT'S WORKING AGAIN, NO SNAPPING THE UHF VOLUME OFF ANYMORE BY PRESSING THE PINKY SWITCH WHEN USING IT AS A MODIFIER. VERY ODD.

FURTHER UPDATE: ACTUALLY I FOUND DID HAVE IT BOUND, BUT IT WAS BOUND IN THE AXIS SETTING....DUH....I BOUND IT TO THE PINKY SWITCH+ONE OF THE THROTTLE KNOBS SO I COULD ADJUST IT BECAUSE IN LIBERATION USING THE VIACOM PROGRAM, THE AWACS BECOMES ANNOYING AT TIMES. SO APPARENTLY I HAD THAT KNOB ALL THE WAY DIALED DOWN, AND WHEN I HIT THE PINKY SWITCH, IT WAS THROWING IT HARD LEFT....SO WE'RE ALL GOOD NOW I THINK....AND NOW I'VE REMEMBERED THAT I'VE BOUND THAT, SO I CAN GO BACK TO USING IT FOR WHAT I MEANT TO USE IT FOR TO BEGIN WITH

Edited February 7, 2024 by Hootman9104

[Floyd1212]

Yeah, that was what others were suggesting; check the axis binds, not just the button binds.

Glad you found it.