I guess it's time to explain this for one last time.First of all, Interp does close to nothing. It used to, back in 2004ish but Valve fixed it in an update. ex_interp is a client side command, meaning EVERYTHING about it has to do with the client. So the delay you see is only client side. In other words, all those "interp shots" you see are shots ... YOU SEE, they don't really happen in the server. Let me explain what interp is first. All ex_interp is a interval for a "prediction" done by the client between 2 packets received from the server. For instance, setting ex_interp to 0.1 makes the client predict quite a bit, as opposed to 0.01 where the client predicts ten times as less. So in a nutshell, 0.1 makes more client side predictions resulting in smoother models with less accuracy and 0.01 makes less client side predictions resulting in not so smooth models with more accuracy. Now say you experience packet loss or other inconsistencies between packets, if that happens the client makes predictions of player positions that are not necessarily correct. These are the "interp shots" everyone complains about. But if you read and understood what I wrote before, the concept of an interp shot doesn't make sense. Well, that's because "interp shots" are not what you think they are (these days they are mainly used as excuses when you are getting owned.)Let me put these alleged interp shots into two different situations.Situation 1Say you are using 0.1 and you score a headshot by shooting absolutely nowhere near a head (kinda like in those videos.) Well, that's an example of the client making a false prediction of a player position; the actual player position was where you aimed and shot, but the client showed you a false position. However, the server registered your shot as a headshot because you shot at the actual position of the head. This could be considered as an interp shot.Situation 2You die behind cover AFTER you peeked into cover, but you are certain you didn't get spammed. This is an example of a delayed shot and it has nothing to do with interp. This may have been caused due to a plethora of issues. Namely you having bad rates, them having bad rates, packet loss, choke, and other server/client side connection problems. These are NOT interp shots.oh and one more question to answer, the question I have been asked on Steam two billion times. Here goes the answer to legendary "whats the best interp?"0 (zero.) Why? simply because it automatically sets the ex_interp to the correct value (using the equation interp=1/updaterate.) Something else I should mention is that using ex_interp 0.1 was illegal way back in the day because it had a clear impact on gameplay. But now it is not, because since the valve update interp has little to do with anything. being said that, let me give you this final advice to all you players out there. You shouldn't really be concerned about interp and rates because they have close to no impact (no impact at all if you play LAN) on CS as long as you have a correct set of them (101/101/20000/0). There really are other things you should be concerned about like teamwork and strategies because (I think I'm able to say this) I can't think of any CS teams in SL at the moment who know what they are doing.Anyways, I hope this made some sense, and hopefully now you know what ex_interp actually does. I wrote this in sort of a time crunch so I apologize for any grammar and spellings mistakes.Have a nice day!
Nice post zhkR, you mean
how come mine is 0 .. I'v never changed it.. O_o
and u playin 0 wow man u so cool
wen u get into glk it automatically goes to 0.1 man try change that to 0.01 or make the users config decides lol and u playin 0 wow man u so cool
