.Map :: MoHAA Mapping

Is there any way to show your ping on screen, like in quake?

i used the quake command:

cg_drawping 1

but diddn't work....

Pull up ur console and type

fps 1

and to turn it off type

fps 0

That's for fps, not ping.

an external program might be your best bet.

opps

all i know is the dos command:
ping -t xxx.xxx.xxx.xxx
x=IP

maybe this should be in scripting

rofl... no i think his best bet is to make a C++ prog that basically writes the server's ping (from query ports) on your screen. Elg has all that in it, just not querying ping.

cg_lagometer 1

once again, he wasnts ping not meters.

Rookie One.pl {sfx} wrote:cg_lagometer 1

ROFL @ lizard, calls himself a scripter

do you have any tact? You piss people off a lot with your attitude problem.
Notice that?

ROFL @ lizard, calls himself a scripter

do you have any tact? You piss people off a lot with your attitude problem.
Notice that?

Thanks, i like making people laugh.

cg_lagometer 1 is a small little meter on the bottom of the screen giving you server (blue, one would hope) and client (green, one would hope) in meters. it's nice, i use it all the time but Thanatos apparently wanted numbers.

no command i know of to return raw numbers, so i gave the only option...

hogleg wrote:do you have any tact? You piss people off a lot with your attitude problem.
Notice that?

Erm... Was that about me? I was in a hurry, just wrote a solution and that's it, why do you think it's impolite?

Just steeping in here, but hogleg, I find that post rather hypocritical

That is the most tactless denouncing of anothers tact I think I have ever heard/read...

No Rook, it was about me. Apparently i was tactless in trying to get the guy a number ping. I'll apologize if i offended you with stating the obvious, but i really can't see that being a problem.

I see.

Well, this is impossible anyway. The pings and score info are requested by the client (through the stats server command) and downloaded from the server everytime you press Tab, so this would be a little bit bandwidth-hungry. The lagometer is handled by the client game library and is a representation of snapshot traffic. Every snapshot has a timestamp. Their order is, obviously, based upon the timestamps. If you miss too many of them, mountains appear on the lagometer. They actually don't represent your network performance, they're frames where the client game library had to perform some additional interpolation and client-side prediction due to missing snapshots.

Cool, i didnt know that, i always figured it had a small timer from when a packet was sent (small green bar) and when a packet recieved and calculated the height on that, but snapshots make more sense in a way.

Thanks.