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 Replyhttp://www.bungie.net/en/Forum/Post/69265642/0/0 My problem is mentioned in the link above, as well as the workaround for "marionberry" which is a temporary fix and really not acceptable ! But better than nothing I guess. In short. Xbox 360 Home Network Tried all Methods you offer to Troubleshoot in #marrionberry Still Happens on Wired connection as well btw... I'v had this Issue since the beta (marrionberry) i have posted here back then as well link : http://www.bungie.net/en/Forum/Post/66833572/0/0/1 So as some one here already stated, We had those Errors back in beta (that is the purpose of the beta isn't it ? ;) (looks like some one didn't finish hes Homework / "Network" ;) Big F if i was to Grade it... ;) Bungie its time to step up and ACKNOWLEDGE That this is a problem with your Servers Not our connection/hardware or anything else you might come up with ! (didn't see here on the forums no one complaining about and error called "Chooks" ;) So to conclude Bungie ITS YOU ITS NOT US ! We cant #Helpyoutohelpus , Its a one sided Problem on your side ! (Ahhhm Servers/Net-code , W/E it is its Yours to FIX) So its time to announce on the Main/home Page of your site An Acknowledgment. (See How Rockstar Handled her self With the lunch of GTA V Online.) what are you doing to fix it ? and regular updates with progress ! We your loyal fans and customers are eager for Information any thing official from you will go a long way IMHO just my 2 Cents ;)