JavaScript is required to use Bungie.net

Forums

originally posted in: FIX MOOSE ERROR
7/22/2017 10:21:06 AM
5
Still didn't work I guess is something more than just the router. I think bungie doesn't care anymore been almost 4 days and still keep getting moose. Didn't even bother to give us some answer or help how to fix this. I think they don't know what's happening . Anyway I'm losing interest in this game and was a big mistake pre ordering it. My expectations to play the game where high now all I see is the same problems of d1 why they keep insisting on doing this p2p shit. We all know about d1 PvP and its will be the same old story again. Hope someone will come up with a fix and have time to complete first mission of this be but probably it won't happen. Well done bungie keep your streamers and YouTubers happy and forget all about the others like me who can't play.
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by vmondude: 7/22/2017 11:17:49 AM
    Well all the answers in bungies info request post showed Technicolor routers with a few net gear and tp-links scattered in there. So I'm pretty sure this is the problem. Make sure to set up the consoles network settings again from scratch with D2 closed, then turn off the console to refresh everything. If it still doesn't work then I really am sorry ☹️ But I can at least assure you that the game feels much better than destiny 1 for sure in pvp. Even pve is fun again and actually a challenge! Wtf lol. There's obviously going to be things that need adjusting, but its definitely good! Apparently the new connection system is a hybrid dedicated/p2p system so that's why it feels so much better. I was furious with my moose, but don't doubt that D2 is to be leaps and bounds improvement over old 😊

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Finally i found a way round this and managed to play the whole mission using vpn and Google dns and 1500mtu. I think it's more of the ip address. Maybe will help others. And I used again Technicolor router. The problem seemed solved atm for me

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by vmondude: 7/22/2017 11:38:47 AM
    Well fingers crossed. Although the ip will be the same on any router and it worked for me so I don't know. It will be because a vpn diverts you through a different location if op is the problem. I just thought it funny how everyone nearly posting their problem has a Technicolor router. But hey whatever as long as you got it working. I just hope it stays stable for you after homecoming mission.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I am still playing completed even the strike without any problems

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Good good

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon