Server Tick problem

[the_unknown]

hey everyone

 

I am having some problems with my tick, and currently using the Counter-Strike: Source config, which is the default config for TCAdmin attachment below if you want to see it.My tick rate is set to 100 for one of my servers command line:

-game cstrike -console +ip 72.44.215.109 -port 27015 -tickrate100 +maxplayers 24 +exec server.cfg +map ba_hiddens_jail

and so i added {TICKRATE} to my adverts in mani, and the server replied 34 is my current tickrate.

 

P.S i used the Override Default Command Line to change my command line

Counterstrike Source.txt

[studeggle]

If that is a true copy you typo'd your command line and that would explain a 33.

 

Guid to running a boosted CSS server.

 

1.tickrate is set by adding the -tickrate 100 (for a tickrate 100 server) in the command line start up parameters. Tickrate cannot be changed on the fly via console, HLSW or rcon, it can only be changed in the commandline and the server must be restarted for the change to take effect.

 

2.If you want your tickrate changes to have any noticeable benefit you must change a few other server variables as well as change the Windows Kernel Timer Resolution (pingboosting)

 

3.To change the Windows Kernel Timer Resolution (pingboost a server) all you need to do is run Windows Media Player. It does not need a file open, it just has be running in the background, if you do not do this, your servers fps will be limited to around 64 frames a second.

You can also use a little app that somebody wrote call srcdsfpsboost

 

4.The servers fps can be seen by issuing the stats command in console or via HLSW or via the RCON STATS if you are logged in via rcon on the server.

 

5.The server fps is regulated by the fps_max command (default is 300) which ends up producing around 256 fps in RCON STATS. Don't ask me why, I've asked Valve, but the next step up is to run your fps_max at 600 so you then get 512 fps in RCON STATS. It can be set somewhere between 512 and 600 via console or HLSW and permanently by adding the commandline parameter +fps_max 600, but if you set it at 511 or lower you will see that your FPS according to RCON STATS will still sit at 256 fps even after a map change, so you must set your fps_max higher than what you actually want, to achieve the desired affect. fps_max 512 produces strange results on ping boosted Windows based SRCDS, where as fps_max changes on Linux SRCDS is affected by many variables, such as, Kernel Version, Kernel Timer, and Hardware so the rules for fps_max that apply to Windows SRCDS has minimal relevance to Linus SRCDS. DO NOT take my word for it, test it yourself! The reason for running a high server fps, is to ensure that when a server does run a tickrate calculation, that it is using the most up to date information available.

 

6.So you have a high tickrate, your server is pingboosted and is running at high fps, none of this is of any use to your clients (the players) if you do not change your servers rates, specifically the sv_maxrate and sv_maxupdaterate variables.

 

