There isn’t much going on in the actual game of Destiny 2 this week unless you want to beat your head against a wall for the nightmarish Grandmaster Nightfall, the Ordeal, and yet something massive appears to have happened all the same for PC users.
No, not anti-cheat, but Bungie announced that they apparently solved the ongoing Beaver error issue that had been plaguing Steam players for months.
This would often be caused when you would load into a zone, nothing and no one would be there, and then you would get booted either to orbit or to a reloaded version of a zone. I had experiences where I would try to load into the Tower 5-6 times and get beavered every time.
This would ruin Crucible games, raid and dungeon runs, tons of stuff on PC, but finally, it seems to have been brought under control according to Bungie:
Bungie says that Beaver errors will still exist in the game for normal connection issues, but the ones that were happening all the time for no reason seem to be gone. From what I’m seeing from the community, and from me loading into a ton of places just now to test this, there are apparently very, very significant improvements.
The Destiny community seems to believe that this recent fix may be tied to something that Valve had to find and fix themselves, citing this tweet, also on July 16, from an engineer there:
So, this would mean that there was literally a hardware problem that could have been causing this issue, and the hunt for the “fix” in software was why it took so long to address. And it wasn’t actually anything on Bungie’s end. But it’s not confirmed that these two things are definitely related (one big coincidence if not, however).
Nobody likes to fight connection errors when playing a game and Beaver errors have destroyed too many activities to count in Destiny 2 the past few months. I’m not 100% sure we’re out of the woods, but things do seem to be a lot better on PC for now.
The next thing everyone wants for PC is again, anti-cheat and better detection and elimination of cheaters, which seems like no less of a problem now than it was months ago. On console, I’m starting to hear the DDOS issues are becoming a problem again, when that was supposed to be mostly solved a while ago. So there’s always something.
But goodbye Beavers, I will not miss you, and you were not a good “you had to be there” moment.