{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/27/2016 5:45:43 PM
8
How about Bungie fixes their damn Matchmaking and netcode first? I don't have any lag in other shooters like Call of Duty, Battlefield or even the goddamn Titanfall 2 beta only Destiny has been a lagfest since Y2 when 2.0 came.
English
-
Same here. Only Destiny gives me issues. It's Destiny's last gen P2P mediocre networking. Just like you I'm playing almost every other shooter out there (most running decent DS) and not having problems, and I don't have to do any technical wizardry to get them to work. Also not hating the Titanfall 2 "TT". Definitely not something I'd shell out $60 for, but it's definitely running better than the crucible.
-
I feel exactly the same!
-
OK so your one of those guys. All the games you list run over standard ports that should already be open for PSN and XBL to actually works. Destiny runs on non standard ports, so users need to open those ports to get the best possible exerience But hey, your a CCIE and I should need to tell you this, right?
-
Doesn't Destiny run on TCP/UDP port 3074 on XBox? Isn't that the XBL port for most games? How is that a non-standard port? [spoiler]Don't be so pompous toward everyone who disagrees with you.[/spoiler]
-
Gaming should never use TCP...
-
XBL apparently does for some things. I haven't looked into what.
-
Edited by murrgh2014: 8/28/2016 5:29:32 PMThen they are stupid... I'd actually expect TCP for any authentication. But, no. Not for actual gaming. It wouldn't work.
-
Who knows? Could be for anything that requires no data corruption or out of sequence packets. It probably has nothing to do with the actual gameplay.
