My system is a wired Xbox One with an open nat, all known needed ports open, and zero problem in any other game.
What bothers me is how inexplicable nature of the Bee error. Sometimes, I play for hours in strike missions and nothing happens. Other times, the thing almost chain crashes to the point where entering the Tower is luck and stability once in there is questionable. There is never any noticeable lag before it happens. I'll be chatting with my buddies and fighting just fine and then bonk. It's like somebody yanks a network cord it's so sudden -- hilariously, I always instantly kicked to orbit and can immediately join my friends again.
I'm in a rural area with limited options outside basic DSL, but it runs other stuff without major hitches. Stuff from MMOs to intensive FPS games. Sometimes the ping could be better, but I never get kicked from games.
It's just bothering me. It's like the server loses track of me for an instance, and instead of buffering, it just drops you from the server or something.
English
-
Same, no lag or anything then bam I'm dropped from the game. Only in pvp matches with over 6 players for me, though.
-
Yeah I'm pretty convinced it's something to do with the amount of other people connecting. My problem is most prevalant in the tower and Crucible. I have finished Crucible matches but most run for a couple minutes and then explode. I've gone to the Tower and things run find, but frequently get bee'd. Seems like when I finish a match, the numbers stable -- see not lots of new people loading into the match after it starts. The overworld and strikes work MOST of the time. But when they do crash, it's almost always with lots of other players running around (typically when people load in).
-
[quote]It's like the server loses track of me for an instance, and instead of buffering, it just drops you from the server or something.[/quote] That's what I was thinking.