{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/15/2014 7:51:39 PM
130
Packet loss means bee error SHOW YOUR SUPPORT!
Ok so I have seen Many topics that all say about no tolerance for packet loss being the issue for error codes like "bee". If like me you have tried a static ip, port forwarding and all the other fun stuff but haven't got results, post below. If we get this topic big enough we might get a response.
comment if YOU want to see packet loss tolerance in the game to enable to play the game at last!
English
#Help
-
Packet loss is not necessarily within the control of the user or the server and can be caused anywhere along the trace route. 0 packet loss tolerance is unrealistic. Besides, I know its next to impossible for me as my packet loss on a wired connect has ALWAYS been 0% for years and I have a 2 to 9 ms ping to my ISP server (their server farm is about 8 blocks from my house so that is why it runs almost consistently at the 2 ms transmission ping for impedance.) So 0 packet loss is not a good design if that is what is causing the beaver error that has not shown up until today 9-26-14 @ 12:50 PM. Prior to the last 10 minutes my connection has been flawless since converting to a wired connection.
