{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Antox:
8/10/2016 1:27:22 PM
28
WHICH NETWORKING HEADACHE ARE YOU HAVING SINCE HOTFIX 2.3.1.1?
[b][u] ***PLEASE BUMP! IF YOU VOTE IN THE POLL!***[/b][/u]
[b][u]I'm interested to know how many people started having issues since hotfix 2.3.1.1 and are now persisting after the revert (not including issues Prior to that) and exactly what issues they are. In hope that this information will help bungie fix the problem faster.[/b][/u]
This is the worst time I have ever had TRYING to play Destiny. It is clearly not our network setup causing so many issues on this grand scale. I have read many posts with so many people fustrated at the moment, clearly there is a problem with the game/servers otherwise they wouldn't have pulled the hotfix, which when released marked the start of the majority of players issues with the game at this time. No other games are having such bad connectivity issues, and again this all started when bungie changed something.
-
So it's not just me?! That's reassuring at least. Games also take so long to find....
-
Has anyone else experienced a loss of their roster? Since the update my roster will not show me my friends list so it makes it a hassle to actually see who's online and join up on people.
-
Yesterday I was constantly being kicked out of my fireteam with a message saying that I had left my fireteam. Cleared the cache of my XB1, made a hard restart, restarted my router, etc, but I had to give up the raid. Went to crucible and for the first time since 2014 I had a red bar in Destiny, never happened before. Tried some other games online and all of them worked perfectly smooth, no issues at all. Came back to Destiny, went to crucible and again red bar. Lot's of messages appearing at the bottom of the screen saying "contacting Destiny servers..." Not funny Bungie, not funny at all
-
I'm not getting into crucible or matchmake strikes. Does not find any other players? NAT type ok and connection speed perfect?
-
I've only been having issues with red bar gods topping the charts, but that's been ongoing. I'm so sad to see how many people can't play with their friends or at all. I take it for granted. I'm sorry guardians! You can come to my house!
-
I can't get past the connecting screen and have gone through all of the supposed fixes
-
-
New games are not starting out with full rosters. Usually 2v4 or 4v4. Even had to go solo for the first 3 minutes against a team of 6
-
3 RepliesEdited by M1ED: 8/12/2016 1:17:06 PMJust read Deej's update. My Gad man. Don't you think that your players have more than two brain cells and have already traced any possible problems on their end? Are you so arrogant to think that we have no idea how computers and networks run. That you have to hold our hands to walk us through setting them up? Forget Germany pal. And fix this game. It isn't my system or my Nat. It isn't my ISP or my internet. It's that's lousy ass patch you put out that is full of bugs that's screwing everything up. Ed
-
Beetle and baboon FTW baby! Running heroic strikes, get kicked, spawn back and all my heavy and special ammo away! Happens all the time, even with baboon. Or when you are at the boss, almost dead and a booster on... Kicked! Off course NO XP! Kicked to orbit and beyond Star trek: eat your heart out! With destiny we just get kicked to orbit and beyond. And we don't even need an expensive ship with lots of personell. XD
-
I just started playing on the PS4 yesterday without issue but I'm getting iron banner levels of contacting Destiny servers this morning when of course all my tests are good.
-
Edited by HiPOJaK: 8/12/2016 8:24:51 AMBump - every error code under the sun. Never had a single error before the beaver hotfix.
-
2 RepliesUnable to join husbands fire team and vice versa since the 26th July. He's also getting booted from anywhere with beetle or beaver, although that's ceased now due to the rollback. Kind of makes us buying 2 PS4s pointless at the moment.
-
2 RepliesUnable join my sons in the same fireteam since the 26 July update. Helping my kids level up was a good father /son(s) quality time doing something we all love to do. Hope Bungie fixes this issue.
-
2 RepliesYou left out the "None." option. That's what I'd click.
-
I've had zero netwoking issues, other than Destiny's famous PvP lag and the recent beaver fever that affected everyone for a few days after 2.3. I've honestly not noticed a sudden change in PvP lag since day one. As the player base shrinks, I have witnessed an increase in foreign opponents, and longer matchmaking times, but it's been a slow and steady change, nothing I can pin on a particular update.
-
I've actually noticed big time crucible improvements. I know some of my friends were having issues before 2.3.1..1 Not sure if they still are, or even if they were Destiny related since they're part of the preview program.
-
9 RepliesWhere is the "no errors at all" option?
-
1 Reply
-
-
1 ReplyUnable to join friends from friends list
-
No issues previously, fibre broadband and type 2 Nat same router same house,and now can't join up since patch. Bungie has buggered up game and instead of removing the hotfix they just leave us to get get annoyed! I love this game and I preordered, but how long are they just going to drag this on for, they should be dealing with this as a priority and seeing if the can resume temporary service by removing the patch.
-
The infinite "Evaluating guardians" when trying to find a game.
-
All day baboon fire team join failure unable to load . Crucible won't match make , patrols lagging with contacting destiny servers . It's quite a nightmare. Not fun. Yes I've followed the networking instructions . And no it's not my internet !! Common bungie listen to us and let us know an eta to patch yesterday's patch. Cause your broken right now !!
-
3 RepliesNone of the above? We've tracked down issues in the Carolina's that are still not resolved. Problems we found with exchanges into XO.net cleared without us contacting them. Some Level3 exchanges still want to act up from time to time, but my ISP is usually able to route around it. So...the issues I have aren't game specific but ISP centric, so are being handled via my ISP. The problems were actually detected when affecting other services so weren't really impacting Destiny--when I know signalling is unreliable for twitch gaming, I don't load Destiny. So I've pretty much only seen the contacting servers one night when a player in Michigan was team leader. Otherwise I've only noticed the odd red bars here and there, but nothing has been game breaking on the networking side when I've played. But then again, I am more aware of the state of our routing in general than most may be because of all the time I've spent with my ISP in the issue. Perhaps some of you guys need to get in touch with yours as well. Make sure you are configured properly for this game's p2p model and if it persists bring your ISP's tier3 team on board to investigate.
-
Marionberry on every log in :(
