I have had constant issues with voice chat in game since launch. I have tried everything I can find online, I have tried deleting and reinstalling the game, I have tried allowing voice comms through my xbox profile online, I have tried changing my sample rate to something lower, I have tried setting a different PTT button or turning PTT off. I have changed inputs through the Xbox Console Companion and the Xbox Game Bar. I have done everything. I put in a support ticket months ago that told me to do everything I have already done and never got another response. I just want to be able to use voice chat in game. The thing is, occasionally I can get it to work and it will work for 2 weeks to a month and then it just stops again. All my other apps including Teamspeak and Discord work just fine with my mic. Please help, I want to be able to communicate with my crew by means other than typing.
Constant Voice Chat Trouble (PC)
@aod-thatnavyguy does it happen to mess up after Windows Updates?
Sometimes it decides to reset your audio preferences for....fun?
I have a program/App called Ear Trumpet (https://www.microsoft.com/store/productId/9NBLGGH516XP) that seems to have stopped it being changed (seemingly at random).
No guarantee it will fix your specific issue but it at least keeps your audio preferences once you have set them. (also try disabling any other mics/cam mics you may have plugged in)
@aod-thatnavyguy
This is most likely linked to the drivers and/or software your system uses, it might be a single advanced option that is causing the issue.
Also, check software that is used for recording, shadowplay, OBS, specific audio software, etc. you might have running that is limiting your voice to be broadcasted in game.
Good luck pinpointing the culprit.
My PC has a Teredo error every couple of days. I have to fix it and restart before playing. Go to settings/Gaming/Xbox Networking. It will run a scan and under NAT Type, if it says "Teredo unable to qualify..." then you can't communicate in game. Click Fix It, restart, and that should do it. If you're like me, you'll form a habit of checking every time before launching the game. Haven't been able to find a permanent fix, yet.
@eastwood304 said in Constant Voice Chat Trouble (PC):
My PC has a Teredo error every couple of days. I have to fix it and restart before playing. Go to settings/Gaming/Xbox Networking. It will run a scan and under NAT Type, if it says "Teredo unable to qualify..." then you can't communicate in game. Click Fix It, restart, and that should do it. If you're like me, you'll form a habit of checking every time before launching the game. Haven't been able to find a permanent fix, yet.
Oooo, this seems promising. I'll try it in a bit.
@eastwood304 said in Constant Voice Chat Trouble (PC):
My PC has a Teredo error every couple of days. I have to fix it and restart before playing. Go to settings/Gaming/Xbox Networking. It will run a scan and under NAT Type, if it says "Teredo unable to qualify..." then you can't communicate in game. Click Fix It, restart, and that should do it. If you're like me, you'll form a habit of checking every time before launching the game. Haven't been able to find a permanent fix, yet.
@aod-thatnavyguy said in Constant Voice Chat Trouble (PC):
Appears to have fixed it that one time but I feel like this should be addressed by devs. All my other applications work fine with mics. Why is it only this one?
I think it is actually a Microsoft issue. I have done absolutely every fix that the internet suggests and it still happens. It is either a conflict with my antivirus software (Bitdefender) or network driver compatibility issues. Just lucky that way, I guess.
@eastwood304 I think it is a conflict with Bitdefender. I tried fixing it in the built in firewall for Bitdefender but I cannot find the file path. It is a hidden folder in WindowsApps and the typical methods of granting permission don't seem to be working. If anyone knows the EXACT path including the name of the file that windows installs to by default, please post it here. I believe this could be the fix for this issue. I saw a post about this in a blog a few days ago and had already tried but couldn't find the path.
