{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by BNGHelp5:
7/20/2017 9:43:28 PM
983
[BUNGIE] Destiny 2 Beta Investigation: Error Code MOOSE
Hello all,
Since Early Access to the Destiny 2 Beta began, we have been investigating player reports of MOOSE error codes impacting various activities.
To aid in this investigation, we are asking impacted players to provide additional information concerning their network circumstances. Please see the following:
[quote]
• Which [b]Console[/b] are you encountering these errors on?
• Which [b]Activities[/b] are you encountering these errors in?
• Are you currently using a [b]Wired or Wireless[/b] connection when attempting to play the Destiny 2 Beta?
• Are there [b]multiple consoles[/b] on your Local Network connected to the Destiny 2 Beta?
• Are you currently attempting to play from a [b]University[/b]?
• Could you provide any information about the [b]Router[/b] you use for your home network?
[/quote]
Stay tuned to [url=https://twitter.com/bungiehelp]@BungieHelp[/url] on Twitter for service status and updates.
English
#Help
-
Xbox One Joining fireteam, when leader was already in The Farm, haven't yet tried other same-LAN activities. Result was briefly joining a game (not sure if was same as fireteam host), that appeared unpopulated, except notifications like "so-and-so dances". Within a minute, would be kicked to orbit with MOOSE. This happened repeatedly. Also got RABBIT and VIPER once each, unclear whether these were related. Wired, IPv4-only Yes, prospective fireteam leader's console is on the same LAN Nope, residential cable internet PFsense, with UPnP, NAT hairpinning and static ports enabled. Same setup works fine/as-expected for Destiny 1.
-
Edited by NoxiousEfluvium: 7/23/2017 5:52:42 PMXbone, wired connection at home, only console active (powered up), NetGear...had 20+ OLIVE codes and logged out three times and changed characters as well. My Titan is the only one that could make it to the farm. Have landed multiple times and keep getting MOOSE within 15 seconds of arrival. My network connection is fine and I live within 60 miles of your studio, so I don't think it is an infrastructure issue. Also, I could see dialog of other player(s) actions, but no one was there.
-
Playstation 4 The homecoming mission, I can't get to the part with Ikora wireless One consol I'm not playing from an university
-
Edited by Mphiz: 7/23/2017 4:48:16 PMPlayStation 4 The homecoming mission, the cabal are not even there Wireless One console Not a university
-
Xbone Right when the doors to the sheiks generator should open. Has happened 4x now. Wireless One console Not a university
-
xbox one when icora suppoust to show up, fail the game in the beggining of the history wired one console no telmex 10mb
-
• Which Console are you encountering these errors on? PS4 • Which Activities are you encountering these errors in? Homecoming (every single time except one which allowed me to get into the beta proper), The Inverted Spire (so far every single time), very occasionally Control or Countdown. • Are you currently using a Wired or Wireless connection when attempting to play the Destiny 2 Beta? Wired. • Are there multiple consoles on your Local Network connected to the Destiny 2 Beta? No. • Are you currently attempting to play from a University? No. • Could you provide any information about the Router you use for your home network? UK Plusnet Broadband, Technicolor router, PS4 is in the DMZ with the Router.
-
Xbox One cant finish opening story Wireless just on No Technicolor TG788vn v2
-
I'm still experiencing moose when trying to play the either strike or crucible with my friends on the same network. Xbox one, wireless connection, home network, 2 consoles, netgear r6250 router. When I do reconnect, I'm left last guardian standing and no visibility of enemies or team members, or in crucible, control points or team mates or foes. Thanks
-
PS4 Pro Homecoming. Ikora will not spawn, kicked soon after. Wired No No Technicolor TG582n Pro
-
The detective conducting the investigation must be Sherlock Holmes...
-
Ps 4 Strike Wired Only happened when I was joining with others on my in home network, they are also wired Using a Netgear router
-
HI guys. Firstly, "Parabéns" for the amazing work in Destiny and for sure in the beautiful D2. So, I am experiencing this error too from the first day. First time after joining some friends to do the strike, when falling to fight the boss. Only me had the error and went back to orbit. I had it several times and was hard to rejoin my friends' team. I was playing with Warlock. Then, I started with Hunter and had the error when was supposed to meet Ikora, in the story mode. No way to proceed from that point. I was using a PS4 Pro in enhancing mode. I switched it back to normal and the error persisted with both guardians at the same point. Then, I tried to play it with a PS4 and started also to play with Titan. Same thing and at the same Ikora part. I am wireless connected through my home's Apple Airport router and at the time I was playing only cellphone and TV was also in the same network, besides the other PS4 which was in stand-by mode. Hope it can assist you guys and please, let D2 Beta live for a couple more of days, anything around 100 days....
-
*Playstation 4 *In the first "mission" that you enter, always on same place "Leave the plaza and find the seeker" part, spans no enemies and then i get thrown out. So haven't tried anything else... *wired *only mine but have a turned on computer and an shut off X1 on same network. *From home 100mb fiber *Thomson tg789vn Have tried with different classes, have turned on and off the PS4, tried on different times and days but still the same Moose problem :( Seems to be a really cool game tho :)
-
- PS4 - First story mission, when Ikora should appear. - Wired - No - No - Proximus b-box 3
-
I have this error since tuesday.... Only time i could finish the opening mission was when i used my iphone as a hotspot. • Which Console are you encountering these errors on? [b]Ps4[/b] • Which Activities are you encountering these errors in? [b]Homecoming mission, enemies do not spawn[/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[/b] • Could you provide any information about the Router you use for your home network? [b]Experia box V8 Astoria Networks VGV7819 (ISP KPN Netherlands)[/b]
-
This was the most epic beta in gaming history!
-
-Xbox One -First mission start. Wall explodes open, but no Cabal enter. Can run for a minute or so and then I get error code MOOSE. Haven't got around to play at all basically. -Wired -No -No -ZTE model MF286
-
Update please... if you say that we don't count, it's fine... at least we know and stop trying.
-
Why isn't this thread pinned anymore? WE NEED ANSWERS, WE DESERVE ANSWERS !
-
Edited by Shirogohan: 7/23/2017 12:24:35 PMI tried like 20 times in the last 2 days, but some minutes ago it just worked. I'll describe what I did, and I hope it helps, but I'm still not sure it was not pure luck: 1. I turned off the wireless in the router (Technicolor TG784n v3) the PS4 was wire connected,; 2. I turned off the controller vibration (it was not working consistently anyway); 3. I played slower. Intentionally took more time to kill all mobs, and also walked (giving the system more time to load the next group); A detail worth notice is that the last phase of the 3-step mission with Zavala was not triggered (because I've not been inside the shield, maybe? .. not sure). I gave it extra time, stood a couple of times inside the shield, still no mission status on the HUD .. but I progressed anyway. To my surprise, the door opened and Ikora appeared!! I followed the next phases slowly and was able to complete the Homecoming. I also played the Strike, and when we wiped at the drilling machine, was not able to regroup, but that's ok, the dammed Homecoming was finished and now I have access to the Director. Good Luck! ;)
-
1- Xbox one. 2- In the end mission strike end in multiplayer. Error code Moose. 3- Wired. 4- No 5- No 6- My router is Thecnicolor Adsl/adsl2+vdsl2 Modem Fibra Tim Connection 100/20 Mbps
-
1 Reply1) Xbox one 2) In the first mission ,when imita should appear.. 3) It's a wired connection 4) No 5) No 6) I use fastweb's routers ,it's a technicolor but i don't any other characteristics
-
1 - In ps4 2 - In strike, its impossible to play the end. Error code: MOOSE 3 - Wired 4 - No 5 - No 6 - My router is from thompson, with version TG784N. Is provided by my operator, by its name MEO.
-
Edited by Forcado: 7/23/2017 11:53:46 AMI have the same situation as JohnyBigodes. Tried several times to go through the first mission, only to fail miserably on my 20 or more attempts at it. I tried everything: restarting the console, reinstalling the beta, reinstalling my router, trying wired or Wi-Fi connection, everything. I was a completely hardcore fan of Destiny 1, but this beta experience is amongst one of the worse (if not, the worst) I've ever had. Please, make sure that this does not happen on September 6th, and it would be a nice touch if you could solve these issues and allow people to replay the beta when the problems are fixed. I would be completely upset if I paid for the pre-reserve to get beta early access, and failed to even complete the first activity of this beta. • PS4 • Homecoming mission • I've tried both wired and wireless - still the same problems. • Mine is the only console connected. • I'm playing from home. • Technicolor Tg784n v3
