Сообщество Steam :: Руководство :: CS 1.6 Rates Guide

Эта публикация удалена, так как она нарушает рекомендации по поведению и контенту в Steam. Её можете видеть только вы. Если вы уверены, что публикацию удалили по ошибке, свяжитесь со службой поддержки Steam. Этот предмет несовместим с Counter-Strike. Пожалуйста, прочитайте справочную статью, почему этот предмет может не работать в Counter-Strike. This guide details the 4 main commands which are considered «rates». I explain each one and what the best setting is for each and why. Этот предмет добавлен в избранное. Ah rate, the setting that is set wrong by 95% of people who don’t have a clue and just copy everyone else. First we will start off with a quick history lesson. Quake, the game engine that was used to make Half-Life and in turn CS was created using the same engine. Quake has rates too! And in fact the max rate on Quake is 25000. This is why today most players use a rate of 25000. This is wrong. Half-Life 1/CS actually has a maximum rate of 20000, it has been proven many times and setting your rate to 25000 is pointless.
People also say «rate 25000 is for LAN and 20000 is for online», wrong again. When you play on LAN rate does nothing at all, in fact you could have rate set to 100 and it would have no effect on LAN. 20000. So all the players thinking they have been playing with a rate of 25000 on LAN are wrong, you have been playing with 20000 all along. 101(I will cover this later) but again, this is wrong. Cmdrate is data that you SEND to the server, so every time you shoot, walk, move your mouse, anything, cmdrate uploads data. Now because most people use 100fps people set it 1 above this to 101, so that you are always sending more data than needed, but 101 actually isn’t enough. This can be seen by net graph. Red dots appear at the bottom when data is not sent because your cmdrate is not high enough.
Red dots at bottom of net graph showing unsent data. Now with 101 you still get red dots from time to time, in fact the best cmdrate to use is always 5 more than your fps, so for the maximum 100fps 105 is fine. No red dots, all data is sent. Updaterate is a tricky one as the best setting is different depending on the server. Cmdrate is data you send to the server, updaterate is data you receive from the server. People just used to set this to 101 to match cmdrate but didn’t really know why. So how do you know what to set it to? 1 to predict it. 0. (I will cover this later) then join a server, if you see lots of orange and yellow dots on your net graph, this means your interp is set wrong for the server and you are not receiving the right amount of updates for your interp setting. Try lowing your updaterate by increments of 10 until the yellow/orange dots go away, you will find servers that have maxupdaterate set to 30 they will go away when you set it to 30 etc.
30, reg will be random and terrible. Still on ♥♥♥♥ server, but using correct updaterate and interp. Like I said, everyone just used to set it to 101 and leave it like that, this is wrong, the correct setting should match your interp otherwise will cause reg problems. 0.01 which I will go over next. 100, but I’m still getting yellow/orange dots! Just because a server has the right setting does not mean it can still actually send 100 updates per second, some bad servers can’t handle it and you should lower your updaterate by 10 until the dots go away, note servers like this are very bad as it depends on how many players and how much action is going on at the time. For example both teams rush B the server cant handle all the traffic of 10 people shooting at once and can only send for example 50 updates per second instead of 100 at that time, so everyone in that moment gets bad reg (which is shown by orange/yellow dots).
Источник: кейсы кс