{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by DuskRaven91:
7/26/2014 9:46:52 AM
10
error codes related to network
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
-
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?
