PDA

View Full Version : High Pings


P.I.M.P
11-21-2003, 02:51 PM
I host a server and I don't want anyone with a ping higher than 200 to connect. I set the maxping setting to 200. Some people will connect to the server, but once they start playing their ping will jump to 300. When I do a whois, I find that these people are from Europe or other countries. Local people from the US can connect fine and have a ping of around 50 when playing on my server. Is there another way I can filter out high pings? Thanks in advance. :atat: :jawa

PG|Prometheus
11-21-2003, 03:04 PM
Why not let them stay? And surely they'll leave if they have a 300 ping anyway...
However, those that ping around 50 in europe have about a 120 ping for east coast US...so I doubt its the players, perhaps your server.

Amidala from Chop Shop
11-21-2003, 06:37 PM
sv_maxping blocks players with challenge pings higher than that number from connecting. Pings fluctuate. If at the moment they try to connect their ping is lower than sv_maxping, 200 in your case, they can connect. Once they are in, sv_maxping has no effect. So if the players you want have pings in the 50 range, set sv_maxping lower than you have it, maybe 150.

It is a double-edged sword however. Remember I said pings fluctuate. If a player who normally has a ping of 50 happens to have a ping of 151 when she tries to connect, she will get the "Server for low pings only" message and won't be able to enter. She will have to keep trying until she can challenge ping at 150 or less.

Rad Blackrose
11-21-2003, 07:02 PM
Pings fluctuate.

Just for reinstatement purposes.

