Hey guys, I was trying to figure out how to improve the ingame experience. I mean that I wanted to solve little lag problems and things like that, because I noticed that I was a bit "late" compared to other players. Panda gave these few commands: cl_cmdrate "40" cl_interp "0.025" // Change to 0.0375 for hitscan cl_interp_ratio "1" cl_lagcompensation "1" cl_pred_optimize "2" cl_smooth "0" cl_smoothtime "0.01" cl_updaterate "40" rate "35000" Now I'm trying them out to see if it works or not. I noticed that ingame I now have an orange lerp. Some people say that yellow lerp sucks but that orange lerp could be good, others tell that both yellow and orange suck. Who's right ? If some of you have some tips or whatever, feel free to talk about it ^^
rate 45000 cl_cmdrate 67 cl_updaterate 67 cl_interp "0.034" // for rocket launcher or other projectile weaps: "0.0152" cl_interp_ratio 2 cl_smooth 1 cl_smoothtime "0.068" smoothstairs 1 cl_predict "1.0" cl_pred_optimize 2 cl_lagcompensation 1 Rate: packet fragmentation goes up above 50K on "rate", its known that ppl with higher rate than that cause lag on the server. Yes, EVEN if the server has set sv_maxrate "50000". on a busy server, a "update" is often no more then 600 bytes. cl_cmdrate = cl_updaterate: all TF2 server run 66 tick, its hardcoded a fixed tickrate, only some hacks make it higher, I didn't encounter such servers yet. The values need to be equal or very close. If having cl_updatrate 20 and cl_cmdrate 66 for example, that player is as I call it "ratehacking" its ban-worthy, and there groups out there that ban for it, cos it makes them near impossible to hit. There is even a plugin to check for that cl_interp = cl_interp_ratio / [tickrate or cl_updaterate, whichever is LOWER] its the time to wait for the next required update defined in the frame of cl_interp_ratio. if thats 2, this time must be enough to recieve both updates within that frame. Given value is a correct value to use with the other values. cl_interp_ratio: 1.0, 1.5 or 2.0. can be restricted by server basically its the number of updates that is used to interpolate the next "frame" on the screen, the higher the better the interpolation. cl_smooth: smoothing of other players, if disabled this can lower your feeling of a smooth gameplay, people will be "lagging and teleport a bit. cl_smoothtime "0.068" time in which the smoothing must take place, double of the cl_interp. smoothstairs: eye smoothing if going of or on stairs.... cl_predict: perform client side predction on, please leave on, for your own sake. cl_pred_optimize: mode in which the optimization takes place. cl_lagcompensation: leave on for your own hitreg, or you will not lagcompensate, but the server will. Some ppl will add a "+" in their rates, which has as result their ping will be below 10, to fake the pingkicker, and to ratehack cos on the server it will lag them out vs other players. Bannable offence, same as with the overly high rates. As far as I know, LZ has no rules regarding this and is by no means enforcing them, but those are generally accepted rules around.
Yeah but those parameters are for good connexion I think, no ? (I m supposed to have a good connexion if you look at the polish speedtest in my signature x) ). Maybe I'm a bit far from the server but I'm sometimes feel laggy :s A few days ago I had cl_updaterate 66 cl_cmdrate 66 rate 60000 cl_interp 0.01 (or something like that) cl_interp_ratio 2 cl_smooth 1 cl_smoothtime 0.1 but didnt seem to be well optimized
The LZ CSS ones or all the CSS ones? I remember having a smoother experience on CSS with 101 instead of 67.
The CSS ones. Every single ad you see to rent CSS servers says 100 tickrate and things like that. Didnt think there were lower tickrates for CSS ;p. Some people like Chris or maybe M0re, didnt remember that having an orange lerp couldn't have a negative impact on your gaming experience. So, I'm still wondering
There are only a few TF2 servers that run more than 66 tickrate.So having cmdrate 101 and updaterate 101 is pointless. afaik there are more CSS servers with tickrate 100. It runs slightly better but it's not really worth the extra money. If you think that cmdrate 101 and updaterate 101 run better for you in TF2, you're fooling yourself - the engine freezes the values to the max tickrate (66).