Advertisement
sndrec32

TF2 Tickrate Guide

May 15th, 2015
1,969
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.41 KB | None | 0 0
  1. the tickrate launch parameter was disabled by an update from valve back in 2010, and naturally, a plugin was swiftly written to bypass this. it works for both CSS and TF2, though i've yet to find any TF2 server making use of it. you can find the plugin + its source code here: http://didrole.com/tickrate_enabler/ - you MUST install it in order to modify your tickrate.
  2.  
  3. tickrate is set by adding -tickrate # to the server command line start up parameters. it cannot be changed in realtime, and the server must be restarted when you wish to modify it. additionally, if your server is running on windows, you will need to use a third party program in order to boost the Windows Kernel Timer Resolution - you won't see the benefit of a higher tickrate without it. i'm not entirely certain on the particulars linux servers - i'd like if someone could get back to me on that subject.
  4.  
  5. you can either run Windows Media Player, or use this small command-line app to do it. http://whisper.ausgamers.com/downloads/srcdsfpsboost.zip
  6.  
  7. 1. set your tickrate in your command line parameters. 100 or 128 are good values to go with if you are running a smaller server (12-18 players). you may find that your server performance suffers if you try to use a high tickrate value such as 128 on an active pub server of 24 players, if your server hardware or connection isn't up to snuff. a tickrate of 128 is almost double what the game normally simulates - so expect around twice the CPU + bandwidth usage on your server!
  8.  
  9. 2. if on windows, run media player or srcds fps booster, so that your server can achieve a higher fps.
  10.  
  11. 3. adjust your server cvars! you won't see much improvement if you don't have rates that your clients can make use of.
  12.  
  13. i've included MINIMUM rate cvars in here, since most players don't have their rates set up for more than 66 tick. if you deem it necessary, these commands will force them to send and receive 128 updates per second - otherwise, leave them out.
  14.  
  15. fps_max 300
  16. sv_minrate 10000
  17. sv_minupdaterate tickrate
  18. sv_mincmdrate tickrate
  19. sv_maxrate 20000
  20. sv_maxupdaterate tickrate
  21. sv_maxcmdrate tickrate
  22.  
  23.  
  24. an sv_maxrate 20000 server with 20 players is going to require around a 4Mbps upstream connection to adequately cope with the load. this was harder to achieve many years ago before the tickrate restriction was introduced, but most servers nowadays should be able to withstand the extra load.
  25.  
  26. good luck, and happy fragging.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement