1. Marathon Help
  2. Community
  3. Bug Report: Systems, Settings, & Services

Didn't find what you were looking for?

New post
Bungie Answered

Voice Chat (Bluetooth) Weirdness

Avatar
aidypoo

In all my gaming endeavors I use a ROG Delta II wireless headset. Works in every game. Works in Discord. In Marathon my teammates can hear me, but I cannot hear them, UNLESS I switch from Bluetooth to 2.4ghz. For some reason this results in constant disconnects and reconnects, so I don't want to have to use 2.4ghz.

I went through the Audio-Voice Troubleshooting guide, and everything is set up as directed. No dice. I went ahead and bought a wired desktop mic, hoping using that as the input and Bluetooth for the output would resolve this. Nope. Same problem, they hear me, I don't hear them, unless the output is via 2.4ghz.

Tried using Apple AirPods (the only other output device I have) for the output and the wired USB-C mic as the input. Nope. They hear me, I don't hear them. Switch to 2.4ghz, and it just works. But then I'm dealing with the random 5-10 second disconnects at random inopportune moments, which I know is a headset issue and not a Marathon issue, but I can't figure out why Bluetooth doesn't work. Is there anything that can be done?

0

Comments

2 comments
Sort by Date Votes
  • Avatar
    aidypoo
    (Edited )

    Here is the template as outlined in the Bug Reporting Guide:

    • Bungie Account Name - aidypoo#6560
    • Platform - Steam
    • Description of Issue - Cannot hear team voice chat when audio output is connected via Bluetooth.
    • Rough Date and Time of issue - Has been consistently happening since I started playing.
    • Repro Steps - Set audio output to any Bluetooth device. Input device does not appear to matter whether it is Bluetooth or not.
    0
  • Avatar
    Bungie Support
    Marathon Support

    Hello there,

    Thank you very much for reaching out to us. I'm sorry to hear that you are having issues with the voice chat in the game. We've received some reports of this issue and are investigating the underlying issue.

    0

Please sign in to leave a comment.