{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
11/23/2014 2:02:02 PM
13
Literally can't play Destiny after the update
Update the 1.03 update. I literally can't play Destiny. I can connect to the server and stay in the orbit and that's it. Everything else gives me the #currant error and kick me back to orbit before the loading finish. Even after i tried to get into the server, it still randomly kick me back to orbit with #hare error.
I have a 32/32 fiber connection. I even bought a new switch and router yesterday, DMZ my PS4, open all ports and it only gets worse. I can't even farm mat and play the daily today.
Anyone got a fix?
-
i have the same problem, i get kick back to orbit or get disconnect from xbox live and sometimes it will take a few hrs to reconnect
-
Might as well put this game away until bungie figures it out. How disappointing.
-
https://www.youtube.com/watch?v=VJ5PZyTBBA0&feature=youtu.be I uploaded a video to youtube. It sums up my Destiny experience in the last 3-4 days.
-
Same for me the last two days. Constant disconnect after disconnect and booting me clear to the start screen. Usually it is only to orbit but since the update its the start screen. So sick if seeing "Contacting Destiny Servers" I just logged off. Never have experienced this much frustration or fatigue from a game like this one. Gives me a migraine :(
-
4 RepliesHey stainsoftime, I am sorry to hear you have been having these connection errors recently, and we understand it is frustrating to hear that changing your home network can help if it was working previously, and if port forwarding is making the connection worse we recommend clearing out the port commands and attempt enabling UPnP if you have not done so. In some cases, even power-cycling the router/modem and the console itself can get rid of these errors, as currant and hare are general network errors. If none of the above-mentioned steps work, we are aware that sometimes this is out of the player's control, and we understand this may be an issue you cannot solve alone and is not an issue on your end. In all cases, we’re constantly monitoring and improving our network services to keep Destiny up and running for as many players as possible.
-
2 RepliesEdited by Kekker00si: 11/23/2014 7:37:25 PMYep, like bee error is supposedly connection trouble between me and internet, and I should do something for MY connection, but I still am able to play every other MP game on xbox live. And on top of that I was able to play Destiny too without significant troubles for many weeks. I hate that Bungie puts these vague responses here concerning these error codes, and they basically say WE customers have problems in our end, in our connection, router whatnot. And everybody knows these problems are in their end, and latest update just broke game for me completely.
-
1 ReplyThis is getting very disturbing..... here is a list of the error codes I've gotten in the last 24 hrs: Coconut, Nightingale, Cattle, Bee, Lion, Baboon, Weasel, Currant. Most of these are occurring within minutes of one another. I can see if it is the same code over and over again, but it's not. I've even tried to reconfigure my network and assign static IP addy to my console in hopes of helping with this issue....i get nothing. Help us out, Bungie, please.....
-
1 ReplyEdited by Grey wolf SWAT: 11/24/2014 4:00:02 PMI just deleted destiny completely and then re installed destiny, because after the update i had the same issues. I did not download destiny ether i have a disc copy it took an hour but it worked destiny plays as good as new.
-
The fix is you play a different game. As far as Bungie cares, they got your money so we can screw off. They blame the issues on us all the time when its their shitty servers and such.
-
2 RepliesDisconnects every few mins from Xbox live. We've done everything and more that bungie recommended and no change. Game was perfect before the patch and now it's unplayable.
-
1 ReplyA lot of us are in the same boat. I was able to do one strike and midway through the other one before being disconnected for weasel and then bee and then fly. A total playtime of 20 minutes. I've done everything short of buying a new router which is not going to happen since mine is a top of the line gaming one. I really enjoyed this game but in the state it is in right now I can hardly say its worth the effort to continue playing.
-
Its the same for the xboxit was fine sunday morning know i cannot even do three mins of gaming befor chrashing I hope they fix it.
-
Bungie's side not yours