If you have ever used ASE, they give two columns to determine in game latency: Ping, and flux. Ping is what you would normally have granted no flux is present. Flux, on the other hand, is the factor it would have on your ping. Flux could be a number of things: server power, bandwidth, if one box is running two servers (especially if it's siege, look for statement we got from the IDS siege provider below), etc.

People have a misconception that people with high ping will cause others to lag out. While there is the occasional flood, it doesn't occur in a general sense. I had to deal with it in Counter-Strike when I was still playing on a 56k.

EDIT: Whoops, forgot the statement!

We have learned that there is a deficiency in the Siege game with certain Siege maps. In some cases, changing to one or two particular Siege maps while in Siege mode can lag the whole box, and all the servers on it. So while you may not be playing a Siege, someone else may.

That's the problem. We don't quite have a solution yet; we're not quite sure there is a solution just yet, as it's a problem with JKA itself.

We hope to put out an announcement soon asking customers not to use Siege so much. In the meantime, we're investigating other options.

Thanks for your continued patience!


-Name removed

PG|Prometheus
11-21-2003, 07:42 PM
May I say, thats the worse solution I've ever heard.
Er...our product isn't working properly...so...er, dont use it as much.
They should just try to fix it, but telling people not to play is just stupid.

Rad Blackrose
11-21-2003, 07:51 PM
Originally posted by PG|Prometheus
May I say, thats the worse solution I've ever heard.
Er...our product isn't working properly...so...er, dont use it as much.
They should just try to fix it, but telling people not to play is just stupid.

It's JA, not the server's fault. I believe we also leased the JKII server from them, and we never had a problem there.

Amidala from Chop Shop
11-21-2003, 08:46 PM
I continue to lease two JK2 servers from that same provider, as I have for many months, and lag problems are extremely rare with the JK2 servers.

The JA servers are another matter. I had two JA servers, and one of them would have one or more lag waves (they last too long to be called "lag spikes") nearly every day that sent pings >500 for minutes at a time. Sometimes the pings would hit 999 and the server stopped responding to rcon until the lag wave passed. If I saw it happening I changed the map (which didn't always help) or even restarted the server (if I could get it to accept a rcon /quit command). It doesn't happen as frequently with the second server. I suspect they are on different boxes, and the first server's box had more Siege servers running on it.

This was very distressing to me because the players would blame the last person who joined for the lag, or would accuse me of running a server on a 56k modem, or of not knowing how to run a server, or of downloading porn (!).

I shut down that first server and moved it to a new host who will not allow people to run Siege servers until and if a cure for Siege server-induced lag is found. I will keep the second server with my original host for now, but I will move it or shut it down as well if the lag waves continue.

Chuahtemoc
11-21-2003, 08:49 PM
That piece about the siege mode makes sense ( i know from experience :mad: ) because alot of siege end up being around five to fifteen people from either team converging on a single door or a single area, and it's sickeningly taxing on both individual comp memories and on the servers. I mean, having 30 people in one room, all blasting eachother at once, (15 trying to destroy something and 15 trying to protect it) has got to be damaging to the server.

PG|Prometheus
11-21-2003, 10:40 PM
Even so, I dont think discouraging seige servers is the answer to the problem.

rofl running a server on a 56k. Damn I bet that would be fun lol!

Chuahtemoc
11-21-2003, 11:26 PM
Originally posted by PG|Prometheus
Even so, I dont think discouraging seige servers is the answer to the problem.

:D lol not even what i had in mind, i love siege :rofl: 56k servers litter the sof2 boards, which sucks, but i'll own anybody there regardless :P

StormHammer
11-22-2003, 06:20 AM
Thanks for the info, Rad and Amidala. I have to say I was one of those who thought someone joining with a high ping was lagging the Siege servers I've been on...but this seems not to be the case. If there are a few Siege games running simultaneously on a server box, no wonder it impacts performance.

It's unfortunate that there is a problem with Siege mode itself that is causing this problem. I can only make reference once more to Wolfenstein: Enemy Territory. I've played that game on servers with 60 people (30 per side usually), and experienced 'acceptable' or very little lag. Some people have connection time-outs - but it usually doesn't impact other players. Trust me when I say there can be a lot of action on the screen at once in ET, and yet for the most part the game runs smoothly. It too uses the Q3 engine.

So it seems to me that Siege mode in particular needs to be revised in some way, or the netcode improved.

As for the original point raised in this thread...if you're just running FFA etc., I don't see much of a problem allowing people with higher pings to join the server. I can usually cope with high pings when I join US servers, and other players can cope with me. If you're running Duel mode, that's a different matter. High pings can kill enjoyment of that game mode - seeing your opponent jump from one part of the map to another, and then finding yourself dead without even seeing the attacking move is no fun at all.

Amidala from Chop Shop
11-22-2003, 07:28 AM
It's nice if there isn't too big a spread between the high-pingers and the low pingers for fairness sake ("ping is king"). Not only are the high-pingers at a disadvantage compared to LPBs (Low Ping Bastards), they tend to whine "laaag!" all the time, and you know I hate any kind of whining.

I vary sv_maxping throughout the day. My default value is 300. Remember, one more time, pings fluctuate. Someone with an average ping of 120 might temporarily be pinging at 201 for a few seconds, right when they are trying to connect to your sv_maxping 200 server, and they won't get in. When a server is getting full, I start reducing sv_maxping because there are usually a lot of low-pingers already playing, and if a lot of people are trying to get into the server I can be selective (like the bouncer at the velvet rope in front of the hot club) so there are only low-pingers inside with a small range between low and high pings. That is good for everybody because it's fairer and no one is teleporting around or whining about "lag". On weekends or when school is out and the servers are busy, I've reduced sv_maxping as low as 150.

On slow days, or especially late at night\early morning after North Americans have gone to bed but foreigners are still playing, I increase sv_maxping to 500 so it's easier to get in, but it still blocks the ridiculously high pingers. One of the things I like to do in the early morning hours is run a geographical traceroute on my players and see where they live. Then I'll sometimes psay all a message (so it appears in large type to all players like the ones that say "so and so has entered the battle) like "Welcome, Darth Bane from Seoul, Korea!" or "Welcome, Master Yoda from Madrid, Spain!" I've had people from all over North America, Brazil, Argentina, UK, Finland, Denmark, Poland, Germany, Austria, Czech Republic, Spain, Italy, Hungary, Australia, New Zealand, Korea, Hong Kong, Singapore, and others I can't remember right now.

My servers are my own little United Nations where people from around the world can gather to promote mutual understanding and world peace by shooting, exploding, choking, decapitating, and throwing each other to their doom, all for fun.