{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by voiceafx:
8/27/2015 5:24:21 PM
4
Crucible - network problems only when in fireteam. Multiple PS4's on one network.
We have 3 PS4's sharing a 100 down 20 up internet connection through Comcast. Our modem is the TC8305C. UPnP is enabled, and we are NAT type 2. Can't do NAT 1 with port forwarding because we have multiple PS4's on the network. Average ping latency is 46 milliseconds (typically), with average latency jitter of around 1 ms. All our connections are wired, no wireless.
We can all be playing Destiny separately in Crucible with few problems, but the moment we jump into a fireteam together, one or more of us is consistently kicked to orbit, and Destiny itself often errors out and force-closes. Typically this happens during or shortly after matchmaking. It has never happened while we were still in orbit. It *has happened mid-match before. We rarely have problems doing PvE strikes or patrols as a fireteam (haven't done a lot of raids, so can't comment on that). We've tried deleting and reinstalling Destiny with no effect.
Sometimes Destiny complains that we are on NAT 3 even though we are not. Not sure if this problem is related.
It's worth mentioning that we don't have problems with any other game - we can play as a party in Battlefield 4, Call of Duty, or Borderlands and, on the PC, Heroes of the Storm and Starcraft. Zero issues, except with Destiny. We have good ping, low jitter, with bandwidth to spare.
There is obviously something going on here. The fact that Destiny force closes on network errors is indicative of a problem with the game itself. At the very least, it should handle errors gracefully, and it's not like you have to worry about different hardware - this is the PS4, for Christ's sake. Also, the fact that Destiny alone seems to have problems like this, and (in this case) only when we form a fireteam with PS4's on the same network, is suggestive of an in-game bug.
But I'm open to suggestions. How can we fix this?
-
2 RepliesEdited by Tok Ra Jolenar: 8/27/2015 5:30:27 PMHi Voiceafx, I have setup gaming rooms and stations for multiple PC and Console systems. The key to this type of network is processing power of the router and true available bandwidth of the ISP. I have found that modem router combos are not the best choice for multiplayer online intensive games as their components are substandard to keep the cost of the units down. The symptoms you're describing sounds as if the combo unit processor is not fast enough to handle the port routing and NATing required. Inclusion of a standalone router may help your network perform better. At this time most high end consumer routers from Linksys and Asus handle multiple devices simultaneously without issue out of the box. If you go with this method you'll need to get your ISP involved once you're ready to connect the router. They will need to change the network protocol of the modem to accept the router as the new gateway for network devices otherwise you'll be back where you started. Concerning the ISP most providers balance bandwidth at hubs to ensure equal service to all parties. This can at times slow ping rates and constrict bandwidth during high volume. Which in turn will affect game performance. Depending on the game and console, console/game rebooting as long as this does not occur often with any game is a function of both the program and console pulling a network error that enables a data protection module to prevent malicious intrusion into the source material or network manipulation. Hope this helps. Edited for more content.
-
Edited by voiceafx: 8/27/2015 5:07:24 PMBump. I'm not going to let this post disappear into the noise. Considering that Bungie has no method of providing support other than hit-and-miss responses to forum posts, I'm holding out for a response from Bungie.
-
3 RepliesEdited by KannibalKlown: 8/27/2015 3:35:35 PMIt'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.
-
If bungie answers I'll buy the expensive TTK version.
