Players continue to experience frustration due to the persistent Guitar glitch in Destiny 2, which inexplicably causes the game to crash during critical play moments. This issue, regrettably, has been present since the game’s launch.

In simpler terms, since the beginning of D2, the “Guitar” glitch has been a recurring problem. When this error message pops up, players are unexpectedly kicked out of the game without any apparent cause.

In simpler terms, Bungie has pointed out that the problem arises when too many items are left uncollected during gameplay in Destiny 2. This is a memory-related issue, meaning it pops up if players don’t gather resources like Glimmer or Orbs of Power from the ground.

After more than five years, players are extremely frustrated as they’ve yet to receive an appropriate solution to the problem. Moreover, the persistent error messages are spoiling the enjoyment of the game’s latest updates.

Guitar error runs the risk of making Destiny 2 “unplayable”

A disgruntled Destiny 2 gamer voiced their difficulty with an issue that surfaced during gameplay in the Onslaught: Salvation mission, specifically at Widow’s Court.

In their Reddit post, the user mentioned that an error occurred during Wave 49, which was particularly frustrating because it was just one wave away from finishing.

The player stated that the issue has escalated far beyond an annoyance; it’s become a game-altering problem. They could handle it occurring during routine missions, but finding it in seasonal events is the final straw for them.

In the comments section, fellow Destiny 2 players have expressed their agreement that the Guitar glitch should be addressed too.

One individual mentioned that the game has been increasingly difficult to play due to frequent errors while running The Pale Heart.

Another user mentioned that even though they desperately desire the Arc Conductor Ergo Sum, they haven’t interacted with The Pale Heart for several months due to a persisting issue.

Although Bungie has tackled this problem in previous years, they haven’t implemented a solution that completely solves it as of now. Given that the issue appears to be related to memory management, it seems connected to the custom Tiger Engine which underpins Destiny.

Read More

2025-01-06 04:23