OHHHHH!
Yeah, it would be "both buttons at the same time" that's the problem! That would explain it!
I'll just test now...
...yup! There we go! Works just fine with only one of them pressed.
Well, there we go then. It would be a nice feature to have, to be able to have more than one PTT bind. Then I could pretend I'm a real fighter pilot man, talking to my element on one radio and AWACS/Tower/Ground on the other :D
Though possibly I could get away with no PTT at all too, I'm not sure.
Wait, hang on. I'm trying to get that set up now, and running into another issue: UHF isn't working, while VHF is. Weird! For instance, I've set my ELEMENT PTT to VHF, which is "Winwing WINWING Orion Throttle Base II + TGRIP-F16 Btn 24". When I push it, I can see the little white controller icon on the ELEMENT group turn green. I did exactly the same thing to set GROUND to UHF, which is Btn 26. When I push it, the white controller icon on GROUND stays white, and when I say "Ground, pin" the log indeed reports that it recognised the command and inhibited it due to PTT.
Weird. It did work when I changed GROUND to my C keyboard key, just to test, but not that other HOTAS key. I know the button itself works - after all, FoxVox itself picked it up when setting the PTT key!
Make sure that the button isn't registered in the block list (found in settings). Otherwise, FoxVox won't pick it up when it is pressed. Some other settings in the PTT could also affect it such as the 'Isolate' option which limits PTT to not work if any additional keys are pressed besides the bound PTT Keys.
Besides this, what you describe doesn't seem to be a FoxVox issue. As you said, it picked it up when you assigned it to the PTT. Make sure the hardware/drivers are passing through the button accurately and consistently on press each time - FoxVox doesn't do anything with the input besides monitoring the button states passed in by the OS. Verify it's not being affected by any controller macro logic or third party apps.
Hm.
I'm 95% sure it's a FoxVox issue, because I've successfully used the same keys with other programs, like SRS. I have them as push-to-mute in Discord as well, which also picks them up fine.
My block list is empty.
It seems to me that FoxVox likes some of the keys and doesn't like others, because I've found other ones that also don't work: 5, 10, 11, 15, 23.
It's so weird! For instance, IFF in, IFF out and VHF all work, but UHF does not and pushing in that switch does not. Speed brake close and neutral work, but deploy does not (and all of those definitely work, both in DCS and FalconBMS!)
Ok, I've posted an update to attempt to fix the issue. Unfortunately I don't have any hardware to test, so I'm relying on you to let me know if it resolves the issue. Also, I've added in a feature with the Push-to-Talk settings that let you specify 'Any Key' to allow any of the bound keys to activate PTT rather than all. Let me know how it goes!