{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Steel Revenant:
10/2/2014 12:03:41 AM
1
Ports forwarded, wired connection, cache cleared, and still getting bee errors. Obviously this is on bungie and not a personal router issue. If someone plays without a bee error then give it a little while, it'll happen. It's been hit and miss on whether I have a day without bee errors but it seems like once it starts, it continues for awhile. It's ridiculous. The claim of 53% reduction in new errors by bungie just means it's got a 47% failure rate, and to be honest I think even their claim is false as it seems a lot higher than that. I'm thinking their figure of 53% less failures is actually due to them losing 53% of their player base due to all of these errors which has showed 53% less errors being reported than previously because there's less total people actually trying to play now. The decrease in reported bee errors is only because there's less people still around to actually report said errors. If no one is playing this game then no one's reporting errors. Good job on the fix bungie!!!
English
-
Exact same for me to man it suck so bad! The game is fun but what is a fun game when you can't play it! The only ó thing setting that people have been switch which they have claimed to work is going to the Detailed Network Statistic page on your Xbox One or PS4 and looking at what the MTU listing is, then putting that value in manually into your router. (Usually 1480 on the game system) For me it improved a tiny bit but I am still getting disconnections every 2-5 minutes along with no hope joining a crucible match. ): #Help
