Hello Bungie Support,
I'm experiencing what appears to be an account-specific issue with Destiny 2 voice chat.
I can successfully join Fireteam Voice Chat, and other players can hear me without any problems. However, I cannot hear anyone else speaking.
When another player uses push-to-talk, I can see the small "X" next to their speaker icon disappear, indicating that the game detects they are attempting to speak. However, I never see the voice activity bars appear next to their speaker icon, and I receive no incoming voice audio.
Troubleshooting Performed
Voice Chat is enabled in Destiny 2.
Other players can hear my microphone normally.
I can hear all other game audio (music, sound effects, dialogue, etc.) without issue.
The problem occurs on both PC (Steam) and Xbox using the same Destiny account.
I tested on multiple platforms with the same account and the symptoms are identical.
I tested using a completely different Steam account and a new Destiny account on the same PC, using the same headset, same Windows installation, and same network.
On the new account, Destiny voice chat worked correctly immediately. I could hear other players and they could hear me.
Switching back to my main account on the same PC causes the issue to return.
Summary
Because the issue follows my main Destiny account across both PC and Xbox, while a different Destiny account works correctly on the exact same hardware and network, this appears to be an account-specific voice chat problem rather than a hardware, Windows, network, or headset issue.
Could you please investigate whether there is an issue with the voice chat configuration or permissions associated with my Destiny account?
Thank you for your time and assistance.
-
2 RepliesHello there, Thank you for your detailed report. We understand you're experiencing voice chat issues in Destiny 2. We're sorry to hear of this, as we can imagine the impact of such an issue. By any chance, does resetting the game's voice settings on your primary platform, which appears to be Xbox in this case, resolve this? If not, please let us know and we'll investigate.