Hey guys, salut mes amis och hallå gubbar, Maxim here. Here’s another noob to pro tutorial, this time I’m going to talk about network settings It’s important to know what the network settings do and which ones are the best. Since some of these technical terms can be hard to understand, I’m going to explain them as friendly as possible so that hopefully everyone understands. Let’s begin with the command Rate. To simplify the meaning, rate decides how much information you’re downloading from the server you’re playing on. When you watch a YouTube video, and you increase the quality you might have issues watching the video. But if you lower the quality you can watch the video without any problems BUT you won’t get the best quality. It’s pretty much the same with CS:GO. To find the best settings, you first need to know your internet speed. I’m using speedtest.net which is a perfectly fine and working service. What you need to look at is how fast your download speed is, your upload speed has nothing to do with this. Since I’m from the BEST country in the world, I’m getting these dope results.

But I know that most of you are not from Sweden, which is why I made a list here to show you what settings I recommend depending on your download speed. I’ve increased the requirement to give you the most stable solution for CS:GO. If your download speed is 8 megabits per second or more then use this to get the best server experience. If your download speeds are lower than 2 megabits per second I recommend using this value anyway. Now I wanna go through updaterate and commandrate. These commands are connected to the servers tickrate. Maximuh, what’s a tickrate? The tickrate is a frequency which checks if something has happened in the game. When you increase the tickrate you’re telling the server to work faster.

This means that the players on the server will need to keep up with the new speed. If the players can’t keep up they will encounter performance issues, that’s also why Matchmaking is using a tickrate value of 64. This is sort of like the safe-zone cause most players will not have any issues running the game here and it will still perform well. However, servers created by the community are usually set to 128 because it’s obviously more accurate, but it’s heavier for everyone. The best settings in my opinion is to set both cl_updaterate and cl_cmdrate to 128. If you look at your netgraph you can see if you’re using the best settings for the server. Ah, much better. Now let’s say you’re standing still and you’re getting peeked by someone. In this scenario you encounter something called interpolation. So what is interpolation? Let’s say the enemy moves like this, without interpolation the movement of the player can look very choppy or jittery. Interpolation will go back in time to make the movement smoother and more sexy.

But that also means that interpolation will not show you the players real position, which is bad if you wanna rek noobs. What I would recommend is to adjust the settings so you’re getting the lowest interpolation possible. Use cl_interp 0 and cl_interp_ratio 1. If you’re experiencing some packet loss, you can raise cl_interp_ratio to 2 or 3 instead. Next up, client-side prediction. In short, it means that if you’re moving around or shooting someone, you’re doing it before the server knows that you’re actually doing it.

If you have a bad ping and you shoot a player, you will see that the player gets hit much much later, just like one of those old low-budget fight scenes. I recommend having cl_predict and cl_predictweapons on 1. Even if you don’t hit your shots the same time the servers knows about it, it’s still better to be able to move and shoot from your screen without any delay. Another thing that really helps people with high ping is lag compensation.

If you don’t have lag compensation and you’re lagging because of your wireless connection or your slow internet, it could look like you’re shooting a ghost. Lag compensation works in a really cool way. When you shoot a moving player, the servers wants to be a bro. So the server goes back in time to compensate for the fact that your lagging and then counts it in as a hit. So basically you should ALWAYS enable lag compensation and prediction. Make sure cl_lagcompensation is set to 1. These are the most important network commands and now you’re ready to go! If I were you I would save these commands in a config so you can execute everything at once.

I’ll see you guys in the next video, go bananas!.

As found on Youtube