{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by BNGHelp1:
10/23/2014 12:20:56 AM
4
beeeees
Been getting a ton of bee errors lately. Not sure what's going on. Currently I have the PS3 set as the dmz on my home network so there shouldn't be anything between it and destiny except Comcast. Usually I can play for a bit and then once the errors start it seems to be a cascade style effect where they keep coming. Sometimes it includes other animal codes like cattle, buffalo, centipede and sometimes not. Any thoughts? There usually isn't any other network activity happening when I'm playing. Also it's a wireless connection. Wired is unfortunately not an option.
Thanks!
Edit: grammar
-
2 RepliesThe bee is still an ongoing issue, the latest updates from bungie can be found here: http://www.bungie.net/en/Help/Article/11791 If you want to check the status of other error codes, check here: http://www.bungie.net/en/Help/Article/12207
-
one in a blue moon I'll have a flawlessly smooth game. It's whenever a game gets over 10 players that the bee errors appear. Sometimes 12 players doesn't matter. Clash is more stable than Control. I'll be in a game and it's going smooth but then I get the warning message. Console can't communicate with Destiny servers. Sometimes I get booted when someone rage quits , leaves, or triggers the mass bootings. sooo and soo leaves the game sooo and soo leaves the game die can't respawn... spawn timer stuck. respawn tryting to communicate with Destiny servers boooted other times respawn can't communicate with destiny servers can't communicate with destiny serves back to orbit ... error code bee It happens in games with no lag. The game has a hard time respawning me in 6v6 games. Error code bee errors happen most during spawning.
-
2 RepliesWell, the being in the DMZ or not shouldn't impact BEE errors, as those are packet loss causing an inability to stay connected. Open NAT, etc. won't impact the number of BEEs a player gets. If wired is not an option, it might be worth boosting the signal of the wireless hardware with a better antennae, changing the channel of the wireless router, reducing the use of 2.5GHz or 5GHz devices that could be causing interference. Aside from updating the firmware on your existing hardware, or getting new hardware there might not be much you can do on your side. Side note: Even if wired isn't a permanent option, it might be worth temporarily trying to play wired to see if that solves the BEE issue. If it solves it you can troubleshoot your WiFi setup. If that DOESN"T solve it then it probably isn't worth your time to troubleshoot your WiFi. At that point it might be worth calling your ISP to figure out what might be happening. We will continue to tweak our settings to reduce BEE errors.
-
3 RepliesEdited by BurgerFredFred: 10/22/2014 10:32:14 PMI'm not really sure what the reason is for these issues. It's the same thing for me except few minutes ago I was able to log in for the first time since early Saturday. Though I also moved my ps4 from where it was to only a foot away from the router. Maybe the last update messed up how sensitive the game is to the network?
