{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Bearbeitet von SirJ2theK:
6/29/2016 4:20:25 PM
30
Contacting Server Banner constantly
Latest edit: I feel our post has run its course, we got no answers or even acknowledgment so Your Welcome Bungie my money will be ready when Destiny is.
At least we tried to help each other.
I am receiving this error constantly,
I have refreshed licences,
Cleared Cache,
Restarted Router.
I use a lan Cable cat6
My mtu is set correctly for my broadband default doesnt work either,
And i have a separate switch for cabled bandwidth traffic.
Video shows frequency over 2 minutes just a sample to show people.
Its not always the users fault.
I hear it loud and clear unlike bungie who is scurrying around the game files to see whats happening.
I have had my moneys worth with this game which is why i can say we need dedicated servers but the dont even reply if the did it wasnt public enough.
Bungie is "investigating" the issue, thats fair enough but its not a solution.
We all know the solution but arent told why we cant have it.
Why are we getting sh!t on because bungie cant resource manage.
A reasonable answer is all we want. Investigating the issue wont work any more.
-
It even shows up on patrol and story missions.
-
I have been seeing the notice but it hasn't caused any problems.
-
Bearbeitet von Pacifico Slim: 6/29/2016 10:47:45 PMThis happened to me all night last night, and all this afternoon. Never got kicked, or disconnected, but it is frustrating.
-
All night on Tuesday, even got kicked to the title screen. What's up with that?
-
I got it alot but it never affected gameplay
-
I've had that "error" pop up at least once during each game I played IB. I was still in the game but it can get pretty annoying and it's basically a false error in this case.
-
5 AntwortenBungie is aware that players have been receiving "Contacting Destiny Servers" and are investigating. https://twitter.com/bungie/status/747906233818976256
-
2 AntwortenHard wire
-
1 AntwortenI got it too and then went away in game, my bar was green the whole time.
-
2 AntwortenSame crap happening to me and other people I play with on Xbox One. Does not happen on Raids, only when I go on Patrol or to the Tower/Reef. Other XB1 players said the same thing. Obviously Bungies maintenance to the Servers this morning broke something.
-
1 AntwortenSame here. In a fireteam of 6 yesterday, several people got that message. Repeatedly. While connection bar was green. Most of them had wired connections. That's new.
-
1 AntwortenBearbeitet von Gralen: 6/29/2016 7:35:38 AMSame here. My wife even got booted out of an IB match. This is super frustrating and only started happening after maintenance. Also am getting an exceptionally large number of Beetle errors.
-
2 Antwortenmost expensive beta ever. hopefully they take all our money and make sure destiny 2 is above all this.
-
1 AntwortenI've had this constantly throughout this iron banner. Pain in the ass.
-
Come to my twitch stream for iron banner blaowzin_420
-
3 AntwortenWould like to know if this helps any at all lets try to get it up top of forums
-
2 AntwortenOne guy reported me and recorded a video of me lagging cause of the contacting destiny servers and probably got his whole fire team to report me lol
-
1 AntwortenYeah, it feels like I'm getting it every 5 - 10 seconds.
-
6 AntwortenI have same issue. me and a buddy were able to play two games after update, and i playied a couple as well before that we joined up why could i play for only an hour or so now cant join or find a game
-
10 AntwortenI have this issue.
-
2 Antworten
-
1 AntwortenMe and my friends are having the same issues.
-
1 AntwortenSame issue
-
1 AntwortenChange the tag to #help.
-
1 AntwortenBearbeitet von CozmicClockwork: 6/28/2016 10:04:19 PMStrangely enough Im more pissed off I couldn't navigate my menu than the lagging striker I faced earlier.
-
Bungie's net code is garbage. Did you not get the memo?
