That isn't what you like to hear!! :D
Well... let me elaborate as best I can. This has happened not less than 3 times over the past couple of months. Each time, I can correct it only by uninstalling and then re-installing FSUIPC.. on doing so, all works fine. But, as I said, it keeps coming back. And, it is important to note that the PTT function will be working fine for weeks. I will have made no changes to any setting, not even opened FSUIPC during this period.. and the issue will abruptly return.
What is happening is that the microphone goes hot, or continually transmits, via SB, and I can do nothing to make it stop.
FS9 and SB are running on the server computer. CH products yoke is attached to the server computer. The functional instance of SB is running on a client computer. I am using the keysend function/control for PTT... parameter 1 when pressed, 2 on release. The control to repeat when held has been tried checked and unchecked with no change when the issue surfaces. It must be checked to repeat when held for the PTT to work properly, when it is working :)
On a potentially related note: I have numerous GoFlight panels also attached to the server. Recently, the throttle movement started giving me rudder and elevator imputs. Through discussions with GoFlight I learned that FS will, on occation, take it upon itself to assign functions to the GoFlight joysticks... in this case, it assigned the rudder and elevator axis to the throttle inputs. I am currious if something similar might be happening with the CH yoke... might FS be assigning an input to the PTT button that once accuated cannot be terminated. If so, I have not been able to find it and am not clear on how reinstalling FSUIPC corrects it... which it does each time.
I use the Project Magenta software with the GoFlight panels, so each time I reinstall FSUIPC I have to go back through and setup the button assignments again... is a time consuming process. I assume if I keep the INI file, even though I remove FSUIPC that I could retain the button assignments?
Anyway... unless I am not being clear in my description, it is happening as I describe... but the source of the issue may not be at all associated with FSUIPC... but re-installing FSUIPC does indeed correct it..
Hope you can recommend some course of action to track down this odd and recurrant problem!!
Thanks!
Tony