November 22 2024 04:58:31
Navigation
· Home
· Discussion Forum
· Downloads
· 3v3 Hall of Fame
· Web Links
· SourceBans
· gameME
· Servers

· Steam Group
· MOTD
· Search
· Contact Us
Forum Threads
Newest Threads
· Something Fishy
· What happens when a ...
· gameME Stats Hosting...
· гипер козлÐ...
· Multi-hacker - car d...
Hottest Threads
· Something Fishy [6]
Donate

Current Donation Stats

Nov's Goal: $100.00
Due Date: Nov 30
Amount in: $25.00
Balance: $23.17
Left to go: $76.83


Click here to expand donation informationCurrent Donations
View Thread
DoGz Gaming Clan » Public Forums » Public Chat
 Print Thread
A small guide on cl_interp and how it influences your aim/hit detection
terrowrist
http://dl.dropbox...nterp.html

"Don't ever change interp with the cl_interp command. cl_interp should always be on 0, instead, you change the interp using the cl_interp_ratio command. IMO, cl_interp is an ancient command that should be removed and completely replaced with cl_interp_ratio.

Only use whole numbers with cl_interp_ratio; it's simply unnecessary to use values like 1.2, because all it does is adding useless interpolation time. I especially don't understand why you would use this in combination with a 120hz monitor; that combination seems a bit irrelevant.

Instead, use cl_interp_ratio 1 if you have little to no packet loss (check this with net_graph 3), cl_interp_ratio 2 if you have regular packet loss, and cl_interp_ratio 3 if you have a fairly big amount of packet loss.

You can also reduce cl_updaterate and cl_cmdrate if you experience packet loss or packet choke, respectively. Although I'd prefer to increase interp before resorting to reducing rates."

Source: Reddit
"Nobody really knows what they're doing. We're all just trying to figure out what makes us happy."
 
Jump to Forum:
Powered by PHP-Fusion copyright 2002 - 2008 by Nick Jones.
Released as free software without warranties under GNU Affero GPL v3.