{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/25/2014 7:46:00 PM
7
Can you guys fix the dropping fireteam members ASAP? My friend I want to play with is about to quit Destiny already, and we've only played a few days together...
The "check your nat type" and "port forward" advice is unhelpful and a little insulting to people who have tried that or know that's not where the problem lies. In my case, not only have I done it and it's completely "open/Type 1," (and port forwarding is a hassle when your router happens to gets reset and shouldn't be necessary just to make [i]your[/i] game run) but it's only related to being on someone's fireteam while you're on the same network. I have no problems playing with 2 systems on the same network with [i]any other game[/i]. I see a bunch of people reporting similar problems on this site with that particular problem not being addressed other than the nat/port forwarding advice when I look it up via Google, and a quick search didn't show anything on the feedback forum's main page. I'll keep bumping this so it's noticed.
[b]This is the important part though;[/b] Like I said it only happens (in my experience at least) when you're in the same fireteam as someone on your network. Meaning you can both be playing Destiny through the same connection only not together, as soon as you link up together it starts dropping one or both players every few minutes. The problem lies somewhere in the fireteam/network setup.
-
Bump! It was especially bad today! Inchworm, Quail, Jackrabbit, couple I can't remember galore! [b]Addendum;[/b] It happens when there's certain players in the same arena. Like when at ______(insert location here) on Venus or Mars and the notification pops up saying someone is in the area it's a roll of the dice whether or not one of us will be booted. It's almost never fireteam leader either, we've switched off and it's usually the joiner who's booted. Next, whenever we tried to join a strike we were perfectly able to, but the third person was forcibly booted it seemed. It would say the third was playing with us but he never loaded up until they appeared to quit. Speaking of which, during both a Public Event and a game of Crucible; During the former, a Warsat and all participants were invisible and intangible, only popping up for the joining player a minute into it! And for the latter, the same thing during multiplayer. The whole team was in game and running around, but nobody could see or interact with each other until a few minutes into the match when everyone suddenly appeared to each other.
