These settings are for 128 tic server. c2 matchmaking is still using 64 tic. also cl_interp should be set to 0 it will automatically set the right interp for your ping. The correct settings are: // Rates rate "500000" cl_cmdrate "67" cl_updaterate "67" cl_interp_ratio "1" cl_interp "0" cl_lagcompensation "1" cl_pred_optimize "2" cl_predict "1" cl_predictweapons "1" cl_smooth "0" cl_smoothtime "0" cl_wpn_sway_interp "0"
There is a new update today and valve have fixed the default have This is my autoexec now autoexec.cfg: r_fullscreengamma 2.6 cl_updaterate 128 (probably useless but w.e) cl_interpratio 1 (2 - above 60 ping/unstable connection)
@@TheDarkelm I will explain the settings. Ive run a counter-stike server for a long time. rate = your ISP Mbps max is 6.2 Mbps - rate 786432 cl_cmdrate and cl_updaterate are settings set server side and your client needs to match the setting for best accuracy. CS2 match making servers are still 64 tic. That is why we are setting both to 67. cl_interp_ratio will multiply the cl_interp value by 1 or two cl_interp = the avrage ping in the server you are playing. so if you have 15ping you set cl_interp to 0.015625 or 30ping will set 0.03125. you can change interp ratio to 2 to have 60ping and 30ping from the interp values. back in the day you would need to match your ping and interp... but now you can set to 0 and valve will auto set it.
Thanks man. Appreciate the effort👍🏼.
These settings are for 128 tic server. c2 matchmaking is still using 64 tic. also cl_interp should be set to 0 it will automatically set the right interp for your ping. The correct settings are:
// Rates
rate "500000"
cl_cmdrate "67"
cl_updaterate "67"
cl_interp_ratio "1"
cl_interp "0"
cl_lagcompensation "1"
cl_pred_optimize "2"
cl_predict "1"
cl_predictweapons "1"
cl_smooth "0"
cl_smoothtime "0"
cl_wpn_sway_interp "0"
There is a new update today and valve have fixed the default have
This is my autoexec now
autoexec.cfg:
r_fullscreengamma 2.6
cl_updaterate 128 (probably useless but w.e)
cl_interpratio 1 (2 - above 60 ping/unstable connection)
@@TheDarkelm
I will explain the settings. Ive run a counter-stike server for a long time.
rate = your ISP Mbps max is 6.2 Mbps - rate 786432
cl_cmdrate and cl_updaterate are settings set server side and your client needs to match the setting for best accuracy. CS2 match making servers are still 64 tic. That is why we are setting both to 67.
cl_interp_ratio will multiply the cl_interp value by 1 or two
cl_interp = the avrage ping in the server you are playing. so if you have 15ping you set cl_interp to 0.015625 or 30ping will set 0.03125. you can change interp ratio to 2 to have 60ping and 30ping from the interp values. back in the day you would need to match your ping and interp... but now you can set to 0 and valve will auto set it.
@@YTMS879 Thats really great information Thanks for sharing
Thanks :) pls give all commands in discp