Adjust CSS rate
Solved/Closed
spawnland
Posted messages
98
Status
Membre
-
elmouth -
elmouth -
Hello,
Once and for all, I would like to know what rate settings to make when playing on a 100 tick server and the FPS, thank you if you have the right answers
connection 1/2M
Once and for all, I would like to know what rate settings to make when playing on a 100 tick server and the FPS, thank you if you have the right answers
connection 1/2M
46 réponses
- 1
- 2
- 3
Suivant
The console allows you to make several adjustments to the game that are not available through the game options.
To activate the console, go to your Steam menu -> Games -> right-click on Counter Strike Source -> Properties -> Launch Options, and write:
"-console " You can add " -dev " for more details about your machine and -heapsize to allocate the RAM that the game can use.
Example: -console -dev -heapsize 1048576 with a space before each dash.
The -heapsize command thus allows you to define the amount of RAM that CSS can use. It is recommended to allocate half of your total RAM
-heapsize 1048576 allocates 1048576 bytes, which corresponds to 1024 MB. To find the value, simply multiply the desired amount by 1024 (1024*1024 => 1048576). To allocate 512 MB, 512*1024 = 524288. The command to allocate 512 MB will therefore be -heapsize 524288.
Setting the rates to optimize your ADSL connection on a tick 100 server:
Type the following codes in the console to configure CSS. /!\ The values listed are for a connection greater than 8 MB; for other connections, see the entire tutorial /!\
Rate 25000 This is the speed at which you download information from the server you are playing on.
cl_rate 25000 This is the upload speed of game data. That is, the speed at which you send information to play safely on the server. The value of this command must be equal to the value of the rate command.
cl_cmdrate 101 This command sets the number of packets (data that circulates so that your game works alongside other players on the server) that you send to the server where you are playing.
cl_updaterate 101 The cl_updaterate command concerns the refresh rate of data; the higher it is, the more you send or receive information from the server.
Low-Speed Connection 128k rate 6500 cl_rate 6500 cl_cmdrate 40 cl_updaterate 30 ADSL Connection 512k rate 9999 cl_rate 9999 cl_cmdrate 60 cl_updaterate 50
ADSL Connection 2MB rate 15000 cl_rate 15000 cl_cmdrate 80 cl_updaterate 60 ADSL Connection 4MB rate 20000 cl_rate 20000 cl_cmdrate 100 cl_updaterate 80
Useful command for the game but not mandatory:
cl_interpolate 1 Allows the computer to fill the gap of certain users who do not send enough ticks to the server, due to low FPS or a poorly set cmdrate. Set to 0, these players will stutter and be almost untouchable.
cl_interp_ratio 1 The value of this variable divided by the updaterate should give 0.01, or as close as possible, because it is the delay of the graphical display compared to the received data. e.g., at 10, divided by 100 [updaterate] gives 0.1, which means a 0.09-second delay compared to the rest of the world on the server. The goal would be to reach 0.01.
cl_predict 1 Allows the client to do certain things without receiving permission from the server, such as shooting and moving. Sometimes you may shoot and the bullet goes right through the person without hitting them; this is caused by this function, as the server did not receive the info for some reason, but the client preemptively displayed this info. If set to 0, this function causes chaos because some animations and movements are interrupted because the server lost the info, which would normally have been filled in by the client.
cl_smooth 1 Works alongside cl_predict, as this function smooths out the recoil due to the server not having received your last shot or your last movement. Set to 0, this function drastically corrects your position relative to the one you have on the server, causing stuttering at certain moments.
cl_smoothtime 0.01 This is the time allowed for cl_smooth to take effect; keep it as low as possible (0.01). If the smooth exceeds this time limit, the server will brutally reset your position. Rarely found on quality servers.
Cmdlist All available game commands in the console.
cl_crosshairscale 6000 Change the size of your crosshair; the larger the number, the smaller the crosshair size, with a maximum of 6000. Note that changing the size of the crosshair does not alter the trajectory of the bullets... lol.
cl_crosshairusealpha 1 Allows for a non-transparent crosshair => better visibility.
cl_dynamiccrosshair 0 Prevents the crosshair from expanding when you run/jump.
mat_bumpmap 0 Remove bumpmapping for a substantial FPS gain.
cl_phys_props_enable 0 Disables small objects that do not interfere with movement (small boxes, bricks, etc.). This provides a substantial FPS gain and reduces the information transfer between the server and your machine, thus improving ping.
cl_ragdoll_physics_enable 0 Removes the bodies of dead characters. No bodies on the ground. This provides a substantial FPS gain and reduces the information transfer between the server and your machine, thus improving ping.
nosounds To avoid disturbances in the game from all the little sounds introduced into the server, such as haha, runaway, etc.
cl_downloadfilter nosounds Prevents downloading sounds upon entering a server.
To display details of your FPS, ping, and others, go to a server and type in the console: "net_graph 3" it will display on the right.
The details that net_graph displays:
· Your FPS is the number of frames per second processed by your machine. The higher the number of frames, the smoother the animation appears.
· Your PING is the response time of your machine with the server; the smaller it is, the faster data transfers are between the server and your machine.
· Your REAL IN (the updaterate) is the number of updates sent by the server per second; the larger the value, the more accurate the simulation is.
· Your REAL OUT (the cmdrate) is exactly the same as before, but this is for updates received by the server; the larger the value, the better.
· Your LOSS is the number of lost packets in transit; basically, there's nothing we can do about it, as it's related to the quality of your connection!
· Your CHOKE, having choke means that the game does not have enough available bandwidth to exchange packets at the desired frequency; if you have choke, you won't hit anything! With a good rate setting, choke should not cause issues. However, if choke is significant, gradually decrease the cl_updaterate and cl_cmdrate, but never below 60, otherwise you'll lag.
/!\ (Setting values too low for rate, cl_updaterate, and cl_cmdrate can be considered cheating because you'll lag for other players, in other words, you'll become difficult to hit) /!\
To activate the console, go to your Steam menu -> Games -> right-click on Counter Strike Source -> Properties -> Launch Options, and write:
"-console " You can add " -dev " for more details about your machine and -heapsize to allocate the RAM that the game can use.
Example: -console -dev -heapsize 1048576 with a space before each dash.
The -heapsize command thus allows you to define the amount of RAM that CSS can use. It is recommended to allocate half of your total RAM
-heapsize 1048576 allocates 1048576 bytes, which corresponds to 1024 MB. To find the value, simply multiply the desired amount by 1024 (1024*1024 => 1048576). To allocate 512 MB, 512*1024 = 524288. The command to allocate 512 MB will therefore be -heapsize 524288.
Setting the rates to optimize your ADSL connection on a tick 100 server:
Type the following codes in the console to configure CSS. /!\ The values listed are for a connection greater than 8 MB; for other connections, see the entire tutorial /!\
Rate 25000 This is the speed at which you download information from the server you are playing on.
cl_rate 25000 This is the upload speed of game data. That is, the speed at which you send information to play safely on the server. The value of this command must be equal to the value of the rate command.
cl_cmdrate 101 This command sets the number of packets (data that circulates so that your game works alongside other players on the server) that you send to the server where you are playing.
cl_updaterate 101 The cl_updaterate command concerns the refresh rate of data; the higher it is, the more you send or receive information from the server.
Low-Speed Connection 128k rate 6500 cl_rate 6500 cl_cmdrate 40 cl_updaterate 30 ADSL Connection 512k rate 9999 cl_rate 9999 cl_cmdrate 60 cl_updaterate 50
ADSL Connection 2MB rate 15000 cl_rate 15000 cl_cmdrate 80 cl_updaterate 60 ADSL Connection 4MB rate 20000 cl_rate 20000 cl_cmdrate 100 cl_updaterate 80
Useful command for the game but not mandatory:
cl_interpolate 1 Allows the computer to fill the gap of certain users who do not send enough ticks to the server, due to low FPS or a poorly set cmdrate. Set to 0, these players will stutter and be almost untouchable.
cl_interp_ratio 1 The value of this variable divided by the updaterate should give 0.01, or as close as possible, because it is the delay of the graphical display compared to the received data. e.g., at 10, divided by 100 [updaterate] gives 0.1, which means a 0.09-second delay compared to the rest of the world on the server. The goal would be to reach 0.01.
cl_predict 1 Allows the client to do certain things without receiving permission from the server, such as shooting and moving. Sometimes you may shoot and the bullet goes right through the person without hitting them; this is caused by this function, as the server did not receive the info for some reason, but the client preemptively displayed this info. If set to 0, this function causes chaos because some animations and movements are interrupted because the server lost the info, which would normally have been filled in by the client.
cl_smooth 1 Works alongside cl_predict, as this function smooths out the recoil due to the server not having received your last shot or your last movement. Set to 0, this function drastically corrects your position relative to the one you have on the server, causing stuttering at certain moments.
cl_smoothtime 0.01 This is the time allowed for cl_smooth to take effect; keep it as low as possible (0.01). If the smooth exceeds this time limit, the server will brutally reset your position. Rarely found on quality servers.
Cmdlist All available game commands in the console.
cl_crosshairscale 6000 Change the size of your crosshair; the larger the number, the smaller the crosshair size, with a maximum of 6000. Note that changing the size of the crosshair does not alter the trajectory of the bullets... lol.
cl_crosshairusealpha 1 Allows for a non-transparent crosshair => better visibility.
cl_dynamiccrosshair 0 Prevents the crosshair from expanding when you run/jump.
mat_bumpmap 0 Remove bumpmapping for a substantial FPS gain.
cl_phys_props_enable 0 Disables small objects that do not interfere with movement (small boxes, bricks, etc.). This provides a substantial FPS gain and reduces the information transfer between the server and your machine, thus improving ping.
cl_ragdoll_physics_enable 0 Removes the bodies of dead characters. No bodies on the ground. This provides a substantial FPS gain and reduces the information transfer between the server and your machine, thus improving ping.
nosounds To avoid disturbances in the game from all the little sounds introduced into the server, such as haha, runaway, etc.
cl_downloadfilter nosounds Prevents downloading sounds upon entering a server.
To display details of your FPS, ping, and others, go to a server and type in the console: "net_graph 3" it will display on the right.
The details that net_graph displays:
· Your FPS is the number of frames per second processed by your machine. The higher the number of frames, the smoother the animation appears.
· Your PING is the response time of your machine with the server; the smaller it is, the faster data transfers are between the server and your machine.
· Your REAL IN (the updaterate) is the number of updates sent by the server per second; the larger the value, the more accurate the simulation is.
· Your REAL OUT (the cmdrate) is exactly the same as before, but this is for updates received by the server; the larger the value, the better.
· Your LOSS is the number of lost packets in transit; basically, there's nothing we can do about it, as it's related to the quality of your connection!
· Your CHOKE, having choke means that the game does not have enough available bandwidth to exchange packets at the desired frequency; if you have choke, you won't hit anything! With a good rate setting, choke should not cause issues. However, if choke is significant, gradually decrease the cl_updaterate and cl_cmdrate, but never below 60, otherwise you'll lag.
/!\ (Setting values too low for rate, cl_updaterate, and cl_cmdrate can be considered cheating because you'll lag for other players, in other words, you'll become difficult to hit) /!\
Hi, does this happen to you on all servers or just some servers? Because it happens to me too, but most of the time it's on servers where I have a high ping, between 50-60, often German or English servers for example. Otherwise, use the following values: cl_cmdrate 101 and cl_updaterate 101. Try to see if it still happens, then reduce the values by 5 and try again and so on, and you should normally find the right values suitable for your internet connection. Once you find the rate values based on what you discovered (e.g., cl_updaterate 75 and cl_cmdrate 75: rates 15000, etc...). There you go, good luck with CSS.
Low-Speed Connection 128k rate 6500 cl_rate 6500 cl_cmdrate 40 cl_updaterate 30
ADSL Connection 512k rate 9999 cl_rate 9999 cl_cmdrate 60 cl_updaterate 50
ADSL Connection 2MB rate 15000 cl_rate 15000 cl_cmdrate 80 cl_updaterate 60
ADSL Connection 4MB rate 20000 cl_rate 20000 cl_cmdrate 100 cl_updaterate 80
good luck and keep me updated, please, thanks.
Low-Speed Connection 128k rate 6500 cl_rate 6500 cl_cmdrate 40 cl_updaterate 30
ADSL Connection 512k rate 9999 cl_rate 9999 cl_cmdrate 60 cl_updaterate 50
ADSL Connection 2MB rate 15000 cl_rate 15000 cl_cmdrate 80 cl_updaterate 60
ADSL Connection 4MB rate 20000 cl_rate 20000 cl_cmdrate 100 cl_updaterate 80
good luck and keep me updated, please, thanks.
You're welcome, it's always a pleasure to help a CSS colleague. Have fun to everyone who reads this message. Goodbye!
Hi everyone
Sairus, I noticed that you are good with settings, could you help me? I've been playing CSS for about 6 months, but for the past month, I've been lagging a lot. My FPS went from 95 to 8 and my ping from 80 to 175, with spikes up to 1004.
I was told to adjust my rates, so that's what I did, but my game has become unplayable, and I can't reinstall it because my CD drive no longer detects it.
Thank you in advance.
Sairus, I noticed that you are good with settings, could you help me? I've been playing CSS for about 6 months, but for the past month, I've been lagging a lot. My FPS went from 95 to 8 and my ping from 80 to 175, with spikes up to 1004.
I was told to adjust my rates, so that's what I did, but my game has become unplayable, and I can't reinstall it because my CD drive no longer detects it.
Thank you in advance.
Uh, logic dictates that we set the rates to the maximum since it's a limit! Capping the throughput is completely stupid; when are you going to understand that???? Rate 81920 is the maximum value, and if your connection isn't fast enough to reach that value, there is no prejudice! You need to stop saying nonsense; it's absurd to block the rates at 25000!
We need to stop the nonsense about rate and cmd settings... rate at 7500 or 10000 is just plain ridiculous: in my team, many don't even have 1 Gbps and set their rate to the maximum to minimize shocks... for proof, test it yourself by setting a very high value (80000) and you should experience less "shock", and anyway, the server has a maximum limit and will automatically cap your rates... a rate of 30000 is a minimal value to be able to play and receive information, especially when there's action going on: IT'S VERY LOW
Be cautious with cmdrate as it is capped by your number of fps (as the engine of CSS was designed this way :p)... also verifiable: if you look at the netgraph: your cmd (line in: the number on the far right) will never be greater than your fps
For updaterate, unless you really have a bad connection like 56k, set it to 100 for a server with a tick rate of 100 and 66 for a 66
In short, lower your cl_cmd to 80 or 70 if you have low fps
Get as close as possible to the server values for cl_updaterate 100 or 90 or 66 (for a 66 server)
Raise your rate to at least 30000
Monitor your netgraph to fine-tune and don’t have too much of a gap between your cl_upd and cmdrate otherwise it becomes untouchable
And above all, vote to ban the 7500, 30, 20 settings that we see too often
Happy fragging and testing this is the best way for everyone
Be cautious with cmdrate as it is capped by your number of fps (as the engine of CSS was designed this way :p)... also verifiable: if you look at the netgraph: your cmd (line in: the number on the far right) will never be greater than your fps
For updaterate, unless you really have a bad connection like 56k, set it to 100 for a server with a tick rate of 100 and 66 for a 66
In short, lower your cl_cmd to 80 or 70 if you have low fps
Get as close as possible to the server values for cl_updaterate 100 or 90 or 66 (for a 66 server)
Raise your rate to at least 30000
Monitor your netgraph to fine-tune and don’t have too much of a gap between your cl_upd and cmdrate otherwise it becomes untouchable
And above all, vote to ban the 7500, 30, 20 settings that we see too often
Happy fragging and testing this is the best way for everyone
Just a small mistake: 1024 bytes = 1 KB (not 1 MB), so 1048576 bytes corresponds to 1024 KB, which is 1 MB.
ben put that instead: cl_crosshairscale 2500 (small crosshair) cl_updaterate 100 cl_cmdrate 100 rate 30000
I've got a high PING issue in Counter-Strike Source that's causing lags. How can I fix it? Thanks in advance =) (I'm using Windows XP)
No answer is correct and most are wrong. I invite you to read the article on VaKarM.net, which is the most visited French site for news about Counter-Strike Source.
Hello, since I've had Windows 7, my Counter-Strike Source doesn't work like it did on XP. I start CSS and when it's time to choose a team, terrorist or counter-terrorist, the image freezes and doesn't move. I have to restart my PC in order to play. When I restart my PC and start playing, everything is fine, but at the moment of changing maps it happens again, and again I have to restart. If anyone has a solution, please explain. Thank you.
Say, is it normal that when I want to change my cl_rate, the console tells me it's an unknown command? ^^'
"cl_rate 25000 This is the upload speed of the game's data. That is to say, the speed at which you send information to play securely on the server. The value of this command must be equal to the value of the rate command. "
Is cl_rate an unknown command? That's what the console is telling me...
Is cl_rate an unknown command? That's what the console is telling me...
dust 2, set cl_updaterate to 101, not 30,000 ^^'
However, I have a little personal question, the command cl_rate is not recognized and when I look at the net_graph the sent tickrates are at 25.
Well, it allows me to have between 0 and 3 choke but it seems a bit low as a value. Has the command been incorporated into rate or how does it work?
However, I have a little personal question, the command cl_rate is not recognized and when I look at the net_graph the sent tickrates are at 25.
Well, it allows me to have between 0 and 3 choke but it seems a bit low as a value. Has the command been incorporated into rate or how does it work?
- 1
- 2
- 3
Suivant
Your thing must be very good but it doesn't suit me, so I would like to reset my original settings please, how do I do that? Thank you in advance...
please please please how do you set up the console and where is the rate please :) thanks in advance and for the ping when it is too high how do we decrease it?