ex_interp .01

[lockEm]

I dunnnnooooooo

[Phonetically Phamous (dice]

[torankusu]

NoDice said:

LOL.

 

I think Dice wins the argument.

[newrayz]

NoDice said:

 

micheal and dice

 

 

both saints in my book.

[Kuros]

I lied, rates are at 33. That means interp should be .030

[xenocide]

Ok I thought I was beginning to understand, but now I’m confused again. If you’re saying what lockem’s rates and interp should be, given that you know nothing about his system, location, etc., then how is that any different from forcing everyones’ client to uniform values??

[Kuros]

xenocide said:

Ok I thought I was beginning to understand, but now I’m confused again. If you’re saying what lockem’s rates and interp should be, given that you know nothing about his system, location, etc., then how is that any different from forcing everyones’ client to uniform values??

 

I didn’t know the max rates had been set so low. If you can’t talk to wcu at an updaterate of 33 then you really need to find a new ISP/server to play on.

[xenocide]

As far as I can tell, your message had nothing to do with my post =(

[Dankst@]

i just asked how it worked, i didnt mean to start a debate war

[Kuros]

In a nutshell here are the cvars and an overall idea of what they do: (client)

 

cl_cmdrate: number of times per second that you send updates TO the server

rate: max bytes per second FROM the server (usually you get about 3.xx kbps)

cl_rate: bytes per second that you want to try to send TO the server (set it up based on your upload speed, higher for campus internet and lower if you’re like me an on a cable modem…I myself typicall send at 1.xx kbps)

cl_updaterate: number of times per second that you attempt to receive updates FROM the server (more on this cvar later)

ex_interp: number of times per second that your client guess ALL POSSIBLE locations based on a history buffer.

 

Ok now for the big controversy. Because update rate is how many times per second you get updates from the server and interp is based on a history buffer INTERP IS DIRECTLY RELATED TO YOUR CL_UPDATERATE SETTING. By default, CS does not take your updaterate into consideration (the dumbest part of an otherwise really intelligent piece of netcode) and sets your ex_interp setting to .1 (you have a built in lag of 100 ms that is accounted for by the server). Setting your interp too low such as .01 as indicated in this thread is BAD. Why? Because you are actually interping MORE THAN DEFAULT!!!! Why is that? Well, we are only updating on WCUs default max value of 33 times per second which has a lowest possible interp rate of .030. Because you are forcing your client to guess less but are not receiving enough updates to fill in the gaps, you are not seeing what is actually going on in the server. That’s all theoretical however. CS won’t let you try to interp less than it can send you data so it automatically bumps you up to .030 (assuming you are using the cl_updaterate of 33). Here’s where things CAN get messy though. If you set your updaterate to 101 or 100 (which most people here do thinking that it helps them) you are actually hurting yourself quite a bit. Why? Well you are attempting to receive more packets than the server is actually sending you. Your client then drops the 66 update packets per second that it is not receiving and attempts to draw objects based on the history buffer (which is bad, any time you draw something based on where it was and not where it is means that reg is going to suck). So, you want to set your value to the max setting that the server can actually send. You don’t have rcon so you have to go by what I tell you (because I do have access to what the max rate settings are). How do you do it on another server where they don’t tell you the rates? Maybe they update at 66 (like we should)? Here’s the guide for you:

 

http://www.gotfrag.com/cs/story/30057/?spage=3

 

Further reading on goldsource netcode:

 

http://www.overclock.net/pc-games/513495-i…ke-1-6-net.html

 

Enjoy.

[xenocide]

thanks =)

[Author]

Posts