I have seen many of these threads, but it seems that most of the posts are just people ranting and complaining. I will say that I am quite guilty of that as well, and my patience is growing thin, but I think we should try to provide Bungie with more specific information so they can get our issues fixed as soon as possible. Please post your specific issues in here, and try to keep it short-ish, to the point, and present it in a professional manner so they don't have to comb through garbage to find what they could possibly need.
I'll start by saying:
I'm on the Xbox 360. I am on my home network. I get mostly just BEE and CENTIPEDE after entering any game zone. I can sit in orbit and stare at my ship for hours, but even entering a mission, strike, crucible match, or the tower nets me a BEE error within 2-10 minutes. I'VE HAD THESE ISSUES SINCE DAY 1. I've tried all the workarounds mentioned on this site (NAT Type, opening ports, QoS, disabling flood protection, DMZ server, static IP for router and console, hard resetting everything multiple times, deleting system cache, deleting and reinstalling the game, using a VPN, going wireless and wired, and multiple combinations of all of these)
Any help/reply would be appreciated. We must keep hammering them until we are heard.
Also, pass this around the forum:
http://arstechnica.com/gaming/2014/09/eight-days-later-bungie-leaving-disconnected-destiny-players-stranded/
^This is getting ridiculous. We are not a tiny portion of the community.
-
1 ReplyEdited by Baumguy: 9/20/2014 2:06:52 AMI thought it was just me... I've managed to get to Level 22 doing nothing but Story Missions, but that's only because I've been rushing from checkpoint to checkpoint in between disconnects and "resuming" my progress. I'm usually kicked anywhere from 2-5 minutes into any Strike or Story I get into (although I got about an hour in doing the Weekly Strike Solo earlier today, but that's more of an exception to the rule), and I'm usually kicked right off the bat for Patrols and Crucible. This has been happening for me since day one. Both my roommate and I have been trying different things to get Destiny working. I've tried forwarding the ports and setting up a static IP using the guide on Portforward.com, and when that didn't work, we got the ISP to come out to fix it. They've been here twice and can't find the problem. We've also tried using a wired connection with nothing else connected, and that didn't work either. We're not really sure what to try next. The only thing I can think of is that we have a NAT Type 2 and not Type 1, but from what our ISP has said and what I've seen on the internet, we should still be able to get online even with Type 2, so I'm not even sure that that's the problem. Anybody have any tips? Also, I've been getting a ton of different error codes, but the most persistent ones are Bee, Lion, Fly and Eel. I've seen Jackrabbit and Elderberry once or twice, and I'm sure there are others, but I can't think of them just now. I don't think I've got Centipede even once, so I don't think it has anything to do with those problems.