JavaScript is required to use Bungie.net

Help

Help us help you.
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

Posting in language:

 

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

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

    Posting in language:

     

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

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

      Posting in language:

       

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

      3 Replies
      • Xbox one Mainly ikora Wirelesssingle console At home

        Posting in language:

         

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

        1 Reply
        • 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... ;)

          Posting in language:

           

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

          1 Reply
          • If this is not fixed or release, I'm done with Bungie.

            Posting in language:

             

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

          • Echo echo echo

            Posting in language:

             

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

          • 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.

            Posting in language:

             

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

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

              Posting in language:

               

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

              1 Reply
              • Thank you Bungie for the great feedback!!

                Posting in language:

                 

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

              • Which Console are you encountering these errors on? PS4 (not pro) • Which Activities are you encountering these errors in? Homecoming mission, right after the plaza event. • Are you currently using a Wired or Wireless connection when attempting to play the Destiny 2 Beta? Tried both, both went in error • Are there multiple consoles on your Local Network connected to the Destiny 2 Beta? One console, if the digital tv decoder is not considered a console. • Are you currently attempting to play from a University? Nope, from home network • Could you provide any information about the Router you use for your home network? Technicolor .... This feels very similar to the NAT issues we had in destiny 1 where destiny misreads the NAT settings. In destiny 1, the game would read NAT 2 settings as NAT 3 and when engaging with other players destiny would prompt a network error. I really hoped this child disease would have been fixed by now especially by a AAA game developer. I understand that this is probably due to my router settings but it is really up to you guys to find a work around for this as destiny is the only game where this happens... I will not buy the game if this is not fixed (and probably no one in belgium should either)

                Posting in language:

                 

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

              • Edited by monoliet: 7/26/2017 9:10:33 AM
                why games like call off duty - dying licht + many others see i have nat 2 ? you game tinks i have nat 3 ! i was richt to delete beta , restart dying licht ( them are great devloppers + lots of free stuf ) lol lots of Belgium peopel ( me to ) moose moose moose you won worst beta ever price !

                Posting in language:

                 

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

              • Edited by Ankiboy: 7/25/2017 2:37:55 PM
                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]

                Posting in language:

                 

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

                2 Replies
                • just finished playing, managed to get passed the first mission and finish the strike via hotspot (mobile internet from TELENET/BASE in Belgium) --> this is not a real solution BUNGIE! it's not ok that you eliminate an entire player base because of our ISP. It looks like the entire Proximus network in Belgium is affected. If we don't get proof the networking improves and that the game is playeable we will cancel our preorders.

                  Posting in language:

                   

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

                • Spoiler below if anyone havn´t played the mission yet. [spoiler]I made a comment on all my specs and so, tried it yesterday again and it always crashes at the same time. When I start looking for the speaker, the minimap dies and I can run around for a bit and then Moose error comes up. Been the same place 3 times now. Other than that, the mission looks Fu******* brilliant!! Can´t wait to play the game guys! Hypetrain!! [/spoiler]

                  Posting in language:

                   

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

                • Changing the modem for a game is not an option when you pay $100 dollars, Bungie has the responsibility to solve it. That product is the name of the company, That product is the company.

                  Posting in language:

                   

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

                • ps4 Pvp/pve. After 2 match pvp error appears Wireless No 1 console At home technicolor tg789vac v2

                  Posting in language:

                   

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

                • Edited by Bartowski: 7/24/2017 9:04:47 PM
                  [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.

                  Posting in language:

                   

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

                  1 Reply
                  • Xbox one. Wireless. The moose error is at the start, I will appear at the start of the game, and the part at the beginning where the Cabal are supposed to break the wall down, they just don't appear, and once that happens I know I'm about to get booted. I do not have multiple consoles running Destiny. I am not playing from a university. I have a PPPoE connected to a Netgear router.

                    Posting in language:

                     

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

                  • Xbox One & PS4 Homecoming mission, Ikora doesn't spawn, times out with 'moose'' error msgs. Have not finished this mission once, therefore can't access any other parts of the beta, PvE or PvP. Wired. No. No. Home TP-LINK 300M Roteador Wireless N Modelo No. TL-WR841N / TL-WR841ND

                    Posting in language:

                     

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

                  • 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....

                    Posting in language:

                     

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

                    3 Replies
                    • i.....again!! even after patch 1.04, the issue is still present on the PS4

                      Posting in language:

                       

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

                    • still get the moose error at the control panel on the cabal ship

                      Posting in language:

                       

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

                    • Hi.....again!! even after patch 1.04, the issue is still present. PS4 homecoming mission, after 3 waves with zavala, ikora in north tower doesn't spawn. The music changes, and after 30\40 sec, moose error. I'm using wired connection. No multiple consoles, no multiple account, no in university. i'm playing from home, router is technicolor TG1100, Internet provider is Fastweb, I'm located in Italy, in a big metropolitan city in Italy, I never had problems with Destiny 1. My connection is with fiber optic, one of the best in my country. I'll wait a few more weeks if you fix the problem okay, but otherwise, if you do not announce that you''ve solved the problem, I will drop the pre-order and ask my money back. bye bye

                      Posting in language:

                       

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

                    • Seeing a common trend................... 1-non-US internet 2-technicolor router

                      Posting in language:

                       

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

                    • fixed my moose problem . i returned my technicolor to my isp and they changed it to a zte . problem solved , did the strike already 3 times .

                      Posting in language:

                       

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

                    • Edited by Konkoeni: 7/25/2017 10:15:57 AM
                      try to disable SIP ALG on your routers, this was the solution of a friend of mine. router was technicolor

                      Posting in language:

                       

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

                      5 Replies
                      1 2 3 4 5 6 7
                      You are not allowed to view this content.
                      ;
                      preload icon
                      preload icon
                      preload icon