To change the value of these variables (as any others) you should either set them directly from console or by “set variable value” command or just set them in your config file.

com_maxfps - maximum number of frames, sent from server to the client. Accordingly your FPS can’t exceed this number. The change of this variable won’t improve the connection quality, but can prevent the problems with FPS jumps, connected either with connection lags or with lags of the system itself. The most optimal com_maxfps value is your average FPS. Choose it having played for a while with the FPS meter on - "cg_drawfps 1".

cg_lagometer - now you should test your connection at work. In order to do it you should turn the lag-meter on by means of "cg_lagometer 1" command. You’ll have a small oscillograph. The first line on a diagram shows as your system reacts to the data, sent from server about changes in game situation. If the line is blue then it’s ok, your screen refreshes as the situation in a game changes. If it’s yellow, then it means that your system fails to process some data sent from server. In this case you should either stop sending this additional information by means of "snaps" command, or follow the recommendation on videoparameter setting to increase the system output. The second line is a network graph similar to the one used in Quake2. The green color indicates that connection is ok; yellow – that you don’t have enough rate to send all parcels ; red color shows that some network parcels are lost due to the low connection quality. Conclusion: if yellow color prevails, then try to increase rate and decrease snaps. If red prevails, then I would recommend switching to another server or searching another connection alternatives. Try to change settings at least. Set "cl_packetdup 1" and try to adjust snaps and cl_maxpackets, in order to make up/compensate parcel loss.

Вторая линия - это сетевой график, аналогичный тому, что был в Quake 2. Зеленый цвет показывает что связь в порядке; желтый, что вам не хватает rate для передачи всех пакетов; а красный говорит о том, что из-за низкого качества связи теряются сетевые пакеты. Выводы: если много желтого, то попробуйте повысить rate или уменьшить snaps. Если у вас много красного, то рекомендую перейти на другой сервер или поискать другие варианты соединения. В крайнем случае попробуйте поэкспериментировать с настройками. Поставьте "cl_packetdup 1" и попробуйте отрегулировать snaps и cl_maxpackets, чтобы компенсировать потерю пакетов.

snaps - this variable defines the number of “snaps” with information about game situation is sent from server to the client.

cg_predictitems - defines whether it is a server or a client that makes the decision about an item being picked up. I’d recommend setting “0” here, i.e. let the server define whether you’ve taken armor (weapon, health and etc.) or not. If you set “1” then there are situations when you think that you’ve picked an item up, though you haven’t actually.

cg_nopredict - this variable defines whether the player system can make a prediction – i.e. try to determine what changes have really occurred on server if there is a network parcel loss due to the connection problems. It is “1” by default, i.e. prediction is allowed. I’d recommend to leave it as it is.

rate - size of the network parcels. I’d recommend setting the values depending on your connection speed. In the end of this section there is a summary table with values advisable for each type of connection. Don’t forget that if you have data compression connection then you can increase the rate parameter. Read how to use lag-meter and try experimenting with rate value to improve it.

cl_timenudge - if you’ve played QuakeWorld, HalfLife, then you should remember "pushlatency" command. So, "cl_timenudge" is its synonym. I won’t explain the meaning of this variable, I’d rather say that "cl_timenudge" value should be some 30-50 points lower than your average ping. You can try experimenting with it using lag-meter to check the results.

cl_packetdup - if you turn this variable on, then every network parcel (minimal data block) sent between server and clients is duplicated in case of bad connection data loss. If you have a good connection (see the lag-meter), then turn duplication off with "cl_packetdup 0", if according to the lag-meter you loose your parcels constantly, then turn "cl_packetdup 1".

cl_maxpackets - this variable sets the maximum number of parcels that your system can send to the server. Changing its value can help those with low outgoing traffic speed. It’s “30” by default. Sometimes with modem connection you should decrease its value. And playing with digital connection you should increase it.

cg_forcemodel - if "1" is set, then all players on server will have standard model “to you” (or Sarge in old version, or your model in the latest version), accordingly allowing your system not to keep in mind other models. It’s “0” by default, i.e. all players have chosen models.

By Goblin and Littleb