30tic = slow pistol fire

[Shaft 6]

i host the odd source mod here and there when there are no other servers with the features i want.

one issue i have come across is the hl2 pistol in synergy has a slow fire rate with a low tick rate. if i increase the tick rate it fixes the problem but i'm hosting from home so i don't want people chewing up my bandwidth. i have tried sv_maxcmdrate 30 but it doesn't seem to make any difference.

a solution to this would be nice preferably one that doesn't involve increasing the tic rate because me cpu has a hard enough time on some synergy maps. also this isn't just a synergy thing its also noticeable on zombie panic source but not as bad.

[Spartanfrog]

Uhh 30 tickrate? I thought the least was 33? Anyway, just up it to 33. It wont use much more reasources or bandwidth but would be fine and the pistol should not shoot slower.

[Shaft 6]

Spartanfrog Wrote:Uhh 30 tickrate? I thought the least was 33? Anyway, just up it to 33. It wont use much more reasources or bandwidth but would be fine and the pistol should not shoot slower.

oh yea thats the other thing. if i up it to 33 the problem is only a little less both zps and synergy are designed to run at 66 tick i think.

btw only the tickrate needs raising not peoples rates. i've tried 66tick with 20upd 30cmd and its fine the only problem is people are allowed to crank the cmd over 30

[Drocona]

Then try set the tickrate to 66, but keep sv_maxupdaterate 30, see if that's any good.

[Shaft 6]

Drocona Wrote:Then try set the tickrate to 66, but keep sv_maxupdaterate 30, see if that's any good.

i use sv_maxupdaterate 20 and that works. I want to know if there is a way to raise tickrate and limit the cmd lower than the tick.

[Drocona]

Only way to lower cmd is the way I told you above, you set the tickrate in commandline but limit it by sv_maxupdaterate

[Shaft 6]

Drocona Wrote:Only way to lower cmd is the way I told you above, you set the tickrate in commandline but limit it by sv_maxupdaterate

i don't quite follow.

i put -tickrate 66 in command line and sv_maxupdaterate 20 in server.cfg. then as a client i join with cl_updaterate 66 cl_cmdrate 66 and the updaterate is 20 but the cmdrate is still 66.

i thought sv_maxupdaterate only controls the updaterate not cmdrate?

[Drocona]

Well the updaterate is linked to the tickrate, so you can run a server at 66 tick (which is the cmdrate of the server) but you can limit the updates per second (which is also the server tick) to a certain number without lowering the cmdrate.

If a client connects it HAS to use the servers maxupdaterate, no matter what he has in his cl_updaterate and cl_cmdrate, it's always limited by the lowest of both, in this case the server.