On 10/13/05, Whisper <[EMAIL PROTECTED]> wrote: > -- > [ Picked text/plain from multipart/alternative ] > There appears to be a bug/exploit at the moment that allows people to set > their cl_interpolate to 0 but then set their cl_interp higher and the server > still counts the cl_interp value.
I know. > Those are the guys who keep shooting you after you have run around a corner > reloaded and then you die :) Interesting suggestion, given that I do lock cl_interpolate when I am concerned and this does not change what I describe. The stutter situation I describe actually occurs more during my kills than my deaths. No wait, it happens on both, I just have reasonable KDR most of the time ;) > Its also how people are able to AWP from T spawn on dust2 and kill with > regularity, CT's through the dbl doors as they jump across. I've been hit in this way less times than I have digits, several instances of which I know were un-cheated. > Hmm, I wonder if I've let the cat out of the bag there. Nope because I could search this mailbox for dust and AWP and see several mails at least in which you have re-iterated this problem description. Just out of curiosity, do you have binds that looks something like this: bind KEY ma_cexec_all cl_interpolate 1 bind KEY ma_cexec_all cl_interp 0.1 ;-) :-p (Quick side/end note: there are various systems that allow you to send automated rcon commands. From there you can run the above quite easily, and regularly, with a small penalty.) _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
