|
12-07-2007, 02:27 AM | #1 |
Join Date: Oct 2007
Posts Rated Helpful 0 Times
|
My tick rate is stuck at 33 no matter what server's is
How do I get mine to sync with what server is using?
cl_updaterate "33" cl_cmdrate "33" are these cmds right or do they need to be changed to 66 both, don't want to do anything if I screw up my cfg file. Skillet |
|
12-07-2007, 02:56 AM | #2 |
Join Date: Mar 2007
Posts Rated Helpful 5 Times
|
I thought that the tick rate was a locked down variable for now. I 'm not sure, though.
|
|
12-07-2007, 03:46 AM | #3 |
[AE] 0112 Ihmhi *SJB
Wiki Team
Fortress Forever Staff |
It doesn't matter what you set it to in your console really; the server is locked at 33. Any more than that and FF's server performance goes to Hell.
__________________
Anime: The Thread: Reloaded The one and only anime thread on these here forums. Select the pistol, and then, select your horse. |
|
12-07-2007, 04:44 AM | #4 |
Fortress Forever Staff
|
Feel free to adjust and test those settings all you like.
Here is a guide a long time ago for TFC. ----------------------------------------- Use net_graph "1" Then experiment to get the best settings. Watch the graph lines for the best STABLE ping. On DSL I'm using: (now on cable) cl_cmdrate "100" cl_updaterate "45" rate "20000" I picked up this rate setting from hltoolz. Many ppl use rate "9999". To be honest, I have forgotten what the net_graph "1" lines specifically represent. IN A PERFECT WORLD, the lines would be solid and flat without any spikes or breaks. You want to tweak your settings using net graph one. It does help. For a starting point, enter a game and use: cl_cmdrate "100" cl_updaterate "100" Then change that to cl_updaterate "20". Twenty is probably not a realistic setting but it will let you see the difference it makes in its graph line and in your PING. Start raising the setting by increments of 5-10 points until the line is as flat/stable as it gets. THEN STOP. A lower cl_updaterate will lower your ping but you don't want to sacrifice quality for speed or vice versa. Next do the same thing with cl_cmdrate. Just take your time with it, it's easy to see. |
|
12-07-2007, 05:41 AM | #5 |
Join Date: Oct 2007
Posts Rated Helpful 0 Times
|
Thanks for the replies guys
|
|
12-07-2007, 04:46 PM | #6 | |
SHUT UP AND SWALLOW
Join Date: Sep 2007
Location: Argentina
Posts Rated Helpful 0 Times
|
Quote:
|
|
|
12-07-2007, 05:12 PM | #7 |
G9-
D&A Member
Join Date: Sep 2007
Location: Florida
Class/Position: D Solly,Engy Gametype: ALL Posts Rated Helpful 0 Times
|
on the servers that perform best for me i saw most of them set to 33tick,
and for whatever reason's i could never get rjumps for shit sticking to the floor like i was glued to it pissed me off tbh. so now that our server is at 66 and nfo is 66 now i can rjump like a allstar. maybe thats just me but mainly what i go by is the in and out numbers on the far right on net graph 3 the ones that read #/s i was told they indicate about where the tick rate is set at on the server. if thats wrong though plz let me know.but either way if the #/s's read 66 or lil higher lil lower i can perform better at rjumps and conc's i just thought ide share that and maybe it helps ppl that had my prob. also my cl_updaterate "101" cl_cmdrate "100.000000" ok peace!
__________________
|
|
12-08-2007, 06:37 PM | #8 |
Retired FF Staff
Join Date: Mar 2007
Posts Rated Helpful 0 Times
|
If I remember right in ff 1.0 the suggested tickrate was 33. But with the subsequent patches you were supposed to be able to set it to a max of 66.
__________________
I Love GenghisTron . I miss you sooooo Much. LOL. |
|
12-13-2007, 08:08 PM | #9 |
Retired FF Staff
Join Date: Jan 2005
Location: CowTown
Posts Rated Helpful 0 Times
|
66 server tickrate is fine if your server can handle it. You can't set it any higher, though. We clamped it to 66 max b/c going higher screws with the timing of elevators, doors, etc (that is, you touch them and die )
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|