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 ReplyDear Bungie, NTS Internet users are now approaching one week of not being able to access Destiny due to the Cattle error on the sign in screen. Could you please provide some feedback as to where you and NTS are in the process of solving this issue? Most, if not all, of the people affected by this bug are beyond the point of frustration with this situation. I believe the ultimate fix to this problem resides in your hands at this point. If that is not the case, I apologize. Every aspect of my internet service works fine except for Destiny. That includes other online games. I know you deal with many, many problems each day, but I implore you to take some time and resolve this issue. It would seem to me that errors like this would take priority over whether or not somebody can see their ship, or similar cosmetic bugs like this. At least those people are in the game playing. Those of us with the Cattle error cannot even access the game to play! Please make this issue a TOP priority if it is not already. I have no way of knowing if it is being worked on due to the lack of information you are providing. Your attention to this important function will be much appreciated!