Thank you for your great feedback about this error.... we know nothing ( like Jon Snow ) and the beta is ended....

Xbox one, strike, dual-band wifi, playing with roommate sharing internet. He's hardwired and never got moosed.

Xbox one Mainly ikora Wirelesssingle console At home

Update, Moose code, same problem since the begining off the beta: ikora doesnt spawn Playing on PS4 ( belgium) The first mission : Ikora doesnt spawn and ennemis and all the doors up too the burning three are open. Lately even zavala has trouble spawning and the wave of cabal don't start. Wireless 1 console connected. ( and the Tv + 2 laptop. Not in university No info on my router. Good luck bungie. Hope you can fix it quick like this a can try something else than the first mission over and over again... ;)

Any news ? Is this expected at release? Is there a possibility of feed back? Would be nice 2bh given that I've already put money in your pockets.

i have changed my modem from technicolor to vv2220VDSL and everything works now fine, but this cannot be the solution!

I'm thinking not buying the game, till i have 100% absolutely sure, that they manage this problem with the connections.... i play alot of games online, and not a single problem with them.... they have to ensure, that no one with NAT 2 or better, have any problems with the game. So I advise everyone not to pre-order the game till they assure the problems are solved in the final product. Destiny is 100% online game.... It is absolutely [u]mandatory[/u] that the game is working properly for everyone, [u]with any type of router[/u]

[quote][b]Which Console are you encountering these errors on?[/b] PlayStation 4 Pro [b]Which Activities are you encountering these errors in?[/b] In the Homecoming mission. When entering Tower North, Ikora and the Cabal won't spawn, and all the doors are open. The cutscene leading to the next section of the mission and the dialogue in Tower North don't trigger as well. About 2 or 3 minutes later, I get prompted with the moose error code and kicked back to character selection screen. Sometimes when retrying the mission, no enemies spawn, no scripted events trigger and all the doors are completely open as well. Getting prompted with the moose error code may take a bit more time when this happens, I'm not sure, but I can test it. However, I managed to finish the mission by using my smartphone as a hotspot. I tested the home network for the other activities and found that the same error code is also present. In the strike mission, as soon as I enter the Inverted Spire section, the platform on which you can find the Modular Mind won't load, leading my character to falling in the pit and dying. When respawning, a "Joining allies" message shows up with a countdown. Starts with five seconds, fails; then repeats with just one second about three times before the moose error code prompt appears and I get booted to orbit. In both Crucible maps and modes, most of the time no other players are present on the map and I get a "Last Guardian Standing" warning. This usually happens on the beginning of the match, although I've found that it may happen on the remaining rounds. Playing Control, I get the moose error code and booted back to orbit about a minute after the start of the match. Playing Countdown, I usually get the moose error code in the first two rounds, although I have been able to finish a match. [b]Are you currently using a Wired or Wireless connection when attempting to play the Destiny 2 Beta?[/b] Wired. [b]Are there multiple consoles on your Local Network connected to the Destiny 2 Beta?[/b] No. [b]Are you currently attempting to play from a University?[/b] No. Home network. [b]Could you provide any information about the Router you use for your home network?[/b] Technicolor TG784n v3. The console is connected using a Cat 5e cable to the gigabit ethernet port of the router. Maximum speeds capped at 200mbps for download and 100mbps for upload by the provider. NAT type 2 (I have tried to change it to test the Beta with a NAT type 1 connection, but it is not working for some reason). Location is Portugal.[/quote] [b]UPDATE:[/b] PlayStation 4 (update 1.04) and Xbox One Beta tested. All of the issues quoted from my last post still apply. I would like to add that I have managed to get past the Ikora section twice on PS4 on the earlier version. However, no Cabal spawn in their ship and I am asked to interact with some sort of computer in the first area of this part of the mission where they should spawn. No interaction is possible, the barries that should prevent you to move further into the ship are all down and I end up receiving the moose error code message here too. Zavala hasn't spawned immediately a couple times, but I keep getting reconnected and he spawns eventually. This has never triggered moose. As previously reported, I have made attempts to change NAT type in order to test different network settings. Unfortunately, any changes made to the router end up being overriden by the ISP. Any effective changes to the network can only be performed by tech support unless you have a different router, which sadly I do not. I wasn't even given access to my PPPOE credentials. By the way, I don't know if this is relevant, but my ISP is MEO. Good luck, Bungie.

Hi again, even after patch 1.04, the issue is still present. PS4 pro homecoming mission, after 3 waves with zavala, ikora in north tower doesn't spawn. The music changes, and after 30\40 sec, moose error. If i try to jump back in the mission after the error, no mob in the mission. i'm using wired connection, even if i tried also wireless. No multiple consoles, no multiple account i'm playing from home router is technicolor. Sad thing is that i played more than 2,8k hours in destiny 1, without any issue at all. I already cancelled my preorder on psn, try to fix it for d1 and i'll evaluate to buy the game. Really pissed off by this situation....

try to disable SIP ALG on your routers, this was the solution of a friend of mine. router was technicolor