{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by ThtGuyNamedJohn:
10/29/2019 4:30:50 PM
1
Error Code Beet
Hi Everyone,
I am a PC player, and have been encountering the "beet" error. It seems that it only occurs when I am loading into Gambit Prime (I believe it has also occurred in regular gambit). From what I understand, this issue is due to networking issues, but I don't encounter this error in any other matchmaking game. I would assume, if I were to have an unstable network, this issue would also occur in Crucible, Strikes, and Vex Offensive. I've found that a few other users have encountered the same issue. Is there something I should check on my end to be sure it is not a user issue? I've reset my network but the issue inevitably occurs again. I have found that restarting the game holds off the error for a game or two but happens again sure enough. I'll put the similar posts I've found in the comments below, for prosperity's sake. It's not "game-breaking" but it's certainly frustrating when I can not complete Gambit bounties, or if the disconnect occurs too much and I'm suspended for a little.
Thanks!
PC Specs:
Radeon RX 580
Ryzen 5 2600
MSI B450 Tomahawk ATX AM4
Corsair Vengeance LPX 16 GB (2 x 8 GB)
-
1 ReplyHere are the other posts I was referring too, 5 other people with the issue isn't a huge amount, but it's nice to see that I'm not the only one encountering the error in the same way. https://www.bungie.net/en/Forums/Post/253850168?sort=0&page=0 https://www.bungie.net/en/Forums/Post/253932297?sort=0&page=0 https://www.bungie.net/en/Forums/Post/253934366?sort=0&page=0 https://www.bungie.net/en/Forums/Post/254051723?sort=0&page=0 https://www.bungie.net/en/Forums/Post/254025980?sort=0&page=0
