Well here's my stats
Xbox One
Wireless
NAT Type: Open
Packet Loss: 0%
I have several other games on this console (Battlefield 4, PVZ: Garden Warfare, Titanfall)
All of those games work perfectly fine, no disconnections, so I think I can carefully say that the issue isnt on my end.
And I dont feel like messing around with my router just to stay connected to Destiny.
I can play story missions and patrol missions without getting kicked, it's when I try to play crucible or any other form of matchmaking. I can stay connected for about 5 - 10 minutes then I get Error Code: "Bee"
In the long run, I really do enjoy this game, but it will be even better once these server issues are fully dealt with.
English
-
Edited by mikelimtw: 9/22/2014 8:04:34 AMFrom my own experience ERROR BEE is related to general network stability, more to the point a stable link speed. As I test, I ran Destiny with and without torrent downloads running on my PC. Destiny appears not to be as sensitive to the downstream speed - I used uTorrent to limit downstream speeds from 500kbps up to 4000kbps without any issue. I should note that I have a 100mbps connection. However, when I played around with the upstream speeds, I found I had less disconnects as I reduced the upstream bandwidth available to my torrent client. Stopping torrents altogether gave me a solid connection without any drops or error codes. I'm not suggesting that you're doing any downloading in the background, but Destiny does appear to be very sensitive to stable upstream bandwidth. This makes sense as Destiny works like a P2P network, as peers are responsible for passing along game updates to other peers in the same game instance. I can ony guess that as part of Bungie's attempt to provide everyone with a solid 30fps gaming experience, they might have been a bit overzealous in managing in game QoS (Quality of Service). If a client's upstream becomes unstable or lags or whatever other conditions are being checked by the game, Destiny will dump a client when certain conditions or thresholds are met. This is the part of the network code that Bungie needs to fix. Right now, it appears to be overly sensitive. If your router has QoS options, you might want to try and play around with that to ensure that Destiny packets have the highest network priority.