{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/16/2014 6:39:35 PM
7
BEE ERROR! Port forwardind did not help.
I keep getting ERROR BEE, over and over and over and over. Unacceptable. This is a serious issue that Bungie NEEDS to address. I will [u][b]NOT [/b][/u]be purchasing the season pass and pay more money to not be able to play the game. So far here is what I have tried.
Reset EVERYTHING (modem, router, xbox, tv [ha] )
Check internet connection: Superb
Check modem: Perfect
Check Belkin Router: Operational
Set static IP set for xbox
Xbox Live port forwarding: added (according to bungie's recommendation)
Destiny port forwarding: My router says that the ports destiny wants are "invalid numbers"
When playing a mission with two friends, I was kicked from the game a total of SEVEN times in the space of the level, I kept joining back in and spent literally over half the time of the mission on a stupid load screen.
Does anyone have any useful information pertaining to this error type?
I would love to play this game, if i could.
-
4 通の返信FIXED. The culprit was my out of date router for me. I suspect that this is the case for a bunch of folks. I was told by a former Xbox call center rep that Belkin routers are the worst choice for Xbox. And mine was 8 years old. New router, not even one DC. From anything.
-
Every time I have go into Crucible I get the Bee error code. Bungie this has been going on since day one when I bought Destiny. It is not my router, ports or network configuration as you claim because I can play story with no problems. When will you get this error code fixed? This is ridiculous to sale a game that can't be played in the areas that you are promoting. No video game is worth this aggravation. Do something to satisfy your customers/clients and give us a timeline that this will be fixed. I have made it to the end of one crucible match and your silence and outright lack of communication shows the regard inwhich you hold your customers/clients. Going live is not an excuse to be silent.
-
1 返信I get this same error and get booted every 5mins or so and it seems to only happen when playing Destiny. When I'm playing BF4 I don't get booted at all.
-
Yeah I get this everyday. I can seem to play story/missions with the occasional bee error but crucible specifically 6v6 is something else. Every f***ing game I get kicked out so I can't play with my clan. I know I'm lucky enough to play missions and 3v3 crucible but having this bee error show up everytime I join my clan on control is beyond ridiculous. Bungie need to focus on multiple error codes rather than just centipede because I along with many others are considering selling the game and never playing it again.
-
4 通の返信i hate to break it to you but that's what you get for buying an XB1. have you checked the tech specs? it's inferior to PS4 in every way. i'd imagine their Xbox Live "service" is probably screwing you up. i've been getting the occasional DC but it's only from crucible and it rarely happens, only because i use a wifi router thats downstairs.
-
1 返信
-
1 返信Going to just pass this along because it might work for some others. I have been having problems all week, ranging from centipede, to lion, to caterpillar, and bee. The first time I've been able to play for more than 5 minutes at a time is today when I unplugged my wired connection and hooked my Xbox one into my wireless instead. To be clear, I have also previously gone through all the steps everyone else probably has. I have set up a static IP, set up port forwarding as they have suggested, uninstalled and reinstalled, etc. It doesn't make sense to me that moving onto a less reliable connection has fixed my problems, but at the moment it seems to have done so. I honestly don't know if this will help anyone else, but I figure if there is even a chance...well,better to mention it. Good luck!
