Setti CSS servers update
Posted 29 June 2010 - 10:40 AM
Definitely better than old version. Even Ping got down from ~50 to ~30, but I was alone on server.
Maybe some others join too today to really try this!
Posted 29 June 2010 - 10:53 AM
Posted 29 June 2010 - 02:59 PM
Posted 15 July 2010 - 06:38 PM
Yes, at Setti those settings are good. b00bs mentioned "lerp" setting which means (linear) interpolation. At Valve's wiki on networking (http://developer.val...ayer_Networking) you can search for word "lerp" for more info but it can be quite difficult to understand the point. Setting "cl_interp 0" is probably the best. "Lerp" itself is not a variable that you can change.
It might be better to have cl_cmdrate 100, cl_updaterate 100, rate 30000 if you are ever playing on 100 tick servers. Most (if not all) internet connections nowadays can handle that 30kB/s maximum input datastream. For output the practical maximum is maybe 15kB/s. It's also the maximum and not the average so even though someone's internet connection wouldn't be able to handle the maximum it is very much likely to handle 95% of the traffic. People who are still using these low-end connections should configure their settings to their liking. It's a remnant from 90's when people needed to care about what rates they were using when playing.
In CS:S it's equally good to set something like:
Game server will limit these to the server maximum anyway - setting them to 1 million or 1 billion or any other random number doesn't make a difference. In practice however this is not true because some stupid "anti-cheat" authors think that it's somehow cheating and servers which have these anti-cheat plugins installed might kick or ban you. Ignorance is a hindrance.
Posted 15 July 2010 - 11:20 PM
It's not so simple as you make it seem. What if you set cl_updaterate 0? Then it's division by zero for cl_interp, what do you get? The Source Engine is not stupid. You can't fool it easily.
cl_interp_ratio / cl_updaterate = cl_interp
1 / 66 = 0.015151
So i guess that cl_interp 0 will be fine
Even in intelligent posts such as http://www.straferig...ates-guide.html you get misinformation. He instructs people to set cl_updaterate to server maximum when in fact it's not necessary. The server will tell what the maximum is and limit it at that value. However this guy knows what he is writing about.
Your post is just random bullshit that anyone can find at internet. I don't think you understand what cl_interp_ratio is, I don't think you understand what cl_updaterate is, I don't think you understand what cl_interp is. This is for people who find this thread through Google. You need to give reason ("Justification" in the example link) why you say what you say. Otherwise it's bullshit.
99% of the stuff that you read on the internet boards is false. Only trust Whisper's wiki and Valve's wiki.
For more info read
Whisper's wiki is bit outdated on cl_interpolate and cl_interp but still good info:
90% of people who read Valve's wiki don't understand what they read. They just comprehend the generic numbers and tout them on other internet boards.
Posted 16 July 2010 - 06:34 AM
are the correct netsettings for the new css.. And if your game is laggy or choppy, you can try to add some interp for a smoother game, but thats up to you. The settings above are the optimal ones.
Posted 16 July 2010 - 12:29 PM
In June 12, 2007 update for CS:S there was this update:
Increased the maximum rate to 1 megabyteThe correct settings depend on the server that you are playing on. That is why I recommended setting rates at very high levels so the server tells what the maximum is and client obeys that.
It's fine when people ask for advice or tell others how to do something. It's just annoying to read these "30000 is the optimal" posts as if the values were some black magic.
Posted 16 July 2010 - 04:29 PM
Posted 19 July 2010 - 04:48 PM
Bad thing is that there is no difference saying the above thing or saying that rate 30000 is the optimal. There should be more reasoning for saying stuff like that. Like in http://www.straferig...ates-guide.html
increase your cl_interp value in steps of 0.01 until the lerp value in your net_graph stays white all the time (also in battle). maybe you should then add 0.01 additionally just to be sure... a too low cl_interp value is much worse then a too high one...
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users