Well seems i am running more and more into people with a reallly low cl_updaterate (having a ping of <50 and lagging as hell are usually good signs).

I started a small project with the release of 3.0.
Entering a server, taking a demo and then using demofreak to read out the clients net-setting. A whole 7.2% of all tested clients have used a cl_updaterate less or equal to 15. This caused major lagging of said clients, making them hard to hit.
Wether they did it on purpose (default setting is 20) or witheout knowing the effects it disturbed gamplay and many players complained about warping skulks etc.

I would like to see this problem solved.
The default for sv_maxupdaterate is 30, the matching cl_updaterate equals the sv_maxupdaterate. The problem is that although most servers are using 30 there are servers that dont use the default values. This is why i would like to see the following:

uh huh. And what about those people who need it set to 20 or less? I'm on 56k and get the least choke/loss with 18. Any higher I get huge lag. 35 would be completely unplayable.

I can clearly see your point.
And thanks to your net setting you dont lag from your point of view. But other clients will have issues with you warping through hallways etc.

Maybe some kind of rate taste could be hard-coded. Once you join a server, your max. rate is tested and your rates set accordingly. I dont want to screw those on 56k, i am just a little bit angry about players with mean net setting who are telling me, that their new cable is the pwn

I'm all for allowing servers to keep netcode values between certain ranges, but forcing values to exact numbers or having really small ranges will just screw 56Kers. So, we should just let the server ops set a maximum and a minimum value for certain variables.

Well the general problem is that people who are using sv_updaterate 101 and ex_interp 0 dont have the right net settings they would need for sv_maxupdaterate 30.

This is why i want server and client to synchronize. On a small sidenote using higher values for ex_interp than 1/cl_updaterate is considered an exploit by quite a number of leagues.

Just give the players an option to either read out sv_maxupdaterate or a small box in their options menu: Something like: "Auto-adjust network settings" if checked, it would have the effects described in my first post.

/support

cl_updaterate 10

There isn't even a decent plugin solution for this. Clientexec still requires you to randomly adjust suspect's rates, which is obviously no good as an admin independant solution.

On another note:
Have a look at the latest steam survey.

Only 1.74% are using 56k opposed to 7.2% using net settings, that would match 56k.

I have been continuing my project and the numbers have risen from 4.8% to 5.9%
of all tested clients with a cl_updaterate equal or lower than 15.

It's what cl_cmdrate the client is using that will affect if he warps or not.

New update on the numbers:

The last 3 days did not went well (rate wise): A whole 23,8% of all newly tested clients had used a cl_updaterate equal or less 15. This makes an overall of 7,2%.

Something seems to be wrong with the last few days.... my worst test was 6 out of 10 clients using cl_updaterate 15 and 1 using 10

Has anyone any information about a new "how to hax my rates" tutorial, that was released within the last week?

Correction:
cl_updaterate xx

Specifes how many packets per second you receive from the server.

cl_cmdrate xx

Specifies how many packets per second you send to the server

If you send 10 packets/second to the server. Your model will "teleport" and
you will appear extra jerky. By setting ex_interp 0 you can see who uses this
exploitive setting. Its very exploitive. They will update on your screen 10 times per second. Ever try playing at 10fps? It gives the player a huge advantage. Server admins should be advised to fix their rates. Most servers do not enforce any minimum rates and about 25% - 30% of the ppl use low exploitive rates. When you are an alien with celerity, you become very hard to hit. Im considering quitting ns over this, since barely any admins recognize this problem.
For every server I would recommend these settings:
sv_minrate 5000
sv_maxrate 15000
sv_minupdaterat 25.0
sv_maxupdaterate 80.0

Admins should play with ex_interp 0. It turns of smoothing and you will see who is using lower than desired rates (they appear VERY jerky). Warn/Kick/Ban.
I just played on the I-AM clan server, and they have no min rates, nor do the admins care. But it throws off the balance of the game totally. I myself have tried playing with low rates. Without trying you can easily become #1 on your team. Its just not fair. I would even accept if it these rates were hardcoded to:
cl_cmdrate 30
cl_updaterate 40
rate 10000

Until this is resolved, the Rateenforce metamod plugin by David "Twitch" vonThenen was designed for league play and

great survey your doing.

i like your idea about sync clients +servers, its a good idea.

but I worry about 56kers, i had it for years, i know how much of a pain in the arse it is, but luckily i got broadband now .

id even be happy with the default settings to be changed, since the sv_maxupdaterate is 30, the default cl_updaterate should be 30 aswell, 56kers would just have to adjust there settings then.

56kers wont have a good game feel either way, and most ppl have dsl or broadband.
I think satisfying the majority should be thought. Syncinc with the server is an excellent idea, and which is something I try to do if, I know the servers setup.
56k-ers are not welcome on many counter strike servers. I dont like them much eaither. They teleport a lot. But it was common 4 years ago. Now, they are a pretty much eliminated breed. By natural selection, the stronger dsl / broadband users survived .

They wouldnt be shut down or disadvantaged much more than they are, but it would stop ppl exploiting.