Exactly. Latency doesn't bother me as being a part of the game - I merely call it out when I see those outliers. HTC has done a great job with the smoothing coding; and there have always been those outlier connections.
If I can be bothered to make the needed adjustments, the latency issue becomes less of a factor, but I'm not going to fly around thinking every plane is a latencyboi; this would lead to more frustrations and deaths, so in general I just avoid those areas where know laggers are operating, or make the occasional conscious effort to deal with them and send them to tower or running for ack/help.
I can't tell you how many times I had seen people accuse judge (and others) of using hacks, so part of why I keep going on about latency is to educate those who aren't as familiar with the effects. There's a parallel track (heh) with the GVer and trees. The trees are rotating 2d planes not high fidelity 3d objects, so math finds a way.
Accusations of (various forms of) cheating are more harmful to the game than any smack talk on ch200, imho. And as I've mentioned the visuals and understanding of connections/latency (and even variance, aka warps) have been something I have a clue about.
Probably need to add another quote to my sig file: "Explanations aren't excuses."
So if someone has a crummy connection should they not play?
Should they wait to hear your pings before they fire back?
Not sure what you think a fix would be
If they aren't manipulating their connection on purpose to cause it I think we have to live with it
Eagler
