Changes made to server

[Yamagata 1st MRB]

Here are some of the changes gameservers made to fix our server problem:

// 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

Just in case people were wondering about changes in rates.

[Dillon 1st MRB]

I'm not sure why moving our server from a 100 tick to 66 tick server is going to reduce lag. Its an area where I'm more of a dabbler. Can anyone shed some light on this?

[Dillon 1st MRB]

In my research, I found out that tick rate is just packets.... Are we losing packets to and from the server? I'll do a little research when I get home. I hope the router/swtich at gameservers isn't going out on us. Nothing like CPE errors to make a host drag their feet. Stupid things are expensive.

[Sarsons]

is there anything that we should be changing on our ends to compensate for the rate changes? I for one have been having a Bitch of a time with bullets regestering

[Brewer]

Server is still messed up.

[M. Swartz 1st MRB]

The rates look to be the same Sarson, so you shouldnt have to change anything. To verify your rates you can check them in the console in game. For rate: type rate in console. Should be set to 25000. If not type in console, rate 25000.

For cmd rate type: cl_cmdrate. should be set to 66. to change type in console, cl_cmdrate 66

For update rate type: cl_updaterate. should be set to 66. to change type in console, cl_updaterate 66.

You can set these rates higher but it will only use our server limits. I am also not sure but the server was set up to automaticaly change everones rates when they join.

2ndLt. M. Swartz

[Brewer]

server is good now.