[...] why?

[...] Not really, although you may not want to disable prediction error smoothing (cl_smooth).

[...] when setting the rate to your suggested numbers, should I edit any other of the given commands? cl_cmdrate 66 cl_interp 0 cl_interp_ratio 1 cl_lagcompensation 1 cl_pred_optimize 2 cl_smooth 0 cl_smoothtime 0.01 cl_updaterate 66

With the connection you have you can just put rate to its maximum - 1048576. 1048576*8 = 8388608 bits/s = 8388,608 kbit/s = 8,388608 Mbit/s. This matches a 8 Mbit/s connection. 80000 would match a 640 kbit/s connection.

Ok, so to put it simple: Will i benefit of a rate higher than 60000 with my connection ?

[...] So theoretically, if i have a 6 Mbit/s connection i should be running a higher rate than the 60000 suggested in chris' cfg ? Also, can someone explain what the rate actually does ? As far as i understood it determines how often server and client "communicate" with each other ?

...80000 would match a 640 kbit/s connection.

[...] Yup

[...] pro>pub>default?

[...] Ping has *nothing* to do with rates. S This is basically chris' settings wrapped in some aliases alias net_pro "cl_updaterate 66; cl_cmdrate 66; cl_interp 0; cl_interp_ratio 1" alias net_pub "cl_updaterate 40; cl_cmdrate 40; cl_interp 0; cl_interp_ratio 2" alias net_default "cl_updaterate 20; cl_cmdrate 30; cl_interp 0.1; cl_interp_ratio 2" net_pro net_graph 3 rate 80000 Rate server quality with the net graph and adjust your settings accordingly. Get choke? Use lower settings. Get loss? Fix your connection.

nonono. I had just woken up when I typed that. What I meant was - which of the pregiven rates that are in chris` maxframes cfg should I be using with pings like these?