Me and a group of friend have this error code and we cannot complete the starting mission because of it. Basically something or someone does not spawn and after that the game crashes giving this error code. For example,the starting enemies does not spawn, sometime Ikora does not spawn and sometime Zavala does not spawn and when we reach the certain point in the mission game crashes. Someone is experiencing the same error and is there a way to fix it?
-
Hello, We are actively investigating this issue. Stay tuned to [url=https://twitter.com/BungieHelp]@BungieHelp[/url] on status and updates to this investigation, when available.
-
Help Moose error since i bought the game RIP bungie
-
Edited by Hedera: 8/25/2017 3:01:04 PMEdit: Nvm. It seems the thread didn't get bumped so no point in asking anything here i guess.
-
I have the same problem please help me I ♡ Destiny 2 and I can't play
-
[quote]Me and a group of friend have this error code and we cannot complete the starting mission because of it. Basically something or someone does not spawn and after that the game crashes giving this error code. For example,the starting enemies does not spawn, sometime Ikora does not spawn and sometime Zavala does not spawn and when we reach the certain point in the mission game crashes. Someone is experiencing the same error and is there a way to fix it?[/quote] Same :/
-
I have the same probleme =\
-
Fixed mine so made this quick today https://youtu.be/8HdZzXK2B5k
-
Ohhh porco diooo lo risolvere o no sto problema moose che è 3 cazzo di giorni che ho la beta e arrivo solo a metà missione !!!!!
-
Italy here, again. Xbone One, Telecom fiber connection, open NAT type, powerline cable. When you have to meet Ikora enemies don't spawn and then moose error. After the error, if you launch again the mission also the first cabals won't spawn so to restart the mission again you have to close destiny 2 and relaunch it. I don't want to spend all my mobile GB just to finish this mission because, reading the forum, when you switch again to your home network you will have again the error for whatever you're doing. Let's wait for a (quick) fix, hopefully they'll extend the beta for those who can't play the beta because of this error. PS: Played Destiny 1 and no problem. Hope they fix soon
-
Arreglen este problema bungie por favor !
-
Never had seen so much incompetence to solve a problem. First the pre-order was did for nothing cause exclusive time for playing was done... now the open beta time for playing will be lost. Are you guys learning with Ubisoft how to make poor servers or learning with No Man Sky's how to promise a thing to costumers and don't keep your word? A dog can make a better work... give my money back! If you guys can't even fix a beta, I don't want to pass through this shit on full game! RIP DESTINY! PS: A patch was release earlier today... and don't solve the problem! HAHAHAHA! -blam!-in joke developers team!
-
"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."
-
I open a Thread for yours opinion [url]https://www.bungie.net/it/Forums/Post/229266454?sort=0&page=0[/url]
-
I had to switch to my mobile hotspot to finish the opening mission. Then I change back to my LAN line connect via powerline networking direct to my router. This time it happen in Strike and Crucible. In Strike I got this code before the final bos spawn. In Crucible I have like 2 matches but my third match I'be been kicked out to orbit and my fireteam have to do 3 vs 4. Please solve this issue. I would appreciate if you guys manage to solve before the beta close down. Love Bungie and Destiny 2.
-
Edited by CachorroBranco1: 7/21/2017 12:56:19 AMI know we're in the Beta and that the Beta is to fix the problems and that the Betas always have errors, but it's very frustrating, not to say disheartening. I expected the Beta for months, I made the pre-purchase on the day it was opened for sale, looking forward to playing and unfortunately I can not. Yesterday Beta Launch Day on Xbox, I only managed to make Tita almost 1100 pm, could not play due to the error Moose, I'm already on the second day of Beta and I can not do anything in the game, I can not do any other character, Only the Titan. I'm very disappointed with all this, it's one thing to have some errors, another is the mistake not allowing you to play Beta. I'm in Rio de Janeiro City Brazil :o( Cachorrobranco1
-
Edited by RedPhoenix HD: 7/20/2017 8:43:50 PM[b]To those reading this thread regarding MOOSE... [/b] Bungie now has a separate tracking thread for you to post details in. This information will hopefully lead them to the related cause of the issue. Please supply the information requested ([i]and more if you have tried some debugging of your own[/i]) in an informative manner. https://www.bungie.net/en/Forums/Post/229243896
-
https://www.bungie.net/en/Forum/Post/229243896/0/0
-
Same. Italy again. Seems it's plaguing mostly Europe or it's just my imagination?
-
THE SOLUTION: Share your account with a good friend and let him play the first story mission! I helped my homie with this ;) hope it works for every moose code.. Good light good fight
-
On ps4 set nat 1 or 3 and it will works
-
More than 48 hours investigating and no news/no solution... GOOD ONE SHERLOCK HOLMES! CANCER COMPANY! This guys are a Ubisoft team 2017 version!
-
yap, the same god darn thing after the 3 wave part, over and over and over again, 8H of trying the same thing again and again, enough, i give up, i understand its a beta, but seriously i dread how its going to be on release. insert McKayla is Not Impressed meme here