Apex Legends fans slam 'horrible' audio issues on new Thunderdome map

While standard battle royale will always be the bread and butter for any Apex Legends fan, the rollout of incredible LTMs and Mixtape modes over the past few years has given the community plenty of options in the Outlands.

Season 20 has continued this trend with the devs hitting yet another home run with Straight Shot, with some competitors now making it their default Ranked warm-up.

Respawn wanted to level up Mixtape in Breakout, so decided to release the Thunderdome map - a modern twist on the classic Kings Canyon POI that features a stadium filled with a live crowd.

While the awesome sound effects mean the crowd react to your kills in-game, players have slammed the "horrible" audio that makes it impossible to hear enemies.

Thunderdome's crowd audio is annoying Apex Legends fans

Taking to the Apex Legends subreddit, user Feschit has begged the devs to allow players to "turn off the crowd in Mixtape" as they "can't hear s**t" when taking on foes in skirmishes.

These massive "audio issues" are shared by a lot of the community, as it's frustrating to lose a fight to a foe on Thunderdome because they managed to pull off a silent flank.

"Agreed, I love Thunderdome but the crowd audio just constantly blurring the background sound is f**king horrible," said one user, with another arguing, "The Crowd should have its own Audio slider so I can turn it OFF, it makes the map unplayable due to the volume of nonsense crowd noise."

With sound being such a core part of gunfights and outplaying foes when their not in vision, audio problems need to be resolved as quickly as possible. Luckily on this occasion, Respawn are taking action.

Apex Legends devs respond to Thunderdome audio issues

Click to enlarge

Communication has been solid on this issue from the devs, with the team replying to the thread above directly, confirming changes are coming.

"This was flagged earlier and the team is working on adjustments - Added to the Trello for tracking." Given that it's on the Trello board and a fix was already in the works, we can likely expect this to be patched very soon.