{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/22/2016 12:03:12 PM
8
So 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. This should 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.
English
-
Wish I could say that this worked but it did not. Everything went as you listed up to the weasel error. When we logged back in, tried to join on my son's character and it failed.
-
Did you do all the steps at the same time?
-
Yes. First tried it just as you typed. No good. Next, we tried resetting both consoles, then following the steps you listed. No good. Then we tried the full-monty reset (both consoles shut down and unplugged, AND bounce the main router/modem) and following the steps listed. No good. At this point, we're just resigned that Bungie's code is so jacked up that nothing is going to allow us to play the game as we once did. And this is the only game title that we have this issue with. I'm looking in to using a Meraki MX router in the DMZ behind our main AT&T router. The Meraki equipment is capable of handling 1:many NAT relationships, so each console should be able to reside behind the MX and hit the game servers. If it doesn't work, I can always send the Meraki equipment back (they are good that way).
-
I'm sure you have already done it at this point but did you try using steps with new names for your consoles? Sorry to hear of the issues btw
-
New names you say? I've given the consoles different names (the very imaginative "xbox1" and "xbox2"), but I've not tried renaming them. I'll give that a shot tonight. No worries man. Typical for this game studio that they drag their feet towards an actual fix to this issue, all the while leaving it to the community to come up with solutions. Thanks for the tips. Even if they don't work, it's exactly 100% more than I've gotten from Bungie.
-
No worries. Good luck
-
Thanks for the suggestions. We'll give it a try. Nothing like raid-class complexity of steps just to the play the game!
-
Indeed but hopefully this resolve doesn't get "fixed"
