Cl_updaterate and Cl_cmdrate should be forced to 66

[TaZ]

Hi so ive been chatting a lot with a friend who is a NFO Tech guy and I asked him about updaterate and cmdrate. He said if the server wants better reg then we should force them to 66. He said most people do not even know they can change there rates so there using default rates. Which are cl_updaterate 20 cl_cmdrate 30
The people with these rates will cause the biggest issuse for shot reg on servers. The packets of a high ping player (100 plus ping) will be so slow the players will not hit these players as much. So can we maybe try and foce the update and cmd rates to 66?

 

[sweg]

uhh dropbox?

Sent from my LGLS990 using Tapatalk

 

[Dr. Doctor (inactive)]

Our current servers are 64 tick aren't they? I don't think 66 tick would make much of a difference.

 

[RedDragonKnight]

Our current servers are 64 tick aren't they? I don't think 66 tick would make much of a difference.

He's talking about the source servers.

 

[Dr. Doctor (inactive)]

He's talking about the source servers.

...but would it make a difference?

 

[Fish]

k

 

[TaZ]

for the record yes it would make a difference. Update rate at default is like dial up connection. It is not set to 66 you can set it to 20

 

[Dr. Doctor (inactive)]

for the record yes it would make a difference. Update rate at default is like dial up connection. It is not set to 66 you can set it to 20

Ahhh, I see. Don't servers override that, though, i.e. a 64-tick server setting it to 64 while the connection is open?

 

[RedDragonKnight]

Ahhh, I see. Don't servers override that, though, i.e. a 64-tick server setting it to 64 while the connection is open?

a server can force rates. i don't think it is.

 

[Dr. Doctor (inactive)]

a server can force rates. i don't think it is.

I know that the CSGO MM servers do this. Certain community servers do, too. Not sure if this is needed for our d2 server, though. It's hectic enough, hitreg is not an everpresent worry.

Sent from my ONEPLUS A3000 using Tapatalk