This is truly upsetting. So many of us have been waiting for this baiting and these error codes are stoping us from even experiencing the game! Bungie needs to fix this asap! I agree with the general consensus of having an extended closed beta or something to fix this issue. I didn't preorder the game to not get my special perks that came with it. This is ridiculous.
-
#cancelpreprder speak with your wallet. It's the only thing activi$ion will understand
-
Hi all, I had this "moose" error on my ps4 that wasn't allow me to finish the opening mission. I tried like 20 times and always got booted when Ikora must appear. I did some research and I found something regarding the DMZ on my router. I added the "DMZ" on the firewall of my router and restart the ps4. Then I was able to finish the mission with no issues. Now I am going to start the Strike, hopefully this DMZ thing fix the issue. So my suggest is that you add your console to the DMZ on your router and see if that fix the moose error. Hola, Para los que tienen el error de "moose" que no deja terminar la misión de apertura. Yo agregué la consola a la "DMZ" dentro del cortafuegos(firewall) de mi router. Reinicié la ps4 y ya la puse pasar la misión. Así que intenten eso de agregar la consola en la DMZ de su router.
-
Hello, Could you either update your post or post in the following thread with the answers included in the thread in regards to the moose error code: https://www.bungie.net/en/Forum/Post/229243896/0/0
-
"While we are able to reduce the occurrence of some error codes impacting gameplay, other issues revealed during the Beta may not be addressed prior to the ending of Beta on July 23, 2017. To confirm additional known issues, please see help.bungie.net/beta. As we investigate and troubleshoot these issues, stay tuned to @BungieHelp for service status and updates." Translation: "We aren't fixing it."
-
-
Hello I had moose error and switched to a mobile hotspot got passed ikora and now strike and crucible have moose errors. Better of just not playing till its fixed