I would first like to thank bungie for the splendid work. I would just like to share to you my error codes. it happened to me several times to get very annoying error codes that have made it very difficult to play in PVP: BEAVER BEE and flatworm. I could not play much in pvp just because of these errors,which didnt let me finish several matches, disconnecting and sending me to the main menu on the reporting resulting in penalty for being out of the game still in progress. I checked the following topics related to network connections http://www.bungie.net/en/Help/Article/11930 and performing various tests have not found errors: NAT is open, the test speed from the site that you have put in the guide gave me B vote and multiplayer test on xbox one did not give any kind of error. I noticed that while playing, sometimes, i can see a message on the bottom of the screen that says something like "connecting to bungie servers". I wouldshare with bungie team and other players my ERROR CODES and ask if they are due to the beta or my internet connection. as always very good job bungie
-
i keep getting BEE and FLY error and i know it is not on my end like they say this is the only game that does this to me
-
I'm getting error codes for internet connectivity as well...fly and lion are my codes
-
Ye i got error codes when i play on the moon with friends but then i get disconected and the error codes are mostly flatworm and bee thingie i dont know the full name of it but i hope that bungie gonna work on it but it is a very nice game thanks bungie
-
I would just like to know if bungie is working on this error code thing.
-
Hello, this problem is happening to a minority of users, so I have done the ping test with rated A, and open nat! But the problem does not go away, I can not finish a game PVP! Bungieee FIXXX error BEE!!
-
gotta be the game bro i have 75.58 mbs internet speed and game online all the time on ps4 and pc and never had issues untill i played destiny. All i can assume is that the servers are overloaded with people trying to play.
-
despite getting a strict NAT error warning at the menu screen, I've played the destiny beta since the start and have never had any connection problems. But since the game came back online on Wednesday, I've been disconnected out of the game and back to the menu screen several times with increasing frequency as the week's worn on. The error codes I had were beaver and caterpillar, and today (Saturday 25th) I was disconnected 3 times in one hour with the codes quail and leopard, once while in explore mode, then twice at the crucible at the end of a match, while waiting for a re-match I've read a lot of info about the NAT settings, including player's comments, and it seems people can receive the strict NAT error even if it's set to NAT1 or 2, and even changing the NAT doesn't necessarily solve any problem - I'm not remotely a technically inclined, so even attempting to change my NAT settings is abit over my head but as I said, I've played the beta since the start, playing hours without problems, so why have I been getting disconnected so much since the game was re-booted on Wednesday? Is this simply a beta problem to be ironed out?
-
Yea, it is the game. I have a great network, and even went into my router to check for anything wrong. I realize it's a beta and they are going to have problems, but how can we stress test this game if we can't play it? I hope the full version isn't like this, and hopefully they don't push back the release date either. Other than that this game is awesome.
-
same thing for me and i've called my provider and its fine so im guessin beta bug 360 but its happening to all consoles please help bungie!!!!!!!
-
I've gotten a couple errors while exploring Old Russia too, leopard and flatworm errors, and both times I've gone to look them up the Bungie website said it was down for maintenance. Not sure if it's connected though since I don't think everyone is being kicked at that same time.