{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/1/2016 7:42:55 PM
1
While I tend to agree with you, Battlefield 4 is a classic example of how that doesn't necessarily mean squat. It took DICE years, and eventually a new studio taking over, to solve issues with netcode. And that was with dedicated servers, a server browser, ect...
English
-
Just proving my point. Good servers isn't enough. Good net code isn't enough. Good quality live environment testing isn't enough. You have to have all 3 working in sync.
-
Even after nearly 2 years, I'm amazed that this is p2p. Like we're still on the original Xbox. LOL!
-
i totally agree with every one of your comments... and a side note about myself: year one player, who just recently came back. i've been playing dozens of other games with no problems like destiny's. if the spent their money on their connection issues instead on their advertising budget, they would be an amazing company... but after two of this garbage , its obvious it will never happen..
-
This is an interesting point. I've been running two Xboxes on my network for 8 years now. I've never played a game that constantly reboots my router, or kicks us all off line. I'm wired, and my son is wireless. He is constantly having to refresh our wifi when we are both playing Destiny. But if we are playing a different game together, or separate games, no issues. Ever. I don't know what makes Destiny different, but it puts my network through hell.
