Posted: 28 Jun 2010 12:07

Thanks, mister Obvious. We know. This doesn't answer anything.

Posted: 28 Jun 2010 12:07

soo before it was showing ping now latency, as far as I was told there is a difference hence the higher number?

Posted: 28 Jun 2010 12:28

looks like they only changed the scoreboard display

Posted: 28 Jun 2010 12:34

All im woried about is my game play, and its much much better now imo and in many others, in fact a lot of people came back to AA3 after this patch because of the improvement in game performance, you guys are worried about what is displayed.. I dont care if you display a donkey as long as its smooth

Posted: 28 Jun 2010 13:12

[Ri051]LittleCannon


C:\Users\Dad>ping 74.63.64.138 -l 512

Pinging 74.63.64.138 with 512 bytes of data:
Reply from 74.63.64.138: bytes=512 time=53ms TTL=116
Reply from 74.63.64.138: bytes=512 time=54ms TTL=116
Reply from 74.63.64.138: bytes=512 time=56ms TTL=116
Reply from 74.63.64.138: bytes=512 time=56ms TTL=116


here you go smart mouth. Not a huge difference, and the ping shown in game is STILL WRONG you wing nut.

Posted: 28 Jun 2010 13:53

Whether they're right or wrong, you still can't punish that person for something they have no control over. We don't all have 200mg connections and shouldn't have to be punished for it. I know its up the admins, but they all need to be schooled heavily on how to be one. Some are fine and fun to play with, but others are some seriously power trips. They suck all the fun out of playing the game. I got kicked from because i was chatting when i was dead. how lame was that. Specially when i was answering the admin's question, though i guess that was bait.

I've gone into servers and had a ping of around 200 and completely wiped out the other team, which had supposive pings of around 50-100. 90-180 is around my normal ping in most servers, 200 in some of the laggier servers. For me, its the norm, i've played with that kind of ping for so long that i know where to aim and how to compensate for it.

Posted: 28 Jun 2010 13:53

Calm down and treat others with respect. If not you'll find this thread locked very very soon.

Posted: 28 Jun 2010 13:57

richei, i've always thought player ping had no effect on the server, but that's simply a misconception. in aa3, at least, a high pinger will actually ruin the server's performance. there were many instances where the server started lagging and the only solution was to kick the foreigners that recently joined.

Posted: 28 Jun 2010 13:59

fedayeen wrote:

Thanks, mister Obvious. We know. This doesn't answer anything.

Actually it does, the scoreboard ping is the correct one, it it THE ping, everything else is wrong(yes, we know)

Posted: 28 Jun 2010 14:06

richei wrote:

Whether they're right or wrong, you still can't punish that person for something they have no control over. We don't all have 200mg connections and shouldn't have to be punished for it. I know its up the admins, but they all need to be schooled heavily on how to be one. Some are fine and fun to play with, but others are some seriously power trips. They suck all the fun out of playing the game. I got kicked from because i was chatting when i was dead. how lame was that. Specially when i was answering the admin's question, though i guess that was bait. I've gone into servers and had a ping of around 200 and completely wiped out the other team, which had supposive pings of around 50-100. 90-180 is around my normal ping in most servers, 200 in some of the laggier servers. For me, its the norm, i've played with that kind of ping for so long that i know where to aim and how to compensate for it.

So you're admitting that you have a high ping and ingnore the fact that you're laggin other players. Hmmmm.... I'd be willing to punish anyone with a high ping. Their ping is either high because they're playing on a server that is halfway around the world (which they shouldn't do) or they can't afford to pay more than $10 (or the local equivelant) for internet connectivity. It's not the server admin's fault, nor the other players fault that you can't afford a good internet connection. And if you're paying out the butt for the connection and you're gettin these high pings, I'd talk to your connection provider and tell them they need to run some diagnostics on your segment.

Posted: 28 Jun 2010 15:41

=IK=Doba= wrote:

soo before it was showing ping now latency, as far as I was told there is a difference hence the higher number?

There is a difference in the calculations. Standard ping is a network layer machine to machine latency test (not really affected by server load, only by the "load" of the network cards and the connection between them). The AA3 client "ping" calculation shown in the display really is a server latency calculation calculated by the response between the AA3 server and client, hence the difference from the tcp/ip ping command. This should provide more accurate quality of service info regarding the server and the client's connection to it.

Posted: 28 Jun 2010 16:29

frankof wrote:

fedayeen wrote: Thanks, mister Obvious. We know. This doesn't answer anything. Actually it does, the scoreboard ping is the correct one, it it THE ping, everything else is wrong(yes, we know)

That does not explain why the new scoreboard pings divide neatly by 4 into the supposedly "wrong" pings shown in the server info. They don't even divide just approximately, but EXACTLY. This cannot be a coincidence. Go into any server and try it yourself if you don't believe me. Hence, all that was done was multiplication of old ping by 4. Until you provide an adequate answer I've no reason to believe otherwise.

Posted: 28 Jun 2010 17:04

[programmer]

The internal latency calculation didn't change. This value is converted to an unsigned 8-bit number (range 0-255) for optimized network transmission (needed by all of the other clients for display) thus the number has to be divided by 4 to transmit (max = 1020ms displayed). The client's display needed to be multiplied by 4 to restore and display the correct value (it wasn't). This error was discovered and changed in 3.0.8. Anything above 255*4 (1020) is capped (assume not playable at this latency so display above 1020ms is irrevelant). The previously displayed value (< 3.0.8) really amounted to a latency index as it wasn't tied to any specific time unit.

[/programmer]

Hopefully this clears up the ping calculation.

Posted: 28 Jun 2010 17:57

[Dev]SledgeHammerD wrote:

[programmer] The internal latency calculation didn't change. This value is converted to an unsigned 8-bit number (range 0-255) for optimized network transmission (needed by all of the other clients for display) thus the number has to be divided by 4 to transmit (max = 1020ms displayed). The client's display needed to be multiplied by 4 to restore and display the correct value (it wasn't). This error was discovered and changed in 3.0.8. Anything above 255*4 (1020) is capped (assume not playable at this latency so display above 1020ms is irrevelant). The previously displayed value (< 3.0. really amounted to a latency index as it wasn't tied to any specific time unit. [/programmer] Hopefully this clears up the ping calculation.

Have I told you today that you're my hero, Sledge?

Posted: 28 Jun 2010 18:05

[Dev]SledgeHammerD wrote:

[programmer] The internal latency calculation didn't change. This value is converted to an unsigned 8-bit number (range 0-255) for optimized network transmission (needed by all of the other clients for display) thus the number has to be divided by 4 to transmit (max = 1020ms displayed). The client's display needed to be multiplied by 4 to restore and display the correct value (it wasn't). This error was discovered and changed in 3.0.8. Anything above 255*4 (1020) is capped (assume not playable at this latency so display above 1020ms is irrevelant). The previously displayed value (< 3.0. really amounted to a latency index as it wasn't tied to any specific time unit. [/programmer] Hopefully this clears up the ping calculation.

Im confused,but overall gameplay seems smoother, even when the avarage pings are 70 to 160,where as with 3.0.7 these numbers would cause a server to crash.