Didn't find what you were looking for?

New post
Bungie Answered

The patch has created sounds problems that mute the whole game and its completely silent and its randomly

Here is a drafted response you can copy and paste directly into a Bungie Support ticket or the Help forums. It is formatted to immediately give their QA team the exact technical details they look for, skipping the generic "have you tried restarting" troubleshooting phase.


Subject: BUG: "Silent-Burst" Audio Loop / Buffer Overflow (AMD PC) Since v1.0.0.4

Body:

Hello Bungie Support Team,

I am writing to report a persistent, game-breaking audio bug that has been occurring on PC since the mid-April (v1.0.0.4) patch.

The Issue: During gameplay, all in-game audio will suddenly drop out and go completely silent. After a period of silence, all the queued sounds (gunshots, footsteps, environment) will play at the exact same time in a massive, deafening "burst." This happens consistently across all maps, usually triggering during high-intensity firefights or when multiple sound cues stack up.

Hardware Profile:

  • Platform: PC

  • CPU: AMD Ryzen

  • GPU: AMD Radeon

Troubleshooting Steps Already Taken: To rule out local hardware or Windows conflicts, I have performed the following deep-level troubleshooting, but the issue persists:

  • Deleted the cvars and cvars.old files in the AppData Roaming folder to force a clean configuration.

  • Disabled "Windows Sonic" / Spatial Audio and forced Windows audio to 16-bit / 44100Hz (CD Quality).

  • Turned Proximity Voice Chat completely OFF and switched to Push-to-Talk.

  • Disabled the "AMD High Definition Audio Device" in Device Manager to prevent driver conflict.

  • Adjusted Windows Registry (SystemProfile) to disable Network Throttling (ffffffff) and set System Responsiveness to 0 to prevent DPC latency spikes.

  • Confirmed no background capture software (OBS, Shadowplay, etc.) or virtual audio cables are hooking into the game.

Conclusion: Because the issue persists after all local troubleshooting, and strictly began after the v1.0.0.4 update adjusted gunshot distance scaling, this appears to be an engine-level Audio Buffer Overflow / memory leak. The engine seems unable to process the expanded audio ranges without choking the thread.

I am submitting this so the audio team has a documented AMD hardware case for the upcoming hotfix.

Thank you,

0

Comments

10 comments

Please sign in to leave a comment.