{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Kell of Kellogs:
7/27/2016 7:46:46 AM
10
RELEASE PATCH 2.3.1 THE NEW DLC- "THE RETURN OF BEAVER AND FRIENDS"
I know by browsing the forum recently that I'm not the only one getting error codes and other things that were not an issue before the new 2.3.1 patch.
Just today after downloading the patch at promptly 10am PST and then closing my system down to go to work, I turn on my system and start Destiny around 7:30pm PST and now I can't join friends in fireteams I have played with before the new patch release. I get kicked to orbit or even out of the game completely while just waiting in a nearly empty Tower. I restart my system only to achieve the same results. I then did a system rebuild. Same results. Checked and double checked PS4 network which said both times up and running. I Can't join friends in a fireteam, get kicked to orbit randomly and get animal error codes (beaver 5 times, rabbit once, etc.), where before the patch I had none of these issues. So HELLO BUNGIE YOU BROKE WHAT WASN'T BROKEN.
Really Bungie, YOU ARE SUCH THE ANTAGONIST. Why don't your dev teams check their work before releasing a patch? So, by the quality of work in Bungie I assume that you have interns doing the devs work and the devs aren't doing their job in quality control. BUT AS USUAL, BUNGIE CARES NOT. Getting pretty used to that broken record. Nothing changes, just Bungie marching on to the next DLC or Destiny 2 and not caring about us players. Quality control Bungie, means turning out a product that works at 98% efficiency when we the players are cautioned that we are beta testing. Then at that point you the devs are supposed to be fine tuning to make it 100% efficient. Yet instead of doing that, you are starting at 98% and dropping to 95% or worse now.
I could go on and on but really, I'd just like to see a fix so I can play how I already had it before the patch was released. I want to be able to join friends again and not get kicked to orbit or get an error animal code. You fix this and I'll be somewhat happy. There are many other issues, but I would at least like to be able to play the game. Btw, it's not my internet. I checked that and got successful connection with PS4 network at over 60 mbps download and over 4 mbps upload.
-
3 RepliesHello all, We have identified an issue causing players to receive BEAVER error codes at an increased rate. This issue was introduced in Destiny Update 2.3.1, and is due to complications regarding NAT settings. For more information and a potential workaround, please see our thread here: https://www.bungie.net/en/Forums/Post/209806134 We are continuing to investigate the issue and apologize for the inconvenience.
-
1 ReplyOh so it wasnt just me.....feck
-
1 Reply#bestpatch
-
Beaver, Quail, Rabbit. Sigh.
-
Edited by sjshady0169: 7/28/2016 1:51:21 AMSo wait, Bungie released an update (2.3.0) to tweak hunters and make other changes to the sandbox, and in turn created a new bug involving solar burn DOT not calculating correctly. Then, approximately a month later they found the culprit and released a patch to fix this bug (again, that they created). Turns out, the patch to fix the bug is now causing connection problems for guardians in various game modes. Sooo, then are they going to release another patch to fix this problem...and potentially create a new problem. When does it ever end? Should we expect the same the next time there's a sandbox change? My money is on likely yes as we can clearly see that there's no testing done beforehand and thus the "beta" that is Destiny continues on. My only hope is that Bungie learns some hard lessons from this, because I don't think players will put up with the same bs in Destiny 2. Why should they, when there are so many better options out there. #pissed off guardian #satirenotsatire
-
Same can't go to tower why why
-
1 Reply[quote]I know by browsing the forum recently that I'm not the only one getting error codes and other things that were not an issue before the new 2.3.1 patch. Just today after downloading the patch at promptly 10am PST and then closing my system down to go to work, I turn on my system and start Destiny around 7:30pm PST and now I can't join friends in fireteams I have played with before the new patch release. I get kicked to orbit or even out of the game completely while just waiting in a nearly empty Tower. I restart my system only to achieve the same results. I then did a system rebuild. Same results. Checked and double checked PS4 network which said both times up and running. I Can't join friends in a fireteam, get kicked to orbit randomly and get animal error codes (beaver 5 times, rabbit once, etc.), where before the patch I had none of these issues. So HELLO BUNGIE YOU BROKE WHAT WASN'T BROKEN. Really Bungie, YOU ARE SUCH THE ANTAGONIST. Why don't your dev teams check their work before releasing a patch? So, by the quality of work in Bungie I assume that you have interns doing the devs work and the devs aren't doing their job in quality control. BUT AS USUAL, BUNGIE CARES NOT. Getting pretty used to that broken record. Nothing changes, just Bungie marching on to the next DLC or Destiny 2 and not caring about us players. Quality control Bungie, means turning out a product that works at 98% efficiency when we the players are cautioned that we are beta testing. Then at that point you the devs are supposed to be fine tuning to make it 100% efficient. Yet instead of doing that, you are starting at 98% and dropping to 95% or worse now. I could go on and on but really, I'd just like to see a fix so I can play how I already had it before the patch was released. I want to be able to join friends again and not get kicked to orbit or get an error animal code. You fix this and I'll be somewhat happy. There are many other issues, but I would at least like to be able to play the game. Btw, it's not my internet. I checked that and got successful connection with PS4 network at over 60 mbps download and over 4 mbps upload.[/quote] I have the same...
-
A ZOO!! A damn zoo of error codes..is it a preview of the next big project? Drum roll...suspense..bungie is glad to introduce you to the next-next Destiny chapter..the one where the speaker asks his guardians to find and restore a fallen ship (3 motes of light as a reward ) step 2 scout the solar system looking for animals..possibly 2 of them for each species and store the poor vermins on said fallen ship.(reward a sub level but exotic thing to catch those animals..given after you finished the job using dismissed cabal helmets..unleass the beaver is radiation level big..then using a titan's dome or something..) step 3 wait for the floods..and for cayde to come up with a dastardly plan on how to prevent it or how to best cook all those animals/error codes.. This game is still nice to play sometimes..but those moments are always reducing in numbers..and i fear even the hardcore players are starting to drown in the floods of bugs and poor customer care..
-
1 ReplyWas playing a few matches of crucible and out of nowhere the beaver error code came up and now I cant do anything. Tried fixing network and the network was not the problem. Is this because of the update?
-
1 ReplyThank God somone else knows my pain!!!!!!
