cs得显示速度很不正常

[狮蝎子]

cl_cmdrate越高越好，但要比cl_updaterate低，而cl_updaterate同尝试fps值得average。
这样子net_graph 2那条禄线才能保持直的，没有黄色的点点，减少chock，跟loss。

 

[狮蝎子]

还有可以在注册表里把rate改到25000，这样子cl_updaterate跟cl_cmdrate头可以跳到101，应该对大部分人有用。

 

[☆阿水☆]

最初由 狮蝎子 发布
cl_cmdrate越高越好，但要比cl_updaterate低，而cl_updaterate同尝试fps值得average。
这样子net_graph 2那条禄线才能保持直的，没有黄色的点点，减少chock，跟loss。

专业贴 (ZT)


rate determines the speed, in bytes per second, that your client allows itself and the server to interact at. This setting is needed because your client has no idea how fast your connection is, and it doesn't know how to find out. The rate setting tells it the maximum speed at which it can transfer data. If it is set too high, your connection may not be able to handle it, and you will get packetloss; if it is set too low, choke and latency will increase, possibly making your game stutter or lag. Half-life is generally able to compensate for choke fairly well, as long as there is not much of it; however, when choke gets too high (over 100), it has to start dropping packets (and we all know how bad packetloss is!). I recommend a rate of 8000 or 10000, since most broadband connections can easily handle it (try 10000 first).

cl_updaterate determines how many updates per second the client will accept when it is interacting with the server. A higher value can make gameplay more smooth, although it often makes your ping appear higher due to the added latencies on both ends from extra calculations involved. I recommend a cl_updaterate of 40, which I have found balances ping and smoothness fairly well. Feel free to try higher and lower values. A value too high can cause choke if your machine or your connection can't handle all the packets!

cl_cmdrate relates to how many commands your client sends to the server per second. "I usually recommend that users set their cl_cmdrate cvar to the same value as cl_updaterate."

 

[☆阿水☆]

最初由 狮蝎子 发布
还有可以在注册表里把rate改到25000，这样子cl_updaterate跟cl_cmdrate头可以跳到101，应该对大部分人有用。

一切命令都可以在cs的console里得到 不需要到去注册表