{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by KriTiCaL SiRaNt:
9/15/2014 1:03:45 PM
6
Any solution for "bee" error?
1 week whit the same problem....
Xbox one.
Open Nat.
I dont have a problem in the others games multiplayers.
-
[quote]1 week whit the same problem.... Xbox one. Open Nat. I dont have a problem in the others games multiplayers.[/quote] Answer u customers bungie
-
On Xbox 360 here, but experiencing the 'Bee' issue as well. After years of playing other multiplayer games such as Battlefield Series, Titanfall, heck even all the Halo titles successfully this has been extremely frustrating. Followed the steps Bungie laid out to open up NAT and provide a static IP for my console, but still getting booted out of PvP (I've never been able to finish one match!) and even PvE (mostly the Tower). To say that this issue is related to my network connection only is disingenious and a cop out.
-
1 Replysame problem here - Xbox One (Open NAT Type, portforwarding for all destiny and xbox live ports activated, etc.), but it only appears if there is a huge amount of palyers (6 or above) because in the missions, strikes and the 3 vs 3 pvp mode it works fine but the 6 vs 6 mode and the tower are a big hive of #Bees
-
2 RepliesTo be honest.. I wonder why they still did not release a patch or something like that. I had this problem during the beta as well.. that's why I didn't play it for long. But I don't think this mess is new for Bungie. They must have known about these connection issues since the beta. Normally.. beta tests are there to figure things like this out and make sure they are gone as soon as a game ships. For that reason I am not sure if we can expect Bungie to do anything about it. They've learned about it during the beta and did obviously nothing about it. But at least sometimes my bee becomes a beaver.. maybe that's some weird sort of progress. At least beaver is something they are working on.. error code bee says our connection is to blame.. even if everything else (other games, hd streams etc.) work fine... I've opened all the recommended ports, opened my NAT (Xbox One), switched from WiFi to an ethernet cable.. nothing worked. Some people think buying a new router might work.. but I am not willing to buy a new router for one game because it "might" help. This whole bee thing is clearly something on Bungies end of the line. There are just too many people who are experiencing these annoying bee error codes. Hopefully Bungie fixes it soon. Otherwise they will loose a lot of fans and customers I think.
-
And the staff of bungie, only Copy & paste this direction. http://www.bungie.net/en/Help/Article/11930 Answer your customers pls!.
-
1 ReplyUnfortunately my solution was to buy new gear. Had open NAT wired connection on Xbox One, great connection speed never a problem on any other game but Destiny. For "grins and giggles" I bought my own new modem and router and hooked it up. Since then I haven't had a single Bee error. I know its not the solution you want to hear, but it worked for me. The gear I bought is: Motorola Surfboard sb6121 modem and Belkin F9K1103 N750 DB Wireless Dual-Band N+ Router Again, it's not ideal... but so far its worked for me. On the up side I will now save $15 a month on my cable bill for having my own gear.... shoulda done this a long time ago.