7.sv_maxrate (default is 0, maximum = 30,000 ). I personally have found that the sv_maxrate 0 setting is detrimental to server performance (purely subjective opinion, but there you go, feel free to ignore it until your clients start complaining about stupid lag and player warping issues that don't correlate to any actual network or cpu usage or over usage issues as the case may be) then set your sv_maxrate to 20000 or if you have player numbers in excess of 20 use sv_maxrate 30,000

 

8.sv_maxupdaterate (default 60) setting must be changed to start using all this server generated data more effectively and get the data out to your players who want to run 101/101/20000/10000 cl_cmdrate/cl_updaterate/rate/cl_rate (yes I know cl_rate is defunct but some people can't be told so I humour them and leave it in) settings, thus you need to change your sv_maxupdaterate equal the tickrate. You only have to do this if you run a tickrate higher than 50. eg for tickrate 66 run sv_maxupdaterate 66 or even 100, for tickrate 100 run sv_maxupdaterate 100. If you do not do this, your clients will NEVER see the full benefit of your tickrate changes, and even then, because of server load the clients will not see the full sv_maxupdaterate or tickrate reflected in a net_graph 3. (See below for more information about net_graph 3)

 

9.Do not run tickrate higher than 100, Valve have admitted that there will be issues if you push the tickrate too high. In fact as of 09January2006 players will have problems on 100 tickrate servers, with doors that won't open and get stuck in spots that will not get them stuck on 66 tickrate servers, e.g. Crouched hard up against boxes on angles.

 

10.Make sure you have the bandwidth and CPU to cope with SRCDS running with these settings. If you don't have at least a 10Mbps Full Duplex link , you probably do not have the bandwidth to see the full benefit of following the above instructions. This is aimed at people with servers in dedicated data centres with appropriate high speed Internet connections. Most home users will not have the necessary bandwidth or hardware to take full advantage of ALL of these settings. You may though be able to increase your end users overall experience, just by pingboosting your server and increasing the tickrate and fps_max whilst leaving the sv_maxrate and sv_maxupdate rate settings low.

 

11. 24, 32 & 40 player servers should be run with a tickrate of no more than 66 and sv_maxupdaterate of 100. I've tried higher but you get strange issues for the clients if you do. Well you can if you want, but you need A LOT of CPU dedicated to a single SRCDS process.

 

12.The fps_max setting of 600 does not appear to hit the CPU as hard as other settings I have mentioned here do, your mileage may vary, but try reducing this back to default of 300 if your clients get strange lag issues and you have tried reducing the other server variables mentioned here. i.e. Change this one last! NB: Your servers fps will not exceed the kernel timer resolution, which varies depending upon what Operating System is being run and how it is setup.

 

13.For competition servers, or any server at the 18 player or less mark, then you should be able to use a tickrate of 100 and an sv_maxupdaterate of 100 successfully without any issues, so long as you have the bandwidth and CPU to cope!

 

14.For changes to take affect, the settings must be changed in the server.cfg file (except tickrate & fps_max which should be command line variables) and the server restarted, or if done via RCON, a map change must be done.

 

15.This information is for Windows Source Dedicated Server only.

 

16.This was written on the basis that your SRCDS is a default SRCDS Installation with no Mods/Plugins or Non-Standard anything else, such as sounds, skins, maps etc on the server. Using them (Mods/Plugins) will increase CPU utilisation and thus limit the final result. Obviously you need to monitor these for your particular situation.

 

17.Finally, you need to actually play on your server for several hours with all SRCDS processes full to see if there are any issues that do not show up by normal performance monitoring tools, to ensure everything is running ok. Subjective in game experience can deviate significantly from Objective Server Statistics, thus you will not know there is a problem unless you are on the server playing at the time it happens.

[dimitrifrom31]

also replace

-tickrate100

by

-tickrate 100

with a space

[the_unknown]

15.This information is for Windows Source Dedicated Server only.

 

i have a dedicated server

 

I'm not sure if this applies to my problem?

 

basically tried everything i spaced it in my server then said 101 tickrate

[Goran]

put the -tickrate 100 at the end of the command line

[the_unknown]

tried same thing as always

 

-game cstrike -console +ip 72.44.215.109 -port 27015 +maxplayers 24 +exec server.cfg +map ba_hiddens_jail -tickrate 100

[adamnp]

make sure you have your rates set correctly:

 

sv_maxcmdrate 101

sv_maxupdaterate 101

 

If still nothing, delete your binaries folder and run an update again to replace them, somethings corrupt.

[the_unknown]

is there any way i can save backups for my servers(mods,maps)? im planning to wipe out everything and start fresh

[adamnp]

Go on the machine and save the addons folder, the /cfg folder and if you have any specific sounds or materials those directories also. Then run the hldsupdate tool and itll replace the missing files.

 

-Adam

[the_unknown]

oh i found this in my bin folder ClientRegistry.blob im not sure thats suppose to be in there hmm

 

and these 2

 

these were outside my cstrike folder

 

hlds_steamgames.vdf

 

InstallRecord.blob

 

the ClientRegistry.blob created itself, in the bin folder outside

 

P.S i reinstalled everything

 

still that tick

[ECF]

Those files should be there. As for the tick issue I can't help.

[the_unknown]

alright so im using this game config CS_Source 100 tic and works!, but the settings reset every time i edit it in ftp for my "mods" and then when i do save the edits of my work it will convert back to a cheap low tick server.

[studeggle]

So start editing only one thing at a time. Something you are adding or changing is doing it.

[the_unknown]

studeggle

 

how can i make a good 66 tick server heres my config its for 100 tic but i want to use it for 66

 

// server name
hostname "CSS 100tic Server" 

// rcon passsword
rcon_password "------------" 

// Server password
sv_password "" 

// server cvars
mp_friendlyfire 0 
mp_footsteps 1 
mp_autoteambalance 1 
mp_autokick 0 
mp_flashlight 1 
mp_tkpunish 1 
mp_forcecamera 0 
sv_alltalk 1 
sv_pausable 0 
sv_cheats 0 
sv_consistency 1 
sv_allowupload 1 
sv_allowdownload 1 
sv_maxspeed 320 
mp_limitteams 2 
mp_hostagepenalty 5 
sv_voiceenable 1 
mp_allowspectators 1 
mp_chattime 10 
sv_timeout 65
sv_airaccelerate 200
sv_accelerate 10

// round specific cvars
mp_freezetime 0 
mp_roundtime 8 
mp_startmoney 1600 
mp_c4timer 45 
mp_fraglimit 0 
mp_maxrounds 0 
mp_winlimit 0 
mp_playerid 0 
mp_spawnprotectiontime 5 

// bandwidth rates/settings
sv_minrate 13000 
sv_maxrate 30000 
sv_minupdaterate 66 
sv_maxupdaterate 101 
sv_mincmdrate 66 
sv_maxcmdrate 101 
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 

// server logging
log off 
sv_logbans 0 
sv_logecho 1 
sv_logfile 1 
sv_log_onefile 0 

// operation
sv_lan 0 
sv_region 255 

// execute ban files
exec banned_user.cfg 
exec banned_ip.cfg 

[dimitrifrom31]

sv_minupdaterate 33

sv_maxupdaterate 67

sv_mincmdrate 33

sv_maxcmdrate 67

[adamnp]

As I quoted in the thread earlier, your sv_maxrate and sv_minrate will allow your server to run at the 100 ticrate mark. Restricting it below 100, will limit the ticrate to that. Even if the -ticrate is set to 100.

 

If you want it to run at 100 tic, utilize -ticrate 100 (in command line) sv_maxcmdrate 101, and sv_maxupdaterate 101. (in config file)

 

If you want it to run at 66 tic, utilize -ticrate 66 (in command line) and sv_maxcmdrate 66, sv_maxupdaterate 66. (in config file)

 

If you want it to run at 33 tic, utilize -ticrate 33 (in command line), and sv_maxcmdrate 33, sv_maxupdaterate 33. (in config file)