Repost of a previous topic of mine, with some additions. Bungie, heed my tests. I'm trying to help you. As always, bee everywhere. Xbox One, DMZ, Open NAT, all suggested ports forwarded, on the least crowded channel, not on a campus, wireless internet, 0% packet loss. But it's my end. Yeah. Anyways, I'm doing testing, and will update this after more testing. Here are some tests and results. TEST: Wired vs. wireless RESULTS: Wired or wireless, still be. TEST: See how many games out of ten that I can get through in Iron Banner. RESULTS: One. And I lost. This is great for IB rep. TEST: PvP areas affected. RESULTS: Iron Banner, Control, Clash. TEST: PvE areas affected. RESULTS: Occasionally the Tower. VoG is affected heavily. TEST: Bandwidth? RESULTS: Disconnected everything but xbox from wifi. Bee. TEST: Account specific? RESULTS: Brother's account. Bee. TEST: ISP/router/modem specific? RESULTS: Neighbor with same ISP, router, and modem. No bee. TEST: Any signals it gives before occurring? RESULTS: None common enough to make me believe so. CURRENT FINDINGS: Bee is not cause by packet loss. Bee is not preceded by lag. Bee occurs wherever there is a team of 6 (includes Control, IB, Clash, VoG, and occasionally tower. team does NOT mean fire team). Bee is not specific to any ONE thing, be it ISP, router, or modem. Bee is not affected by wired vs wireless. Bee is not affected by bandwidth gain/loss. BUNGIE: Stop telling us that it is our internet. My findings prove that it is not. Don't tell me there is a 53% reduction in bee errors when all I see in these "forums" are more and more people coming with bee, and none saying "thanks for fixing bee, bungie". I love Destiny, I really do. But when you bring out the Iron Banner with only a 6v6 mode that those of us with bee CAN NOT PLAY, it is very frustrating to us. We know you're trying to fix the issue. I know centipede/zebra takes priority. But, please don't mock us with the Iron Banner. And please stop repeating the same old " it's you, not us; open your ports". We believe in you guys. Please help us. EVERYONE ELSE: Any suggestions for more tests I can do? UPDATES: It seems in the last weekly update that bungie has at least partially admitted they screwed something up with bee. Instead of saying "x% of players don't get bee anymore, trust us!", they now admit that the update actually made MORE bee errors happen. I believe this is the first time in a weekly update that they've said anything about bee? If it is, then we finally have their attention, which brings us closer to some bee repellant. Bee seems to only be affected by certain people (if my theory is correct). It seems very odd do be just a coincidence that I didn't get bee for a few matches in a row with the same people. And this has happened a few times, I just never really though much of it. It seems that if I can make it through a match, then I can make it through three or more. Though it is beginning to seem like we are dealing with multiple errors all labeled as "Bee". It seems there are people who: Can play strikes and 3v3, can't play VoG or 6v6 Can't play strikes, can play all crucible Can't play 3v3, can play 6v6 Can't play anything without fear of bee It seems to be a problem with many variants, which could make it even harder to solve. [quote]Further, I've played Destiny and then put a super heavy load on the network using other machines. This is an an attempt to induce the error through adverse network conditions. I've run speed tests, downloads, and ping loads while playing Destiny. I don't think I've ever been able to force the bee/fly/lion this way -- maybe 2 or 3 time but they may have been purely spurious because the crash happens a lot anyway. So it seems that when I try to force horrid network conditions the game will not crash; rather, it will crash randomly regardless of network conditions. I totally think it has something to do with how many people are around you. I rarely crash when playing alone. Although crashes will happen on Patrol sometimes when other people phase in to my game. Same with the tower. Low population towers rarely crash. Strikes are a mixed bag same with 3v3 pvp. Crucible and VoG raids always crash sooner or later. Never any lag and I frequently can play for a while before the crashing. Somehow the game is muffing the p2p hosting and I don't know why. My nat is open all ports are forwarded. NONE of my other games regardless of system do this. [/quote] Let me be clear here: The purpose of these tests is not to shame Bungie. It isn't to yell about how Bungie isn't doing its job, or doing it poorly. This is not meant to be a Bungie hate topic. This is a topic to HELP them. With these tests, I'm trying to show what may or may not be causing the problem, and what things have no effect on the problem. We have to understand: the faster Bungie can get good information, like these tests, the faster they can learn about, and eventually fix, the issue. And [url=http://www.bungie.net/en/Help/Article/11791]here[/url] is the link to the Bee/Fly/Lion update page.