 Zero-K server has been moved from France or Germany (not really sure) to Canada. Canada has shorter tubes to Asia and Oceania while also still being reasonably close to Europe, so in theory, this should help people suffering from too high pings without hurting other people.
+8 / -0
|
if my ping went up im forking zero-k /s
+0 / -0
|
Back in Canada, so now my bullshit is even more effective! Huzzah!
+2 / -0
|
if it does fail i have 2 weeks subscription on a server provider service in perth WA.. its only 7G ram but im not really using it so i thought id offer
+0 / -0
|
I live in Brazil so I'm doomed to never have close servers to anything. However, I find that its not much of an impediment to Zero-K. My reflexes suck anyways, so I never try leet micro strats that would require super reflexes.
+0 / -0
|
300-700 ping, kinda around 500 most of time. I can live with that, but its unpleasant.
+0 / -0
|
quote:
Zero-K server has been moved from France or Germany (not really sure) to Canada.
Canada has shorter tubes to Asia and Oceania while also still being reasonably close to Europe, so in theory, this should help people suffering from too high pings without hurting other people.
|
sad im very sure france or germany to germany would be much closer then canada to germany
+3 / -0
|
  shrimpy: correct. It's a matter on how you present it though. If we take Paris, Frankfurt and Montreal, you could say "a whole 0.08s difference" or you could say "9x slower latency" (reference: https://wondernetwork.com/pings/Frankfurt). Based on the link (first google result) is interesting to see how small the differences are in absolute values (Frankfurt to Wellington is only 0.3s for 18000 km!)
+0 / -0
|
Some BAR developers have been messing about with networking settings and found something that appears to improve ping. I'd like people to try these out in springsettings.cfg: quote:
UseNetMessageSmoothingBuffer = 0
NetworkLossFactor = 2
LinkOutgoingBandwidth= 262144
LinkIncomingSustainedBandwidth = 262144
LinkIncomingPeakBandwidth = 262144
LinkIncomingMaxPacketRate = 2048 |
+2 / -0
|
You can achieve low latency by decreasing loss factor. There are always tradeoffs, like if you do actually have packet loss or jitter you will end up being worse. Some of these settings should also be applicable to server side. We should check the netcode first however.
+0 / -0
|
|
|
The netLossFactor should be lower and not bigger. It decreases packet send frequency among other things which means updates are less often. The smoothing buffer i am not sure you want disabled. It will cause stuttering on any jitter (uneven transmission times).
+0 / -0
|
The other parameters (link incoming etc) are just for SERVER when hosting. And they LIMIT your throughtput, so keep it at 0, unless you want limits and dropped packets...
+0 / -0
|
My theory is that the internet has become more reliable in the 15 years since Spring's netcode was written, so removing some of the smoothing seems like a safe thing to try.  The link parameters seem to have non-zero defaults.
+1 / -0
|
Hmm ok we should set them to 0 for our hosters, reading from code it will remove various throttling limits
+1 / -0
|
that sucks cuz now it's >500 at least back then it was 300 hope they make it better
+1 / -0
|
