Forum
128 tickrate addon
Created 15th May 2015 @ 18:25
Add A Reply Pages: 1 2 Next »
Quintosh found this earlier today: https://teamfortress.tv/thread/25252/tips-how-to-run-your-server-at-a-higher-tickrate
Basically allows you to run your server at 128 tickrate instead of 66. We tested it in a lobby, and it’s quite clear the hitreg has improved. Please let me know what you think. I’ve set up an MGE server located in germany, running 128tick, which will be open for the next few days: 23.102.35.9:27015 – http://imgur.com/NCfYeIF
Remember to change your updaterate/cmdrate to 128 as well, as you otherwise won’t feel the effect: http://imgur.com/TCDZOY9
It should be fixed now, so you can go to 128. Remember to change your updaterate/cmdrate
Quoted from this is evil evil
It should be fixed now, so you can go to 128. Remember to change your updaterate/cmdrate
please disable random crits, weapon spread, and random damage spread on your MGE server!
tf_weapon_criticals 0
tf_use_fixed_weaponspreads 1
tf_damage_disablespread 1
haha.. sorry man. I’ll do it now :D
I see a lot of players on the server now. Remember to leave your feedback, if it feels any different and/or if you encounter any bugs.
use these settings for an optimal experience in the server
cl_updaterate 128
cl_cmdrate 128
cl_interp 0.016
cl_interp_ratio 1
rate 20000
these seem to be good so far. more testing will reveal better network settings in regards to rates! we’re all stepping into unknown territory, after all.
Last edited by sndrec32,
Quoted from sndrec32
use these settings for an optimal experience in the server
cl_updaterate 128
cl_cmdrate 128
cl_interp 0.016
cl_interp_ratio 1
rate 20000these seem to be good so far. more testing will reveal better network settings in regards to rates! we’re all stepping into unknown territory, after all.
True dat. Those are good settings. You can confirm they are working, by looking at the following numbers on your net graph: http://imgur.com/TCDZOY9 – They should most definitely go above 66, if your connection and computer allows it.
You should not use anything else than 66tick on TF2, there are many parts of the game engine where calculations are based on tick 66, so this’ll fuck up a lot of things (e.g. weapon recoil). That’s why the tickrate is locked to 66 in TF2.
On CS GO Valve fixed all these tickrate issues, so it can be modified without any issues.
Quoted from AnAkkk
You should not use anything else than 66tick on TF2, there are many parts of the game engine where calculations are based on tick 66, so this’ll fuck up a lot of things (e.g. weapon recoil). That’s why the tickrate is locked to 66 in TF2.
On CS GO Valve fixed all these tickrate issues, so it can be modified without any issues.
Yeah, you are probably right. No hurt in testing it now though, to see if it has any use for the competitive side of TF2 :)
Quoted from AnAkkk
You should not use anything else than 66tick on TF2, there are many parts of the game engine where calculations are based on tick 66, so this’ll fuck up a lot of things (e.g. weapon recoil). That’s why the tickrate is locked to 66 in TF2.
On CS GO Valve fixed all these tickrate issues, so it can be modified without any issues.
using those net settings on a normal server is props not good, right?
Add A Reply Pages: 1 2 Next »