I am sorry you are having difficulty connecting. it is true that the BEE error usually indicated packet loss issues. We post updates to the following error page if we have any new information.
http://www.bungie.net/7_Error-Code-BEE--FLY--LION/en/Help/Article/11791
English
-
Getting continuous variety of hawk, bee, cattle vulture errors like the above. Same configuration options tested. No luck. Also, able to successfully play other games (the opposite of what you want). All of this started occurring after downloading 1.0.2 patch. I had minimal to non-existent problems before the patch. Now I can't play the game. Not even for one minute before being kicked out.
-
That page says that since the 25th you did nothing to address this, believing that 53% of the users are not affected anymore. Well from the 47% which I'm part of I urge you to fix this problem (not being able to play one MONTH after the release is ludicrous)
-
The update on that page does not mean we have not done anything. The team is working diligently to fix this issue. and we will update that page when we have more information.
-
Good, understand our frustration in not being to play a game without dropping out since the launch ( this morning I felt the excitement of playing four straight games without bee....it was exhilarating)
-
Hello! I'm having bee errors in 95% of my crucible matches and occasionally while wandering around the tower and it's getting really frustated... I'm having them since launch and never had any during beta. I already tried every piece of suggestion and fix for this but while i do see an improvement over ping, overall stability i continue getting bee bee bee... It's reeeeally frustrating. And although i usually can complete vanguard assaults and other coop missions just fine, sometimes it seems like i'm playing all by myself. I can't find anyone though matchmaking, theres noone in the tower etc etc... I don't know, maybe those two things are related?? Anyway, i'm checking the bee error page everyday looking for updates and eventhough the page claims to be making some progress with 50% reduction, my bee error frequency seems to be increasing everyday. Please, please get this message though to the dev team so they can hurry up and fix those issues because i'm really starting to lose faith in this awesome game. Thanks in advance.
-
im in the same vote. ever since sunday ive been slowly swarmed by bee errors day by day. right now I cant even stay on either pvp or pve for more than 5 min without being booted. tried everything and nothings worked don't know what to do now, guess ill play something else till it fixes itself.
-
As someone else stated, thank you for the reply. But I have checked and double-checked and triple-checked everything on my end. I've troubleshot (is that a word?) my modem, router, and Xbone with no effect. Even changed out our modem for a newer gaming-friendly one, as it was about 2 years old. But I cannot get through a Vanguard without getting BEE, then an immediate CENTIPEDE before being sent to the home screen. I understand and honestly really do appreciate when you say you're working on it. But these errors are not coming from the user's side.
-
Ok. So if it USUALLY indicates packet loss, what's the other thing it could be? Maybe something wrong with your servers yeah? These people have all tested for packet loss and came up with nothing I'm sure. And you just keep singing the same ole tune...
-
I totally appreciate the reply. But it's just getting old. I'm doing a bounty just now. Play through an entire Venus strike with zero problems. Right when the boss dies, and prior to getting credit for it, the game Bees out. Then I sit in orbit and eat a centipede (even though these ports are open and I'm on a residential connection). So I get booted to title. And I immediately can re-access the game. My router diagnostics do not report any packet errors in the past hour. I ran one Mars strike in this period with no problem. Two conescutive Venus missiosn ended in bee. Nothing else on the network right now. Like usual, no lag or any indication the crash is coming.