{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by RAIST5150:
8/26/2016 3:38:35 AM
4
Need to be testing quality to the other players and to Bungie's two networks in Washington and Arkansas.
You can have a two-fold problem of sorts. Background synchs to the Bungie databases can be having issues in route, or the routes to the other players can be having issues. Can get a bit tricky to track down on your own though...either snoop the packets or would need to capture all those addresses and run trace/pings to them. And Bungie's networks won't let you do that either...not to mention many players routers may not be set to respond to pings as well. Tier3 support may be one of your better resources to have on board...especially since it may be an upstream issue to be addressed with their peering partners.
English
-
Yeah I think you got it. This is what I was trying to tell the mentor. I can run nightfall and challenge solo, which means there's no peer to peer. Just me and their server(s). This problem exists even with my high end network stats and properly setup network as listed. Now, when I try peer to peer.... It makes gaming not fun since it combines the "alleged" sync issue with P2P latency.
-
Edited by Anidien: 8/26/2016 4:01:28 AM[quote]Yeah I think you got it. This is what I was trying to tell the mentor. I can run nightfall and challenge solo, which means there's no peer to peer. Just me and their server(s). This problem exists even with my high end network stats and properly setup network as listed. Now, when I try peer to peer.... It makes gaming not fun since it combines the "alleged" sync issue with P2P latency.[/quote] To clarify, the point was that you are not always connected to the same end point - it isn't just you and bungie servers, at all times. Solo, sure. But other times, you are peer to peer and the host is the prime communicator. Which means if you are seeing the issue in all game modes and situations (solo or in a fireteam or in a public place, in crucible, etc), the only common thread on the connection is between your console and the Internet. Which is why the suggestion is to start at your console, and work your way up the connection from there. Neatchee's suggestions were great paths to take.
-
I have contacted my ISP and my router tech support. Through much troubleshooting and testing on their ends they stated everything is working perfectly and suggested I request this tech issue to be upgraded through the game tech support since my Internet, network, router, modem etc.. is all properly setup and working (as I stated). Maybe a little more info on the issue. Again this happens solo and p2p. When it's solo it happens every time, but not every shot. Maybe 50/50, but it does happen every time I go solo (proving it to be bungie side since it's only in Destiny) an example would be an environmental hazard did not blow up until I used 40 rounds of Zhalo, then 4 minutes later I shot another hazard and it blew up with the 3rd round from zhalo. This transfers to ads and bosses as well. I can shoot an add with an entire magazine and it takes no damage (nullified) or sometimes it will take damage 1-2 seconds later. As far as p2p this unsynced or latency issue with bungie server(s) gets worse and has made pvp just terrible. The natural latency of p2p means it's more frequent and I have to use 10 headshots with a scout rifle to get kills 75% of the time. My shotgun rounds either do no damage or half damage at point blank range and my backstab perk only works on rare occasions (true backstab) and even uses up the charge. I have videos of my blade dance on xbox either passing through opponents or taking 3 hits to kill. So again I ask that this gets forwarded as a serious issue that seems to affect a small percentage of players.
-
I have followed all steps and guides, I have superb network stats. Yes, this issue exists across all types of destiny matches, but only in destiny. If the problem crossed over to other games then I would experience the same "lag" as when I go in solo, but I do not. This means there has to be some sort of delay from Destiny server(s). It's easier to say "it's you, not us", even though I realize you're not a bungie employee, but a mentor trying to help. In this case it's bungie not me. As I stated before I've seen people complain about the same issue after the Beaver hot fix and I think there's an underlying issue that has affected a small percentage of its gamers. When my son is on his xbox one (via WiFi) he has none of these issues, yet I do with wired and only on destiny. This (and the myriad of troubleshooting I've done) is the reason I came up with my "sync" issue. It's the only thing that makes logical sense.
