{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Majora:
10/21/2016 4:51:19 AM
8
Such a sad day that we STILL can't connect local! And, with no hope in sight!
How long has it been now? All we get is moderators and Q.A. Testers trying to convince people the issue is on our end. Funny how that works. But hey, would anyone really expect Bungie to own up to their mistakes?
All the people that bought multiple systems, multiple copies of the game, multiple network subscriptions. Only to find out that after a broken ass 2.3.0 update, it was all for nothing. And still, after all this time, we get the same bull crap for an answer. Bungie are "Actively investigating" the issue. That's it. No timeline. No details beyond the generic copy/paste.
I think what the are really "Actively Investigating" are plans for their 6wk vacations coming up and exactly what to cut and charge us extra for as so-called expansions in Destiny 2.
-
15 RepliesHello mustafarkilla, I am sorry that you are experiencing these issues. Have you tried checking out Bungie's [url=https://www.bungie.net/en/Forums/Post/210723595?sort=0&page=0&path=1]Local Network Fireteam Issues[/url] thread?
-
4 RepliesI understand the frustration. I was in the same boat as you. My flatmate and I had no issues prior to 2.3.0. Yes I think Bungie have changed something their end, but we did some testing, neither of us are computer geeks but we figured it was to do with the way that your Router interacts with Bungie's servers. The signal comes in at point A is split to both parties so you can get online, B1 and B2 then when you join a fireteam, point C, the router assumes it's one and the same, hence your issue. So we figured it was the router, ours was a BT home hub 6, pile of shit, user friendly waste of space. So we changed the router, stuck £60 in each, I'm sure there's cheaper options and bought a gaming router. Easy to set up and since then no issues. We've done nothing else to the connection, no settings changes, it just works. So it was down to UPnP all along, I still think it was Bungie upgrading something. But for me that worked and no issues since.
-
It is sad they refuse to fix this.
-
1 ReplyIm having exact same problems as you are I can be playiny for hours then all the sudden cant stay on for a minute im personally tired of it Im hard lined also tried resetting modem constantly shutting down ps4 and unplugging it still same problem fix it Bungie.
-
1 ReplySo this is a work around that seems to work 100% of the time. Trust me when I say I have tried EVERYTHING else! 1. Both players load the game and go to the tower. 2. Both player at the same time press the XBOX button and quit the game. 3. Both players at the same time start destiny again and this should generate a 'WEASEL' error. Thus shoukd usually happen to both players. 4. Close the error and continue to selecting your characters. 5. You should now be able to join the same fireteam team. I know it's a ball ache it this does genuinely work. You can even leave the fireteam after and you will have no issues rejoining. This is a fix for as long as you are online but the next time you play you will have to do this again. Just goes to show that this is truly a bungie issue as to get this to work no changes to any network settings need to happen. Hope this helps.
-
2 RepliesI understand the frustration, but we already know that Bungie is aware of the issue, so there is not much to do other than waiting and hoping. Also, to avoid misunderstandings: moderators are not Bungie employees, and if I remember correctly neither is that guy that has Q.A. Tester or something like that in his forum signature.
-
3 RepliesIt's bullshit, they are not working on it...
-
1 ReplyI fixed it by putting one on hard wire and left the other wireless. Maybe this will work for you?
