{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Modificato da REKT:
10/29/2020 8:43:21 PM
16
The XFINITY Zoo of Error Codes
I'm sure you can see the slew of other posts with relatively the same issue.
- This all started about a month ago, sometime during the week of the 25th of September.
- XFINITY ISP *edit few others in comments (Shaw and Rogers, Rogers uses XFINITY, Spectrum)*
- Receiving error codes: Baboon, Anteater followed by a bat moments after rejoining (probably related)
- I have contacted XFINITY over 10 times about this issue, even had someone come out and check all of my stuff and they said it was fine.
- I have no issues in any other game at all, just Destiny (of course the game I want to play)
- I cannot run Trials of Osiris due to this it completely destroys trials cards
- I have no doubt in my mind this is going to ruin the Beyond Light experience for other XFINITY users not just myself, so this really, really needs to be addressed before hand.
- I'm East Coast (PA) if this helps at all *edit turns out it's happening everywhere*
-Everyone having the same issues upvote so we can get their attention
- I've tried everything possible to fix the issue so don't comment with a fix, this is clearly out of our hands at this point
*UPDATE* - In The 10/29/2020 TWAB they said they acknowledged users having these issues, hopefully there is a fix soonish
-
Reporting in from Massachusetts, Xfinity customer, and I have been getting Anteater codes CONSTANTLY during Beyond Light. Using an Ethernet cable and have very fast stable internet otherwise. Such a bummer. :(
-
Good to know I'm not the only person facing this issue. It's a CONSTANT issue for me. Every session I expect at least 2-3 baboons, and Destiny is the only game I'm having issues with. Really hoping Bungie gets this ironed out ASAP after Beyond Light hits, as this is gonna totally throw off people's day 1 raid runs.
-
1 RispondiTHEY ACKNOWLEDGED US IN THE TWAB!!!
-
We have plenty of people here who have literally done EVERYTHING they possible could, I upgraded internet speeds, got a new ethernet cable, got a new modem and still having this issue just like many others in this thread. Even if this is "on our ISP" it is literally up to Bungie to resolve this issue because for most of us there is 0 that we haven't tried or done :( If this isn't fixed I really don't think most of us will enjoy the expansion at all...
-
Spectrum user here (on Xbox one) ever since the 2-3 weeks before FOTL the connections / hit registration went up drastically, error codes in comp were far more frequent, and got me comp banned a couple times. Super aggravating, one thing that helped a decent amount was turning off Upnp on my router, other then that it’s still on the verge of super aggravating.
-
Shaw 300 in Alberta Canada. Started ever since FOTL began. Constant baboon. 2-3 times and hour. Have done everything in my power to fix it.. Even a trace route is coming back clear. No bad hops. At this point I'm missing out in finishing conqueror and shadow titles because I keep getting kicked. Very upsetting indeed. First time coming across an issue this big in Destiny since the early D1 days... I hope it cleans up before beyond light..
-
Reposting from Reddit: Ever since the FotL began, I've been seeing recurring Baboon error while in fireteam-based activities. Originally, I thought it might be my new gateway, but after a couple diagnostics we haven't found any sign of a problem with the hardware or signal. For the most part, it seems to happen in the Haunted Forest and The Menagerie, and it usually causes a brief blackout and respawn to whatever starting position there is for the current instance. Has anyone else been seeing these errors frequently since the last content update? Edit: Just replaced my gateway - no improvement. Really starting to believe it's something.on Bungie's end.
-
1 RispondiI upvoted as well. Same nonsense has been happening to me as well. It happens during long content (raids, dungeons) but I've had it happen in strikes as well. It especially affects my crucible experience. I can't go more than 2 games without getting babooned. Comp and Trials are accompanied by bat errors following the brief reconnect. I'm in Eastern PA and in my area, I have no other options for internet other than Xfinity. Here's hoping the visibility helps!
-
3 RisposteSame about a mouth or so keep getting kicked can't even play the game. I pre ordered to this is really upsetting and I haven't had this problem before fix it please bungie only game I play and can't even play it
-
I’m on Xfinity in Oregon, I’ve been having the exact same problem as you’ve described. My connection and everything else is perfectly fine.
-
10 RisposteIt’s not just Xfinity users, I’ve got Rogers and the same thing started like a month or so ago now. Frustrating.
-
Holy crap, I thought I was the only one....I've been dealing with EXACTLY this and no one on any side wants to help. Xfinity said my stuff was fine, Xbox Support says they don't handle connectivity issues, and Bungie hasn't responded. What the hell.
-
Also have had this issue for months figured it was just on my end
-
9 RisposteI also had the same issue. I am on their most expensive plan that is available for me. My download speeds were decent. It was my upload bandwidth that was causing all of my issues. I took my modem to an Xfinity store and got a new one. This was also after a tech came out and checked everything out. I was also not having any other issues as everything else we do is download dependent only. I haven't gotten an error since.
-
I’ve had the same exact issue. I canceled my preorder of Beyond Light due to this. No point in getting the new content if I can’t even play the current stuff right?
-
Modificato da EmpressLeyo: 10/26/2020 1:15:56 AMThe same thing is happening to me and its absolutely frustrating. They need to figure this out ASAP. I get error coded at least 10 times in a pretty decent gaming session. This is beyond ridiculous.
