<?xml version="1.0" ?><rss version="2.0">
    <channel>
	<title>ETF2L &#8211; Latest activity in &#8220;New to Source Netcode!&#8221;</title>
	<link>https://staging.etf2l.org/forum/general/topic-402/</link>
	<description><![CDATA[The latest posts to this topic.]]></description>
    	<item>
    	    <title>Reply by AnAkIn_</title>
    	    <link>https://staging.etf2l.org/forum/general/topic-402/page-1/?recent=2395#post=2395</link>
    	    <description><![CDATA[If you have lot of choke then you have a bad connection.

For a good connection, the settings would be:
cl_updaterate 66
cl_cmdrate 66
rate 30000
cl_interp_ratio 1
cl_interp 0.0152

Maximum updaterate/cmdrate are 66 because server's tickrate is locked to 66 in TF2.

cl_interp_ratio/cl_updaterate= minimum cl_interp

If you get a lot of choke (more than 10-15), then you should reduce your cl_updaterate.

Your interp will automatically adjust when you lower your cl_updaterate.

If you get laggy player models, this means that your update rate is dropping (example for cl_updaterate 66, your update rate is dropping to 40 or less, you can see it in net_graph). What you can do is higher your interp, just put cl_interp_ratio to 1.5 and it'll higher cl_interp (shouldn't affect much shoot registry).]]></description>
    	    <guid isPermaLink="false">generator=rsdiscuss&#038;baseurl=https://staging.etf2l.org&#038;feed=forum&#038;forum=general&#038;topic=402&#038;post=2395</guid>
    	    <pubDate>Wed, 09 Jul 2008 13:47:55 +0200</pubDate>
    	</item>
    </channel>
</rss>