{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Zalgarad:
4/20/2020 3:04:19 AM
1
Error code beet
I’ve gotten kicked 7 times within a 2 hour session from trials with the error code beet. This is unique to me playing trials, all elimination rounds I’ve played today have been without problem but I’ve been having a lot of difficulty staying in trials games. I’ve done everything I can on my side; reset Xbox, reset WiFi router, decrease internet load in my house, and nothing has kept the beet from happening. I’ve been fireteam leader sometimes and sometimes I haven’t. There’s no connection I can find between each time of getting kicked, and network manipulation would be unlikely just due to how frequently I’ve been getting kicked and only me out of my fireteam. Any ideas?
-
Bungie is actively tracking this general networking error. Players that repeatedly receive this error may want to consider following the suggestions in our Network Troubleshooting Guide. Additionally, players on consoles may wish to try clearing their console cache. PC players that repeatedly encounter this error may have PC hardware that is below the minimum specifications. To help improve performance, they should try closing other programs, ensuring all drivers are up to date or running the Scan and Repair tool. Players may sometimes encounter a BEET error when they are launched into a private match with a lobby of 12 players. Players who are returned to Orbit from a private match due to this error may rejoin the private match in progress by directly joining a participating friend in their roster screen.
