So many players are having problems with connection and error codes. You go to the page for help and Bungie say its your server. But why is it [b]I can play any other online game[/b] and never get booted from the game? But as soon as I join the bungie servers I get weasel or bee, and even anteater? This for me has only happened from the last update, but others in our clan its been going on longer. This is putting such a downer on this amazing game its making me not want to play it. Or if I do I won't try any strikes, raids as right at the wrong time you get a error code. Anyone else have there chat turn off, get ready to see the loading screen.
Why would anyone come on to a post on a error codes page to click NO option in a poll about error codes.
[b]Thank you Bungie, I see on other post that you know there is an issue and your trying to fix them. I do apologise for the way this post went. [/b]
-
47 通の返信1. Please refrain from comparing other games to Destiny 2. Destiny 2 requires a much more stable internet connection than other games. This has been stated countless times. Just because a different game works, it might not have as strict of connection requirements as Destiny 2. Destiny 2 requires near zero packet loss to maintain connection while most other games do not. 2. The only time I have ever experienced issues is when my ISP has an issue, so I suggest you start with them and ask them to do a complete quality of signal line test. Speed tests and basic connection tests do not indicate if there is an issue with packet loss.
-
2 通の返信
-
1 返信"I can play any other online game" Try Happy Dungeons, makes it feel like Destiny actually is running on Dedi's
-
I constantly get the broccoli error now making the game unplayable. I've tried literally everything you can find on the web for this problem and nothing has worked. I played this game for ages when it first came out with ZERO issues. Came back to try and play again after all the expansions and forsaken was released(exact same pc), I spent over $100 on this game and I can't even play for 10 mins before I get this error. This issue is a bungie problem and it needs to be fixed. I need info on this.. at the very least can I get a "This is a know issue and we're looking into it."
-
1 返信Not as bad as the first destiny game but I have noticed way more errors since last update and really long loading screens between areas.
-
1 返信The issue for many Is their own systems. This isnt any other game, many have not forwarded ports, continue to run wifi and have many devices running on one modem etc. This is not optimal. Bungie recently stopped the leave penalty for Gambit for just this reason, people with poor connections were regularily getting the penalty.. Honestly, this is exactly what I want. I pay a premium for my internet, I take the time to setup my router and modems, run dedicated lines and ensure the bandwidth is set for my ps4 to hogg 98% of it when I play. Many just don't do this at all.
-
I had the same problem since today ! I got some lags friday and saturday. But today it's really impossible to play !!!! 5 disconnecting in 15 min ! Bee Anteater, etc.... 1 year i play D2, no problem like this.....So if Bungie say it's our fault, they lie !!!!!!
-
19 通の返信I know I have crap internet, 5-10mb (not lying) but I’m getting these codes as well and I know it’s not my internet cause YouTube and everything else works fine
-
1 返信[quote]Why would anyone come on to a post on a error codes page to click NO option in a poll about error codes.[/quote] Maybe you should've posted a poll with only "yes" options or titled it as "only click the Yes in the poll I created just to try and get people to click that option because that's what I want to see in the POLL I placed in a public forum".
-
9 通の返信. After getting on and playing for four minutes I get a weasel code. Doing a strike and we are at the final steps to the end I get a weasel. Doing a gambit match and my team is winning I get a bee code and it returns me into the match and now the team is down and behind. These connection problems only started happening and only on this game.