Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
All things in computing happen for a reason.
Many (most?) players play without this problem.
Where do you think the problem might lie?
Only if "coding" means "your client and the properties of its network"
Every Forum you'll see people complaining about Connection Error yet when they play other Online games has zero issue.
So STOP Defending Bungie and Blaming Users for their Internet.
1) A player is in a busy metropolitan area where there are many other destiny players. When he looks for matches the game always finds someone nearby and sets him up as the host for the match. In that area everyone has good connectivity and by being close by they all have little latency. The result is that the connection between all the players is good and thus they hardly ever disconnect.
2) Another player has good connectivity but is in a city with few destiny players. So, if the host of the match is nearby he gets a good connection. But if there are few players at the time he might get assigned to a match halfway across the world. Of course, even if his connection is good he will still have a bad connection due to the distance. So, as the game has fairly simplistic logic, it will think that the high latency means the player has a bad connection and boot him from the match. He is hurt (and maybe even banned) even though his connection is good (locally) and if there are enough local players he would not have problems. And of course everybody in that match gets hurt because they are now one (or more) player short. Finally, whoever gets put into the game will also get hurt as he will be far behind in a strike or join a team that is losing in PVP from being short one or more players.
3) A player truly has a bad connection. Maybe he lives in a rural area of the US (where I can tell you from past personal experience) the connectivity is horrid thanks to internet deregulation from 10 years or so ago. Or maybe he is in China or a 3rd world country where the internet is just bad. Or maybe he is in a country where there are no net neutrality laws and thus ISPs throttle traffic that is not from major paying broadcasters (and a player serving as host is certainly one that would get throttled).
These are the realities of today's internet, and they explain why some people rarely have problems, others have occasional problems and others yet have constant problems. The player might have a perfect connection to his ISP, but depending on who he gets connected to as the host... he can still get bad connectivity and get dropped. And there is nothing *he* can do to fix the problem.
In the end it is only the devs that can fix the issue, and since other games have no problem making their games work fine for these exact players... It is clear that Bungie devs dropped the ball.
..and Rockstar devs, and Bethesda devs, and devs of every other P2P game. Go read the GTA Online or Fallout 76 boards, or the boards of any online game. This is not a problem unique to Bungie.
Peer to peer works for most people and is a pain for some, just as servers work for most people and again are a pain for some, if devs could magically solve it with Juju dust they would because contrary to what morons say on the forums they don't actually like people having problems with the game. So people who say things like 'X studio don't care about cheats' or 'Y dev are crap coders' just sound like butthurt children.
A company with a turnover like Activision had, and now Bungie has, can easily hire in coders that know their stuff so to accuse them of scrimping sounds petty.
After doing a bit of research I found that atleast in germany it is a problem with vodafone as provider. Some users tried a pingplotter and disconnects always happened when a server er1.ams1.nl.above.net (in amsterdam I think) lost connection for a moment. Bungie says go to your provider, the provider says go to the carrier and the carrier says only the provider can make support tickets for them... my provider doesnt really care tho to change something about the routing
if someone is interested I can link the original thread, just be aware that it is in german
And I say more the game could very well have the option of playing solo in certain parts. Like the Tower, it's a hell to go there to get the daily missions. It is simply one reconect after another.
Crucible is almost impossible to play too, it is a reconect after another when it is not a disconnect.
Lately playing destiny 2 comes down to one: reconnect simulator.
I never had an issue of Disconnects with GTA or any other game, no matter where in the world I happen to be at the time.
I very rarely have disconnect issues of Disconnects ith Destiny at any of my main locations.
But... I frequently get Disconnects - reported with error codes that say it is *my* internet or computer that is at fault - during reset windows, especially when a patch is being applied. And when I test the internet for both bandwidth and continuous ping during those time windows it always looks great. Coincidence? Very unlikely. Sorry, but every sign points at Bungie DEVs.
On the positive side... it is happening less now than it was about a month ago, so maybe they listened and started getting their act together.
It is mystifying that no matter the forum, there are those quick to defend Bungie's terrible choice to use a hybrid network, as if they are paid shills rather than an alternate opinion.
Contacting Destiny servers has been a problem since launch and the fact that they intentionally hid a ping indicator means they know it is a problem. Most people wouldn't even bother joining a server beyond a threshold ping, yet in this game, we are forced to connect to a lottery system which translates to random performance.
But wait you say, Bungie can't afford dedicated servers! Wrong, if a 5 dollar Indie game can afford dedicated servers at launch, so can Bungie with their vastly increased revenue stream of launch prices, expansion prices, season passes, Eververse junk and trinkets from their store.
But... the problem you describe is very common across the world and different ISPs. Any good development company knows it and adapts their code so that even something as long as a 1-5 second disconnect is recoverable. In those apps/games you might freeze for a moment, maybe get a "reconnecting" message (which by the way I recently started to see in Destiny, yay!) and then things continue. Much better than a full drop from a match. Also, once they fix the handling for your situation the same fix will likely fix the problems for those that get disconnected by distance/latency instead of ISP issues.
I know that Bungie can do better, and I even suspect that they started doing so.