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 ReplyStarting friday 19/09/2014 I was unable to play Destiny without being interrupted by many errors, mosty beaver. For now, it seems I have got the problem fixed, starting yesterday afternoon. Since that time, I've managed to play online for multiple hours (rough estimate 7 hours) without a single disconnect. *knocks on wood* I hope the problem is solved indefinately now and the beavers never return to my appartment again. The process I took solving it was handed to my by someone from on another forum. I didn't figure this out myself and don't take credit for figuring it out. I have no idea if this solution is area- or ISP-specific, I am not a tech-savvy person and my knowledge of this stuff is limited at best... I found the solution on a tech-related thread concerning problems with my specific modem/internet-connection. For reference, I live in Belgium and my ISP is Belgacom. I'm on the bbox3-modem. The solution was to call my ISP and obtain the PPPoE-username and password. (Note: This was not handed to my by signing up for said ISP.) With PPPoE-data in hand, I was to boot up the PS4 and follow these steps: (Note: My PS4 is set in Dutch. I have no idea of the used English terms, so these may vary from what I type below.) PS4 Home --> Settings --> Network --> Set-up Connection --> LAN-cable Then, when setting up the IP-adress, you have to choose to do it manually through entering the PPPoE-data. After that, follow these steps: DHCP: Do not set DNS: Automatic MTU: Automatic Proxy-server: Do not use When that's done, test your connection. Normally you should be set up at NAT1 with a connection that doesn't give any issues with Destiny. Since yesterday, I've managed to play online in all game-types and haven't experienced a single disconnect. I hope this solution can help other people. Again, I have no idea if it is area- of ISP-specific, but there's no harm in trying, right? If the above does help you fix your beaver-errors, please share this solution with others. Thanks.