[crilleaz]

Okay i've tryed most of theese sv_maxrates and min rates and all those things, nothing seems to work... Been getting my rates at: http://www.reece-eu.net/drekrates.php but they aint working..

heres some specs:
Windows XP Pro 2002, sp3
AMD Athlon(tm) 64 Processor 3200+
2.01 GHz and 1.25GB ram

I want to run a 66tick server, with 16 players because i think thats what my computer can handle, (Im not playing on that computer, only for hosting)

been trying:
// bandwidth rates/settings
sv_minrate 13000
sv_maxrate 25000
sv_minupdaterate 33
sv_maxupdaterate 67
sv_mincmdrate 33
sv_maxcmdrate 67
sv_client_cmdrate_difference 1
sv_client_predict 1
sv_client_interpolate 1
sv_client_min_interp_ratio -1
sv_client_max_interp_ratio -1
-
my players got freeze about 2~3 times\min
so i calculated some:
sv_minrate 5000
sv_maxrate 125000
sv_minupdaterate 10
sv_maxupdaterate 400
the above rates i put 40mb download speed, thats why 125k at maxrate, theese rates are working well, but not that great.. they don't get freeze's as often now, but they are still lurking there.

heres a network spec:

download: 65mb
upload: 2.60.

here's my startup:
"C:\HLServer\Css servers\Server 1\orangebox\srcds.exe" -console -game cstrike +map ba_jail_electric_razor_v6 +maxplayers 16 -port 27015 -tickrate 66 fps_max 250

Ah, yes im using Datavirus's jailbreak plugin.

If you need ANY more information, please tell me, because i really need help!

[Bacardi]

2.60 Mega bits per second
2600 Kilo bits per second / 8 = 325 Kilo Bytes per second

325 KBps / 16 player = 20,3125 KBps to each player

sv_maxrate 20300

*edit
Small upload bandwidth and too many players give that lag, and small rate.
You maybe need "drop" player slots, or get better net

325 KBps / 30K(rate) = 10 players

*edit
try set lower sv_maxrate... Maybe 20000.

[meecrob]

The fact that you are using Windows XP could be part of your problem. This operating system does not have kernal timing optimization as Windows Server 2003/2008 or Linux distributions have. By default you will only get 64 fps with the server. You can start windows media player in the background which will boost your fps to 256, but I would highly suggest changing OS's.

[meecrob]

Here are the settings I would recommend.

sv_minrate 50000
sv_maxrate 0
sv_minupdaterate 33
sv_maxupdaterate 67
sv_mincmdrate 33
sv_maxcmdrate 67
sv_client_cmdrate_difference 1
sv_client_predict 1
sv_client_interpolate 1
sv_client_min_interp_ratio -1
sv_client_max_interp_ratio -1
fps_max 300

The fps_max setting is a little weird, if you set it to 250 you will not get 250 fps, but if you set it to 300 you will get 256. Again this is affected by your OS and by default, you will only get 64 with Windows XP.

Your connection is fast enough that I would set the minrate to 50000 and maxrate to 0 (unlimited). Setting this lower will result in your players seeing Choke.

[NoS]

Originally Posted by meecrob The fact that you are using Windows XP could be part of your problem. This operating system does not have kernal timing optimization as Windows Server 2003/2008 or Linux distributions have. By default you will only get 64 fps with the server. You can start windows media player in the background which will boost your fps to 256, but I would highly suggest changing OS's.

2003 and 2008 also run at 64 fps by default. Running an FPS booster solves that. Linux is the only one without that problem I believe.

Originally Posted by meecrob Here are the settings I would recommend. sv_minrate 50000 sv_maxrate 0 sv_minupdaterate 33 sv_maxupdaterate 67 sv_mincmdrate 33 sv_maxcmdrate 67 sv_client_cmdrate_difference 1 sv_client_predict 1 sv_client_interpolate 1 sv_client_min_interp_ratio -1 sv_client_max_interp_ratio -1 fps_max 300 The fps_max setting is a little weird, if you set it to 250 you will not get 250 fps, but if you set it to 300 you will get 256. Again this is affected by your OS and by default, you will only get 64 with Windows XP. Your connection is fast enough that I would set the minrate to 50000 and maxrate to 0 (unlimited). Setting this lower will result in your players seeing Choke.

Do not use a 50000 min rate, that is completely pointless and a waste of bandwidth.

sv_minrate 0
sv_maxrate 20000

I know someone will argue with me regarding minrate settings, but it saves a lot of bandwidth, and reduces your upload amount significantly.

[Bacardi]

Originally Posted by NoS sv_minrate 0 sv_maxrate 20000 I know someone will argue with me regarding minrate settings, but it saves a lot of bandwidth, and reduces your upload amount significantly.

Even set sv_minrate 0 or 1
Server still restrict clients rate to 1000

] rate 0
] rate 
"rate" = "1000" ( def. "10000" )
** NOTE: The real value is 0.000 but the server has temporarily restricted it to 1000.000 **
 - Max bytes/sec the host can receive data

[NoS]

Originally Posted by Bacardi Even set sv_minrate 0 or 1 Server still restrict clients rate to 1000 ] rate 0 ] rate "rate" = "1000" ( def. "10000" ) ** NOTE: The real value is 0.000 but the server has temporarily restricted it to 1000.000 ** - Max bytes/sec the host can receive data

True, but the only reason I set it to 0 is to leave the min rate uncapped. If you set the min rate to something like 20000, all the clients will be forced to use 20000 bytes, if you allow whatever, then you use less bandwidth.

[meecrob]

Setting the minrate to 0 or 1 will cause issues with clients receiveing "Choke". Choke happens when the server has an update that it can send to the client, but doesnt because the server thinks that there is not enough bandwidth to do so. Setting this higher will resolve that issue which would be presented as lag to your players.

Setting this too high can also cause issues with players "timing out". I'm on a 10 mbps uplink and rarely use more than 4 mbps with 56 connected players.

Perhaps the best thing you can do is use "net_graph 4" and experiment with settings until you find a happy medium. This graph will show you your client rates and the rates the server is producing.