JavaScript is required to use Bungie.net

Ajuda

Ajude-nos a ajudar você.
10/27/2020 3:55:10 PM
10

BABOON errors INTOLERABLE; 1500+ Glory Points Lost after Match wins!!

Dear Bungie and the Destiny 2 team, FACT: September 22nd, 2020 a mandatory Hotfix update 2.9.2.1 was installed into all Destiny 2 end-user systems. This is when the errors began on the end-user side. Here we sit, a month and five days later with absolutely no resolution. Not a word there's a fix in the works or an acknowledgment that anything is even wrong. The only response of any kind is very arrogant, blame the customer first response. It's your problem, not ours is not a very reassuring business philosophy. Never has been, never will be. FACT: Humans make things. Humans aren't perfect and so therefore the things they make are not perfect! I fully understand you're doing your best amidst the COVID-19 pandemic, but on two separate occasions in the last six months there have been exploits players in the game have spread the word about and within 24-hours it's investigated, examined, and corrected. Your actions from the customer side that when it comes to fixing the things that negatively affect players completing things or negatively impact the quality of life performance of the game it takes week, months, or is never resolved at all. YOUR ACTIONS AND PRIORITIES ARE HYPOCRITICAL AT BEST. At this point, BABOON errors have become intolerable. And don't you dare proceed to tell me it's my issue. The update came from you and that's when the problems began. I've worked in the residential and commercial networking and audio/video industry for over 25 years. When I call a call center for help or chat with a company's online tech support or post on a forum, it's always because I've completed as much technical repair or troubleshooting that an end-user can possibly do. What I do on my side to troubleshoot and correct the problem is at a minimum two to three levels above the entry-level tech support manager's knowledge. But it's my stuff, right? I don't think so, and that should never be your default response. So, yes! I have done everything that your "Network Troubleshooting Guide" states. All the things that you could possibly recommend that I do, I've done it every day for the last 37 days, and you know what, I'M FED UP WITH IT ALL. The quality of life for this game is at its lowest point ever! It's time you put your money where your mouth is and fix this issue. You're missing the point if you say it has something to do with our network ISP and there's nothing you can do about it. WRONG ANSWER! The problem started with the update you created, which was flawed, therefore you are the one responsible for the correction. Finally! I really wouldn't be furious with your company and your business practices if these BABOON errors continued as long as I don't continue to lose Glory points in Survival. I've been able to go as many as 10 matches without a BABOON error. But that was only once in the last 37 days, every other day I'll be removed from a comp match at least 5-10 times a day, resulting in warnings, suspensions, and the loss of over 1500 Glory points; 68 points lost per BABOON removal. This is the underlying problem that few have mentioned in their posts. COMP/SURVIVAL IS THE ONLY PLACE I GET REMOVED FROM THE FIRETEAM/MATCH!!! COMP/SURVIVAL IS THE ONLY PLACE I'M PENALIZED FOR AN ERROR THAT'S COMPLETELY 100% OUT OF MY CONTROL!!!!! I am beyond the point of moderate frustration and while you may never actually read the entirety of this forum post, I hope you will hear the absolute anger and disgust in the videos I made to show you how your incompetence in correcting your error is negatively impacting the world around you! Oh yeah, in the course of writing this post, I have received a BABOON error code 7 times over 20 matches. My port forwarded, hard-wired connection with 500 Mbps down/20 Mbps up, with -2% latency, 0.02% packet loss, constantly restarted the modem, constantly power cycled to clear the cache of the 6-month-old PS4 Pro, and where all the equipment on my home system hasn't changed or magically degraded in the last 9 months. IS NOT THE PROBLEM. Please take this ongoing deficiency of your errors to the highest level of attention it can receive and resolve this immediately? VIDEO 1: 10/26/2020 @ 2156 hrs - 1:11 run time - Suspension after Completed Survival Victory - 1st match in 24 hrs. [url]https://www.youtube.com/watch?v=MfunAhXzg6M[/url] VIDEO 2: 10/25/2020 @ 0352 hrs - 0:53 run time - Suspension Warning for leaving but never left. [url]https://www.youtube.com/watch?v=DLl6cxoIp_A[/url] VIDEO 3: 10/21/2020 @ 0150 hrs - 0:57 run time - Suspension Warning for leaving but never left. [url]https://www.youtube.com/watch?v=vY09trb23ts[/url] VIDEO 4: 10/18/2020 @ 0501 hrs - 1:46 run time - Suspension Warning for leaving but never left. [url]https://www.youtube.com/watch?v=uGAeNCCbILg[/url] VIDEO 5: 10/17/2020 @ 0503 hrs - 1:56 run time - Suspension from Survival for leaving but never left. [url]https://www.youtube.com/watch?v=rvXi8HT_o24[/url] VIDEO 7: 10/12/2020 @ 0059 hrs - 0:40 run time - Elimination match without Baboon [url]https://www.youtube.com/watch?v=rvXi8HT_o24[/url] VIDEO 8: 10/11/2020 @ 2140 hrs - 1:50 run time - Gambit Prime Victory but ejected from the team. [url]https://www.youtube.com/watch?v=ZNbKMr9Wklc[/url] VIDEO 9: 10/09/2020 @ 0620 hrs - 0:42 run time - Gambit Prime completed loss but "Baboon" after the end of the match. [url]https://www.youtube.com/watch?v=R62il6iNeHM[/url] VIDEO 10: 10/09/2020 @ 0103 hrs - 1:58 run time - Suspension Warning for leaving but never left. [url]https://www.youtube.com/watch?v=9wKf0CYrcNo[/url] VIDEO 11: 10/08/2020 @ 2257 hrs - 0:52 run time - Suspension Warning for leaving but never left. [url]https://www.youtube.com/watch?v=j9B6O9exl9g[/url] VIDEO 12: 10/07/2020 @ 2304 hrs - 1:02 run time - Gambit Prime Victory but Baboon after completion. [url]https://www.youtube.com/watch?v=VNDAZYsDJoI[/url] VIDEO 13: 10/04/2020 @ 1710 hrs - 1:38 run time - Suspension warning & loss of Glory points after Survival Victory. [url]https://www.youtube.com/watch?v=espTlWJsuYU[/url]
English
#Help #Errorcodes

