{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/19/2014 10:49:54 PM
9
In addition to changing your NAT type, have you also followed the recommendations outlined on the [url=http://bungie.net/networking]Networking Guide[/url]? If not, please refer to that page for information on how you might improve your connection quality.
English
-
This f* bot is pissing me off... ITS NOT A PROBLEM WITH OUR CONNECTION!!! ITS SOMETHING IN YOUR SERVERS!!!
-
Edited by txomin: 7/24/2014 6:16:44 PMI have a great result but the error code "bee" persists http://www.pingtest.net/result/102588430.png
-
[quote]In addition to changing your NAT type, have you also followed the recommendations outlined on the Networking Guide? If not, please refer to that page for information on how you might improve your connection quality.[/quote] I am also getting kicked out of crucible matches almost 100% of the time with the error code Bee on the XBOX one. It seems like the only response you are giving for this networking error is for us to go to the networking guide, which seems to imply that the problem is on our end with our connections. After reading numerous posts and from my own personal experience the networking guide doesn't help with this issue because it seems to be happening to people who have good wired connections, open NATs, and low packet loss which is who the networking guide seems to be geared towards. Can we get a confirmation that the problem is mainly on Bungie's end and not ours? If it is on our end what other troubleshooting can we do other than the simplistic answers given in the networking guide? If it is on your end will you confirm if you guys are working to fix this issue?
-
thanks, everything is well configured, the problem was temporary, I understand that the problem was not mine, after I played without problem, just wanted to report it as a feedback
-
What did you do to fix the issue?
-
I did nothing, I left the game and return to enter, I know this is not much help
-
Unfortunately, the networking guide only helps if the connection is a problem. I have had a lot of time spent getting the best connection possible and knew that wasn't the problem when I started getting booted. I think if you lose connection once, you get corrupted data and you will start losing it repeatedly. I was getting the bee error and rebuilt the database of my PS4 and it went away. This is a fairly common fix for Ghosts after updates and DLC downloads.
-
I did... all of them... even before playing beta... since alpha i got all this settings, and i always use cable networks for my consoles... :( it is frustrating because i really really was waiting for this beta, and actually i played a lot more in alpha :( please help with that.
-
i have the same problem but only on PVP i can reach a PVP game, but after 1 min i'm always kick, code error BEE. i play on PS4, my console is always connected by cable, and i have no problem with all other multiplayer game.
