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.
-
5 RepliesI still can't play Crucible (the error is always bee) - I can enter the game but I then get lag which gets increasingly worse. I get booted eventually when the mismatch between what happens on my side is so out of synch that I get a kill 2-3 whole seconds after firing the terminal bullet. From the start of the match I can almost hear it grinding and groaning trying to keep up. I also get thrown out of the Tower quite often. Strike and Story missions are fine. I admit I do have a relatively poor internet service (rural, ADSL, 5Mb D 0.3 Mb U, 100+ png) but have not had difficulties with any other games (e.g. BF4). I have Xbox One with a wired connection, static IP and port forwarding on the HomeHub4 BT modem. I tried changing the DNS settings to Google's instead of the one's automatically allocated by the ISP - that allowed me to play 2 games on Crucible. I thought I had found an answer, but then I got booted on the 3rd game and I have not been able to play since. It may be stating the obvious, but I can't help but wonder if having less production time devoted to naming errors may have afforded the opportunity to spend enough time and intellectual effort recognising and solving this galring issue, which was pointed out at least as early as Beta. So far though, I am enjoying what I can play of the game and I am looking forward to playing Crucible.