• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

TeamSpeak oddity

falcon409

falcon409

Moderator
Staff member
For the time being I'm blaming this on Win10 only because I know it was never a problem prior to that installation.

I have a dual monitor setup that's shared across both monitors, in other words I can drag things off the main monitor directly across to the right side monitor. Prior to Installing Win10, when on Teamspeak, it made no difference what monitor I was actively using, when I keyed the mic I could talk to whoever was on TS with me. Since Win10, I must be either active on the second monitors desktop or the actual TS popup window in order for the keypress to work. If I'm on that monitor but have another window active. . .or if I'm on the main monitor in another window, the key press will not activate TS.

That may be confusing but I hope I've explained it well enough that someone might recognize why this is happening and suggest corrective action. It simply means that now I have to be very aware of what window I'm working in before I press to talk, otherwise no one hears what I'm saying.
 
Just to clarify, I at first suspected UAC as the culprit since I've always had it turned off in previous OS installs. I turned off the UAC and rebooted the PC, went back to Teamspeak and got that up and running then loaded FSX and nothing changed. If I'm actively in the FSX window then the press to talk key does not work in TS and that's never been the case before, so it may not be UAC but it seems to be Win10 related. . .for now.
 
You must log in or register to reply here.
Back
Top