Noah_Hero Posted March 5, 2017 Share Posted March 5, 2017 (edited) Well as said in the headline it looks like my TFAR Plugin isn´t working as intended. As seen in the picture below I wont get "locally muted" when switched to TFAR-channels (not only on AWE) wich means that my mic is always hot. Obviously this could be kind of solved by setting my TS to ptt but I would like to really fix this. I already tried: starting TS as administrator reloading plugins reinstalling TFAR Also I get no error messages on TS or ingame and TFAR is connected and playing as also seen in the picture below. Does anybody knows a solution for this? Would appreciate any help! Edited April 10, 2020 by Noah_Hero Removed attachments to free up space Link to comment Share on other sites More sharing options...
Colsta Posted March 5, 2017 Share Posted March 5, 2017 You'll never see yourself as locally muted. It only transmits when the blue icon lights up. I don't see the problem. GhostDragon and Nicolai 2 Link to comment Share on other sites More sharing options...
Noah_Hero Posted March 5, 2017 Author Share Posted March 5, 2017 43 minutes ago, Colsta said: You'll never see yourself as locally muted. It only transmits when the blue icon lights up. I don't see the problem. oh, ok thanks. But is it supposed to be voice activated instead of ptt? Link to comment Share on other sites More sharing options...
GhostDragon Posted March 5, 2017 Share Posted March 5, 2017 Nope we force PPT on users within AWE because it avoids cluttering the voice communications. This could be different on other servers. Link to comment Share on other sites More sharing options...
Noah_Hero Posted March 5, 2017 Author Share Posted March 5, 2017 Just now, GhostDragon said: Nope we force PPT on users within AWE because it avoids cluttering the voice communications. Ok so then this is really a problem and not a feature! But I still have no idea on how to solve this issue Link to comment Share on other sites More sharing options...
GhostDragon Posted March 5, 2017 Share Posted March 5, 2017 i personally dont see the issue, just set a push to talk key? Link to comment Share on other sites More sharing options...
Noah_Hero Posted March 5, 2017 Author Share Posted March 5, 2017 24 minutes ago, GhostDragon said: just set a push to talk key yes that would be a solution as said above but as also said above I would like to really solve this and not just go on with something improvised and be always changing between voice activattion and ptt when hopping on TFAR servers. Edit: I have a ptt key setted but the problem is that it just wouldn´t set me to ptt in the TFAR channel Link to comment Share on other sites More sharing options...
Colsta Posted March 5, 2017 Share Posted March 5, 2017 Everyone is forced PTT on the TFAR channel. It's not a problem, it's a necessity, because people aren't responsible enough to use voice activation properly. Therefore, all you need to do is set a PTT. You're forced to use it in the channel. I really don't see the issue. All you need to do is use the key. You don't need to change anything. Nicolai 1 Link to comment Share on other sites More sharing options...
Noah_Hero Posted March 5, 2017 Author Share Posted March 5, 2017 Just now, Colsta said: Everyone is forced PTT on the TFAR channel. It's not a problem, it's a necessity, because people aren't responsible enough to use voice activation properly. Therefore, all you need to do is set a PTT. You're forced to use it in the channel. I really don't see the issue. You probably missunderstood me: I know that everyone is forced ptt and I like this. My problem was that the channel would NOT set me on force ptt but instead just set me on voice activation (And yes I had a ptt key). Regarding to Ghostdragon it was a error caused by the channel wich he has now solved. Thanks to Ghostdragon! Link to comment Share on other sites More sharing options...
Colsta Posted March 5, 2017 Share Posted March 5, 2017 Yes, you're correct. I misunderstood you, and it was an error on the channel. It's all fixed now. Noah_Hero and Nicolai 2 Link to comment Share on other sites More sharing options...
Noah_Hero Posted March 5, 2017 Author Share Posted March 5, 2017 Just now, Colsta said: Yes, you're correct. I misunderstood you, and it was an error on the channel. It's all fixed now. No Problem. But still thanks also for your help! Colsta 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now