Using these settings, I almost never get choke on any server. rate 25000 cl_cmdrate set to the same as your FPS cl_updaterate 20-101 depending on server...if you see choke drop to default and work up till choke starts to show up again
----- Original Message ----- From: "[Mage]-BadPing-" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, October 12, 2003 8:45 PM Subject: Re: -pingboost 3 and low sys_ticrate RE: [hlds_linux] Re: The best OS for the server debian/freebsd > /quote Britt Priddy (PZGN)/end quote > > When I use pingboost 1 or pingboost 3 on a P4 1.7ghz - 1gig ddram - I see > > alot of choke - > > For me choke was almost all client-side. If you make changes on the fly > in game you can really see dramatic changes in connection quality by > messing with the various settings, especially with net_graph 2 enabled. > I'm on cable and these setting result in the minumum choke for me: > > fps_max "90" > cl_updaterate "180" > cl_cmdrate "90" > rate 10000 > > Those settings give me 0 choke when nothing is going on and maybe as much > as 5 or 10 in a really bad firefight. > > For me the easiest to read netgraph settings are: > > net_graphpos "2" > net_graph "2" > > > YMMV. This is defintely not to say that server settings don't affect > choke, but it does help in diagnosing where the choke is coming from. > > -BP > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
