GVME
 
Remove ads!
Rating
Based on GVME Community!
Your rating: N/A
Total votes: 0

You cannot rating yet!
You can rate anything - when you add rating to a submission your vote determines its success or failure.

To vote on this submission
register or login

You cannot add to Favorites!
You must register or login

You cannot say thanks!
You must register or login

Details
More informations about this submission!
Development Informations
No details were entered

Statistics
Scores and popularity
Views: 30
Downloads: 0
Feedback: 0

Which netsettings are right for my connection?

Share:
Added by: Diablo
Category: Counter-Strike > Client
Tags: net connection settings
Author's Readme/Notes
This question is not so easy to answer, since the right netsettings depend on 4 factors:

  • Own internet connection
  • Own bandwidth
  • PC performance
  • Slots (or players) on the server

As a rule of thumb:
rate = own download
bandwidth in bytes (max. 25000) cl_rate = own upload bandwidth in bytes (max. 20000, but default 9999 is sufficient.)
Fps_max = a value that the PC can keep stable (max. 100)
cl_cmdrate = As high as fps_max, but not higher than cl_rate / packet size Out
cl_updaterate = max. 100, but not higher than rate / package size In
cl_cmdbackup = 0-1 (increase only with loss in the net_graph)
ex_interp = 0 (0 calculates the value automatically)
ex_extrapmax = 1.2 (Please do not change the default value . Raise ex_interp for jerky models)

You can find more information on the exact calculation in this FAQ.



Here I would like to suggest some netsettings for typical connections and typical servers.

DSL (all bandwidths, with and without FP, 100 FPS stable, game server up to 12 slots)
CODE
rate "25000"
cl_rate "9999"
fps_max "100"
cl_cmdrate "100"
cl_cmdbackup "0" // Increase to 1-2 at loss.
cl_updaterate "100"
ex_interp "0"


Except for the cl_updaterate value, all other values ​​remain the same on every server.
In the case of servers with more players, lower the value cl_updaterate so that in the Netgraph (during the battle) little (<10) or no choke is displayed.
ISDN with channel bundling (100 FPS stable, game server up to 12 slots)
CODE
rate "16000"
cl_rate "9999"
fps_max "100"
cl_cmdrate "100"
cl_cmdbackup "0" // Increase to 1-2 if there is a loss.
cl_updaterate "75"
ex_interp "0"


Except for the cl_updaterate value, all other values ​​remain the same on every server.
In the case of servers with more players, lower the value cl_updaterate so that in the Netgraph (during the battle) little (<10) or no choke is displayed.
ISDN (100 FPS stable, game server up to 12 slots)
CODE
rate "8000"
cl_rate "8000"
fps_max "100"
cl_cmdrate "100"
cl_cmdbackup "0" // Increase to 1-2 in case of loss.
cl_updaterate "40"
ex_interp "0"


Except for the cl_updaterate value, all other values ​​remain the same on every server.
In the case of servers with more players, lower the value cl_updaterate so that in the Netgraph (during the battle) little (<10) or no choke is displayed. If the server does not allow a lower cl_updaterate, simply increase ex_interp to avoid lying models.
Analog modem 56k (100 FPS stable, game server up to 12 slots)
CODE
rate "7000"
cl_rate "4300"
fps_max "99"
cl_cmdrate "33.3"
cl_cmdbackup "2" // Increase further on loss.
cl_updaterate "20"
ex_interp "0"

Choke will inevitably occur on servers with more slots. A reduction in the cl_updaterate is usually not possible. Raise the calculated value of ex_interp (0.05) to 0.1 to avoid lying models.
Added: 2 weeks ago
Modified: Never edited!
  Thanks List: [+]  
 
 
Add Feedback

You cannot post yet!
Get involved on GVME by posting your thoughts. Give authors your feedback to help them develop.

To post in this submission register or login
Feedback