{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
3/17/2020 5:16:47 PM
17
Beaver/Weasel/Beetle Errors Continue After Port Forwarding and 16/03/2020 Changes
Ever since the new season hit (and Bungie adjusted the game's networking to counteract DDoS attacks), I've been experiencing constant beaver/weasel/beetle errors, even multiple times in the span of 10min.
This persists after having followed Bungie's updated port forwarding guide, and after the changes reported on the [url=https://twitter.com/BungieHelp/status/1239662509444874240]BungieHelp twitter[/url]. I even went so far as to enlist network engineers I know to make sure that I hadn't missed something, and even that hasn't led to any satisfactory resolution.
The frequency of these errors is unlike anything I have ever experienced in Destiny 2 prior to the Season of the Worthy's release, and my internet connection remains entirely stable in all other capacities.
At this stage, I am very frequently booted from strikes and patrol spaces, and I don't want to risk playing Crucible, Gambit, or raids (and definitely not Trials) because of the negative impact a disconnecting teammate would have on those I play with and because I do not wish to incur the wrath of Bungie's automated disconnection punishments.
As it stands, Bungie's only response on the matter has been to direct those experiencing them to their updated port forwarding guide, and then the above linked twitter post.
Given the continuing problem, and the fact that it renders the game almost unplayable, I would greatly appreciate some actual feedback on this problem.
-
did you ever find a fix? I'm having this problem
-
Seriously. It's getting out of hand. Bungie needs to step up on this. The game is nearly unplayable at this point.
-
4 RepliesHello. I appreciate you reporting this issue to us. We're aware that it's occurring and we're investigating.
-
I am also experiencing the same thing and it really only started last week when Season of the Worthy dropped. I can't even get through a game in classic mix for bounties without getting booped out and then kicked. I have done all the port forwarding and everything and still nothing.
-
Edited by SquidGuy: 3/20/2020 12:34:53 AMSame here. Wired 500 mb connection. No issues before this season.
-
Same problem here in PVP and PVE. Can't join my friend since the season of worthy dropped due "NAT issues" where we have played 1000's of hours together before.
-
A clan mate used a it program to check my network settings while I played destiny tonight after not being a le to okay since Sunday night I uninstalled the whole shadowkeep I was able to play for a few hours tonight with a y trouble so I installed the shadowkeep again we shall see if this works it seems I got a currupted file I'll try and keep everyone posted
-
Same, I've lost easily 500 glory and have hours of suspended time from being booted from comp matches. this is the worst the game has ever been..
-
Same. I’ve done everything you have mentioned also. I can’t even join friends now because of a “network issue” yet my ports are forwarded and NAT is Open. If I could get a refund for the silver I spent on this season from steam, I would’ve already done so.
-
Same exact problem. I can't play any activities without being booted. A lot of times players cavalierly throw around the word "unplayable", but in this case the game is just that. Glad the money I spent on silver on top of the season pass last season has been put to good use...
-
-
I second this.
-
Edited by sp: 3/18/2020 2:00:22 PMGlad to see I'm not the only one. I was hoping @BNGSecurity would tell me what my errors and packet loss looks like to them? I played like 12 trials games and the lag came back. I'm tired of having to unplug my router, modem combo and wait 5 minutes only for the errors to come back. I've decided to just stop playing altogether but obviously I'm too addicted so I'll probably just be running strikes now.
-
Same the times that dosent kick me out Is when it puts me solo either un the tower or serafín publics eventes or ignition of forges
-
I'm also getting false error codes like 'Moderate NAT' issues even though my settings are on minimal for that. I just wish that they'd make a post or announcement saying that they're aware and working on these issues because staying silent is making players beyond frustrated when getting kicked mid raid encounter, or partially through a master nightfall or trial cards. If they'd just come out and say, oops we goofed but we're getting it fixed would calm down so many players myself included.
-
Same here, I keep getting Weasel whenever I launch the Lake of Shadows nightfall
-
Happening to me too, it took me twice as long as it should have to complete the fourth horseman quest step on mars because I kept giving me errors. Game is practically unplayable in this state...
