tired of this.

[BanzaiBob]

EVERY single update, EVERY single one, I end up having to buy a new headset to communicate in game. I cvan HEAR everyone just fine. They can't hear me.

YES I have done EVERY single suggestion listed in the forums numerous times, even called my internet provider and had them change my router and modem to the NAT suggestion bungie says, NONE of it worked. I tested my mic in discord, and 21 other games, not ONE single issue.

Razer Kraken X usb

[BanzaiBob]

Originally posted by SolutionS:

The game runs off of some settings in windows. I cant seem to change any output or input device ever specifically for this game. IDK why. Basically when you launch destiny it will use whatever the defaults are in windows. If you change these default settings I think you will need to reinstall the game and delete all local game files. They could fix this like literally every other game and give you the ability to change the audio device for input and output in the games settings.

did all that. even uninstall and reinstall. the incident being referred to is this, running with a friend in pale heart. out of the blue i get booted to orbit off the fireteam with bungie claiming a nat error, your nat setting on your modem is set to low, and you will not be able to communicate in game. My actual nat setting is medium which is has been since I started playing this game. my friend got completely booted off the game from his ps console. Now, no one can hear me, and they cant see my text in the in game chat. I can hear them. but cant see their in game chats. Now you tell me how I am supposed to fix this....

[BanzaiBob]

Originally posted by BanzaiBob:

Originally posted by SolutionS:

The game runs off of some settings in windows. I cant seem to change any output or input device ever specifically for this game. IDK why. Basically when you launch destiny it will use whatever the defaults are in windows. If you change these default settings I think you will need to reinstall the game and delete all local game files. They could fix this like literally every other game and give you the ability to change the audio device for input and output in the games settings.

did all that. even uninstall and reinstall. the incident being referred to is this, running with a friend in pale heart. out of the blue i get booted to orbit off the fireteam with bungie claiming a nat error, your nat setting on your modem is set to strict, and you will not be able to communicate in game. My internet provider actually checked my actual nat setting and its at medium which it has been since I started playing this game. my friend got completely booted off the game from his ps console. Now, no one can hear me, and they cant see my text in the in game chat. I can hear them. but cant see their in game chats. Now you tell me how I am supposed to fix this....

[T3rAbYt3]

Originally posted by BanzaiBob:

Originally posted by T3rAbYt3:

First check the Destiny Audio Guide.

Destiny-Audio-Guide[help.bungie.net]

If it still doesn't work and no one can hear you or vice versa, then the firewall or router blocking ports. Open this ports and see if it works.

Open ports for outbound Traffic UDP range 30009 - 33500.
Open ports for inbound Traffic UDP range 30009 - 33500.

Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types [help.bungie.net]

If Bungie would add a function to Destiny 2 to test voice chat like NAT check if a firewall or router block ports that would be really helpfull.

ALREADY done all that. I actually CALLED a tech guy in and according to him NOTHING is wrong with my system or headset as the same one works in EVERT single game, discord and other programs that use in voice chatting. Meaning its on BUNGIE'S end.

Before i also had the problem with the ingame voice chat that others couldn't hear me or vice versa. I then opened the following ports as described above and since then I have no more problems with ingame voice chat. In the Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types it only says something about port udp 30009. But what my research has shown is that destiny 2 voice chat uses a port range from udp 30009 - 33500. This fixed the error for me. You can enter it for testing if it doesn't help delete it and you're done.

[ShatteredPumpkin]

if you actually buy a new headset every so often because of this then bro your hella lost xD just use text chat or discord nobody uses the damn ingame VC xD

[ThunderHawk]

yep thats destiny for you for me its that i have to restart teh game 5 times before i can play because my game most of the time starts with 8 fps limit since like 4 years

[Prostate Puncher]

Originally posted by redk:

Originally posted by Prostate Puncher:

This is a known issue with this game. No matter what you do to change your in-game settings, and Windows settings (default comms device etc), you'll have trouble being picked up in-game.

Nobody uses in-game voice on PC for this exact reason. Discord is the way.

It works with the Default communication device, you just can't pick your comms device from the game, so you have to set them to default in Windows for the game to use them. And a lot of people use the in-game VC, especially for Fireteam Finder groups, don't spread misinformation.

I'm not spreading misinfo at all. You can set whatever you ♥♥♥♥♥♥♥ want as your default windows comm device and Destiny STILL won't use it. They need to let you pick it in-game but there's no option, and even then, I have no confidence that it will work.

And nobody uses in-game comms to talk unless you're playing console. Everyone uses Discord.