Settings for Counter-Strike 1.6 to reduce choke/loss and max FPS
Choke occurs when the game engine fails to deliver information to the player’s computer quickly enough, generating jagged edges on objects or “lag,” in which the game appears to stall.
Loss occurs when all information is lost, leaving the player with black squares or other visual artefacts in place of the game environment.
Several factors, including a slow Internet connection, a poorly designed game engine, or a fault with the game server, may be responsible for these troubles. The problems of choke and loss in Counter-Strike 1.6 can be fixed using optimised configurations and settings.
So if you looking for the best config for Counter-Strike 1.6 to gain a competitive advantage by reducing choke/loss and maximising FPS use the following configs:
Counter-Strike 1.6 Command-List
Type these in the console:
101 is the max you should set it, and if you have choke, you always lower it until you get a choke. So if you were getting like 20 chokes, lower the updatrate by typing cl_updaterate 70. See if you still have a choke after about 20 seconds. If you do, lower it some more.
This setting is supposed to be around your average fps. So if you average around 40-50, put it at 50. If your getting a constant 100 in the server, you input it 101.
FPS Note: If you have your fps set to fps_max 101 and your fps goes down to like 40-50 and keeps moving around drastically, set it to fps_max 75. Keep lowing the setting bit by bit until it remains pretty constant.
the rate setting is debated a lot, but if you want max performance, use 20000. Many say 25000, but they do not realize that is a LAN setting. Use rate 20000.
Other tips use 16-bit colour.
Use worst-looking smoke grenades.
What is Choke?
Choke is a dynamic technology used to manage network congestion. It happens when the game server believes that a player’s machine is not prepared to accept input due to the possibility of flooding their connection. That or it might be the consequence of an excessive number of requests being made to the server, leading it to throttle its output.
In either situation, the server intervenes and ensures that things continue running smoothly by restricting the amount of input or requests it replies to, even though the best-case scenario seems smooth from the player’s viewpoint.
When it comes to gaming, first-person shooters may be more prone to online difficulties such as choke due to the massive volume of data traffic created by individual players, translated by the server, and then returned to all players on that server.
With so much vital information being sent, little choking may go a long way. In gaming terminology, if you attempt to play online on a congested network – even if you have a high-speed internet connection – your gaming device may miss critical data from a server.
Effect of Packet Loss and Choke in Counter-Strike
As with the term ‘ping’ being used (inadvertently) interchangeably with ‘delay,’ ‘packet loss’, or often just ‘loss’, is a phrase that may be used interchangeably with ‘choke’.
While packet loss and choke are conceptually similar, or even two sides of the same coin, they are technically distinct. Having said that, the effect of each on gameplay might be similar.
Whether you’re experiencing choke or packet loss (or both), your online gaming experience will almost certainly seem unresponsive and imprecise regarding input instructions and may even exhibit a stuttering effect.
When you encounter a choke, your input instructions may seem to be wrongly translated, giving the appearance that you are teleporting or that your hit register is incorrect. This may result in an unresponsive online gaming experience that is, at worst, unusable.