Postando no idioma:

 

Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

  • Novo tópico iniciado: Error code Baboon(3 Respostas))

  • I’ve never had anyone fully represent how I feel in 1 post. You’re spot on and I’m right here with you. I hope this post gets huge so they are forced to see it, since they haven’t replied to any of us on anything and have just had community members do it for them.

    Postando no idioma:

     

    Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

  • 100% this! I am so f’n pissed off right now. I should have never pre-ordered. I would be done with Destiny at this point. I have spent the last 4 weeks working survival matches dealing with BS Baboon errors that started with the last update. 1-3 matches and boom. I am dumped. The. To add to it, I lose glory. I was 14 wins, 7 losses over 3 days, but 10 baboon errors so all that f’n time wasted to gain 0 ground.

    Postando no idioma:

     

    Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

    1 Responder
    • Yep this was the date that all of us started to experience these issues. People that keep telling us to reset routers/clear caches don’t get that we did nothing, then Bungie implemented a hot fix, then we had issues. So who is responsible again? /s

      Postando no idioma:

       

      Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

    • Thank you for this post as I have been experiencing this multiple times per play session as well. It almost always plays out with the initial Baboon error. After which, I am brought briefly back into the match only to then be kicked to orbit accompanied by the Bat error. I have also received the 30 minute suspensions as a result and it is extremely unaceptable and inexcusable!!! Nothing with my network setup has chanced in the slightest and I have exhausted all of the troubleshooting methods in their guide and continue to do so, (much like looking in the refrigerator multiple times in hopes that there will be something new to eat/drink in there...) I have absolutely NO disconnects or errors in ANY other multiplayer games. This is exclusive to Destiny 2. Keep in mind I used to get the occasional baboon or other error but when I say occasional, I mean maybe once a week as opposed to now where it's multiple per session! If this just keeps getting pushed to side as if "It must be the users fault. Please check this and this, oh and do this..." Then I just don't know how much more I can support and spend my money on this game with its poor p2p server system Bungie has always touted as "superior to dedicated servers"... I have called my isp (Xfinity) and spent about 2 hours on the phone with them as well as a tech that came out and went as far as testing all of the wiring to and in our house and they can't find a thing... Especially since nothing has changed on our end or with our internet plan/equipment... I really hope Bungie is actually looking into this on their end as well as working with the ISPs to trace what happened because this is equally as bad as the recent Baboon error that plagued PC players (to which, they found a fix.... ON THEIR END)...

      Postando no idioma:

       

      Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

      3 Respostas
      • It is so maddening. Can't get more than a game in. I really feel for you. I opened the game to a time out and then played one game got kicked and another time out. Ive been taking clips too but i really doubt it will do anything for me.. I just want to play comp lol

        Postando no idioma:

         

        Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

      • Add my name to the list of effected players. I came back to Destiny towards the end of September, and have been absolutely plagued by Baboon errors. My experience in Survival is exactly what you've described. I've followed every single guide that Bungie provides (and others) - I'm hardwired, setup Port Forwarding, verified my game files with Steam, re-installed the game, etc. Now when the error occurs I close and re-open the game, but that only seems to resolve the issue briefly. Since I incur a Survival ban every time it happens, by the time my ban is lifted the gremlins have had enough time to re-establish themselves. I'm lucky to play 2-3 Survival matches in a row before getting the Baboon / Bat wombo-combo. Just now I played 4 matches of Clash without issue, and decided to try my luck in Survival. During my first match I got a Baboon at the transition to the final round, tied at 3-3. Incredibly frustrating, to say the least. I also experience a constant stream of Baboon errors in the Tower, Patrols, Raids, and Trials. It's a systemic issue with some periods being worse than others, but no real pattern that I can identify.

        Postando no idioma:

         

        Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

      • totally get where your coming from... altho im not a pvp player whose losing glory i feel for you ...im a pve player dealing with the same issues -soloing the pit and get a section almost done and get baboon errors n get sent bk to the begining of the section with nothing by knetic ammo .... helping people in nf and other activities and have them happen regularly is just ridiculous... ive done all the trouble shooting bs.... chkd all my network speeds n so forth ...my consoles hard wired on better than avg connection and like others never had an issue in 6 yrs till this ....

        Postando no idioma:

         

        Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

      • Who’s your ISP?

        Postando no idioma:

         

        Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

        3 Respostas
        • [u][b]Hey there![/b][/u] This error code is a known issue affecting Destiny servers and multiple internet service providers. Please be patient while this issue is investigated. [quote]Receiving the same error codes multiple times indicates that you are likely encountering a single root issue. The cause of the disconnects could be something such as corrupted data in the Destiny installation or a source of instability in your network setup. If you are receiving multiple disconnections from Destiny with the same error codes, you may want to try the following troubleshooting steps: -Closing and restarting the Destiny application on their platform -Restarting and clearing the cache of their platform -Switching to a wired connection if the player is currently using a WiFi connection -Searching the Destiny Help Knowledge Base for the associated error page and working through any additional troubleshooting suggested on the page -Reading through the other pages of the Network Troubleshooting Guide -Searching or posting in the #Help forums where Destiny Player Support, Mentors, and community volunteers may be able to provide additional assistance[/quote]

          Postando no idioma:

           

          Comporte-se. Revise o nosso código de conduta antes de enviar a sua postagem. Cancelar Editar Criar esquadrão Publicar

          5 Respostas
          Você não tem autorização para ver esse conteúdo.
          ;
          preload icon
          preload icon
          preload icon