cl_cmdrate bug????

[bob7]

Hi to all,


Please forgive me if this topic has been discussed anywhere else in this forum,but I don't have much time to search for it exactly.

The actual problem is the following:

As soon as the sv_mincmdrate is 66 , when a client type in his console "cl_cmdrate 1" , then his ping will decrease too much, the so-called fake ping.I realy hate seeing people with fake low pings and one day, by using a plugin , i forced them to type the proper rates (rate 100000 , cl_cmdrate 66 , cl_updaterate 66) or else they would get kicked from the server, but it didn't work because most of them were not able to access the console at all!!!So they got kicked without knowing why.As a result, i discontinued this method.

Why the rates of a client (rate , cl_cmdrate , cl_updaterate) are not been set automatically to match the server's ones? I mean, for example you set at server.cfg the following rate settings:

sv_minrate 100000
sv_maxrate 100000
sv_maxupdaterate 66
sv_minupdaterate 66
sv_maxcmdrate 66
sv_mincmdrate 66

That means that you expect that the client will have 100000/66/66 because you set them that way.

But no, this is not happening , because client rates are different and are not forced to follow the previous ones.

And that exactly is my point because when someone has "cl_cmdrate 1" in his config (and you can see that when typing "ma_rates" in console,giving you the real rates of all connected clients,accessible via mani admin plugin), you expect from the above server side settings that he will send and receive 66 updates per second! Not only just 1!!! Right?
However,I see that his ping go low, following this "fake low ping bug", as if he receives only 1 update per sec!!!!!!

So my big question is:
Do I have to shout them and force them to fix their rates everytime they got that low f**** rate settings and fake their ping? Or do nothing , because the server side rate settings,mentioned above are preventing the client's cmdrate/updaterate to be changed anyway?

Sorry for that big post, but i want to clarify it to my mind...

P.S: the default cl_cmdrate and cl_updaterate are 30 and 20 for each.As a result,all rookie players have these low rate settings.

[coach]

Clients will be forced to the server rates.

When you call their rates internally it will show their settings.

On their end it will show a low ping but the rates are set to the servers. The ping is a false reading & something that they hold on to thinking they are getting a benefit. Does that make sense?

[BehaartesEtwas]

sv_mincmdrate and sv_minupdaterate force client rates, not their cvars, to specific values. and it works only, if the client can support the requested rate. especially the cmdrate cannot be higher than the fps. someone walking around with only 30 fps will never have a cmdrate higher than 30, regardless of any settings!

and btw: 20/30 are not low rates. that is a myth. you can perfectly play with those rates and all other players will not notice any difference. especially all negative effects are much stronger for the "low rate" player than for everyone else.

[bob7]

So , you mean that it doesn't matter the fact that they play with low rates, as soon as the server rates are set in a specific value, they play with the server's rates.Ok,that's acceptable!!!


But still can't accept the fake lower ping issue when clients have set them low. It's not smart :S


Is valve going to update this sometime?

Quote:and btw: 20/30 are not low rates. that is a myth. you can perfectly play with those rates and all other players will not notice any difference. especially all negative effects are much stronger for the "low rate" player than for everyone else

This is sick , because if you play with cmdrate 30 for example , and the server dont have sv_mincmdrate set to 66 , then its like playing with 30 fps, isn't it?

[BehaartesEtwas]

(02-18-2011, 08:56 AM)bob7 Wrote:  So , you mean that it doesn't matter the fact that they play with low rates, as soon as the server rates are set in a specific value, they play with the server's rates.Ok,that's acceptable!!!

yes. they do not play with low rates, but with low rate settings. their actual rates are still subject to server and fps constraints.

Quote:But still can't accept the fake lower ping issue when clients have set them low. It's not smart :S

a) I think it is not really possible to fake the ping into the lower direction and b) if someone would do this, it would be completely stupid. the lag compensation would no longer work for him, so he would need to aim ahead of his enemies, just like in old quake days. his enemies on the other hand would not note any difference. no, in fact, if someone wants to fake his ping, it is in the opposite direction. together (and only together) with some other hacks this could be used to get some advantage (namely more time to aim at the enemy).

reducing rates on the other hand will in fact reduce the ping (the real ping, not some fake), in case the connection is close to congestion. if it does so, it will actually make the gameplay much better for everyone (himself and his enemies)!

Quote:Is valve going to update this sometime?

what exactly? the only thing they could update are the default values for the rates, as most modern connections are capable of the highest possible rates (66/66 on CSS).

Quote:This is sick , because if you play with cmdrate 30 for example , and the server dont have sv_mincmdrate set to 66 , then its like playing with 30 fps, isn't it?

no, it's not, because of something called interpolation. simply try it out.