{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by KannibalKlown:
8/27/2015 3:35:35 PM
3
It's not necessarily suggesting an in-game bug.
It *could* be that X consoles on the same network going through the same router to the outside (and back in again) are causing the issue. Typically for things like this, all 4 consoles wouldn't be talking to each other directly on the LAN, but back out into the Internet, then back in again.
*Maybe* the router isn't coping very well with the port forwarding. *Maybe* the connection isn't able to handle 4 of you at the same time (ISP or Bungie). etc. And then just booting 1 or more of you because of *that*
I'm *not* saying that IS the issue, but *could* be related to the network setup in general.
Now maybe some / most / all-other games work fine with this setup. Maybe Destiny doesn't.
English
-
Edited by voiceafx: 8/27/2015 3:43:22 PMI'm open to that possibility. But either way, Destiny force-closing IS an in-game bug, regardless of the cause. It's fixed with a little trick called "Exception Handling." Furthermore, we play Battlefield 4, Borderlands, and Call of Duty as a team regularly without any problems whatsoever. (EDIT: And, of course, the fact that we can be all play Crucible at the same time without any problems UNTIL we join up as a fireteam is also suggestive of some kind of bug)
-
Edited by KannibalKlown: 8/27/2015 3:46:09 PMDifference there, is some games use peer-to-peer. Others use dedicated servers. With the P2P setup, playing in the setup you discuss, Destiny kind of round-robins which of you 4 is hosting the fire-team match... alternating within the same match (passing hosting responsibilities every once in a while). And as mentioned, things don't just stay local... all traffic goes out into the Internet and back in again. And maybe something is getting lost in the shuffle. Other games have a more dedicated server setup... all of you would be talking to a master server somewhere. The traffic is somewhat simpler here... YOU are talking back and forth to server, DAVE is talking back and forth to server, but YOU are not talking directly with DAVE. I've heard CoD is dedicated, but I don't know for sure if that's right. Either way, booting off the game is obviously a problem. But even in games, if the caught exception is big enough / bad enough they tend to kick you out. Especially since repeated issues would interfere with the rest. And chances are Bungie's netcode just cannot handle P2P'ing to people inside the same network very well.
-
I understand, and I agree that Bungie's peer-to-peer setup is very likely the source of most problems. But that doesn't explain why we can all play separately whilst on the same network without problems, while being in a fireteam together consistently causes problems. Somehow, fireteam network COM must be different than normal. Different packet structure, perhaps, or different ways of handling host handshaking. Whatever the cause, the particular scenario (multiple PS4's on same network, in a fireteam) causes consistent issues. That's a reasonable scenario under which the game should work properly, and whatever the under-the-hood explanation, consistent failure during normal use is, by definition, a bug.
