It should be able to be solved, but would be up to Bungie to address it since many use a configuration like this that can't be managed by the end user. Those players can contact their ISPs to open the needed ports, so it can be done by the player himself, but likely he or she would need the knowledge to explain the issue correctly, and also speak with an ISP rep that understands his or her issue.
English
-
작성자: jnikoley 7/21/2017 5:01:35 PMThe destiny two beta uses a slightly different connection between players then destiny one. In D1, it was mostly connection by P2P. In D2, although P2P is still in place, there is a stronger reliance on the use of cloud servers to manage aspects of the game that were previously handled by a player host. I'm sure Bungie is working to figure out a solution. Time will tell if the end result is an improvement over the connection we had in D1.
-
Curious you say that it's isp related when every other online game works other than destiny 2. This is obviously some problem on their end even if the majority of users complaining about this moose error use the same or very similar routers. Even more so when you consider alot of those played destiny 1 with no issues at all. Sure it can be another type of connection but that still doesn't excuse it when every other game works, including their previous game. Also, the decision to make players go through the story mission to be able to play everything else was genious...
-
I'm not blaming players or their ISP, but offering an explanation why some players are having issues while others are not. This does not excuse Bungie who should be able to make a game that works like any other. Considering it took Bungie over 6 months to figure out the same local network issue in D1, they could use all the help they can get in narrowing down the cause of the current issues. Information that players give can help.