Help with Ping/Rubberbanding

[Flame Salamander]

It's kind of as the title says. Sometimes my game rubberbands, no clue how or why at times, because it's not consistent. I just know there are times where it gets really bad. Yet my net is still running fine. I don't think its an internet issue, but for all I know it could be just an issue with me connection to the servers at times. If any has any advice to reduce rubberbanding that'd be great. I tried netgraph to see what was going on, and I noticed my ping was in the 112-125 range, which is weird because my connection to most games usually results in much lower ping. Everything else seemed fine from what I saw on the wiki for netgraph.

[shortguy on indom]

• THIS HELPED ME SOME WITH THAT VERY ISSUE ON MY END:  https://www.grc.com/dns/benchmark.htm

[xaix1999]

The easiest answer is peak player time will cause rubber banding. The long answer is a much more complicated answer as shortguy was eluding but can be explained as distance, internet congestion and game server load.

 

Wireless vs wired can have an effect but it's usually not enough to be concerned. The next concept to be aware of is during pings, more exact is TTL. Time to live, is a limitation put in place to make sure our connections don't loop forever and the internet explodes, figuratively speaking. 😁

 

But time to live can tell us about the distance being traveled. I believe most windows has a default TTL of 128. So if you were to ping the game server and the TTL came back with 64 then half of your TTL is removed from each device that you traversed during your ping connection. What's more important than your TTL being removed by devices or that all of those devices that removed one TTL is all of those devices could have congestion from managing thousands or tens of thousands of connections.

 

DNS or domain name system can cause the initial start of the connection to be slow as your system looks up the website name with your DNS and waits to get an IP address back. Most if not all of this happens at the beginning of your CoX session. Unless the game crashes for some reason.

 

The most dominate issue that happens in online games when talking about rubber banding would be TCP replay and TCP out of order. TCP replay and out of order can be explained at the same as they can happen at the same time. If a game message like where you are or what power you are using like traveling to your next mission, required four messages and the server received 1, 3 and 4 then your computer would resend or replay message 2. Then the server sent back four messages but due to unknown reasons you received messages 2 then 4 then 1 and after the server resent 3 you receive 3.

 

These are very complicated topics and hopefully I haven't done anyone a disservice by oversimplifying them.

Edited September 14 by xaix1999