CS:S config editing ok?

[PurdueRy]

I see lots of people change:

cl_updaterate "60"
cl_cmdrate "60"

To different values. What are the defaults for this and is this considered cheating? I don't want to do something that is. I occasionally experience stuttering in gameplay that is not linked to anythink in particular so I was looking to see if this would help. Any help is appreciated. I also don't see all the settings mentioned in some of the tweak guides...have they been removed so people don't edit them?

 

[PsharkJF]

No, it's not cheating. It's optimizing your client for your connection.
Now, ex_interp (cl_interp on source?) THAT's cheating.

Edit: I believe the default for updaterate is 20 and the default for cmdrate is 30. You should set updaterate to as high as possible without loss (red dots on net_graph 1), however most servers will limit this to ~20-30. Set cmdrate to your average FPS, and I believe servers will limit this too - I think 45 is a pretty standard limit there.
FYI, i'm not speaking from CS or CS:S, I'm speaking from a very heavy TFC background

 

[PseudoKnight]

Ex_interp is NOT cheating. CAL has players set it to 0.01 and the default is 0.1. It's used to smooth animation between packets and to even compensate for packet loss. 1/updaterate is what I typically recommend.

Like Pshark said, you want to set the updaterate as high as you can (100 max) without getting loss. Also, if the server tickrate is 33 there is really no reason to go higher on your updaterate. As for the cmdrate, you want to set this to your average FPS or the average server FPS, whichever is lower.

If you want to figure this stuff out on your own, here's a good resource to learn how it works:
http://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking

 

[PurdueRy]

will changing any of those get me banned and if so which ones so I make sure I don't adjust them

 

[PsharkJF]

ex_interp, back on WON, had the net effect of widening every enemy hitbox, plus enabling the user to hit unseen targets around corners.

 

[hdeck]

you can't get banned for changing your rates or interp.

 

[PseudoKnight]

Some admins will ban you if you set your cmdrate below 20. (it's considered an exploit by many) So, don't do it.

ex_interp, back on WON, had the net effect of widening every enemy hitbox, plus enabling the user to hit unseen targets around corners.

I never heard this. Was there solid evidence to back this up? Either way, cl_interp is fine to use in CSS.

(it is CL_INTERP in CSS and EX_INTERP on CS 1.6)

 

[PsharkJF]

Originally posted by: PseudoKnight
Some admins will ban you if you set your cmdrate below 20. (it's considered an exploit by many) So, don't do it.

ex_interp, back on WON, had the net effect of widening every enemy hitbox, plus enabling the user to hit unseen targets around corners.

I never heard this. Was there solid evidence to back this up? Either way, cl_interp is fine to use in CSS.

(it is CL_INTERP in CSS and EX_INTERP on CS 1.6)

Not solid. But I guess every major TFC league banning it provides some credence

Anyway, changing interp to a lower value than everyone else's, and using a "spray" weapon like the HWGuy's AC, made the AC ~100% accurate, never missing a shell. (I'm not talking point blank range, I'm talking medium range with parts of the "spray cone" not touching the hitboxes)
Furthermore, if you turned interp up, the hitboxes "lagged" further behind the model, and if someone was moving behind a corner, you could shoot their lagged hitboxes, get hits, even though the server says the guy is around the corner. In other words, interp had the effect of moving where the hitboxes were in comparison to the model.
In fact, Steam TFC hitscan was initially said to be like "if everyone had interp".

Hm, makes me want to install 1.1.1.0 again and try it out.

edit: TFC is the land of the engine exploit From tfc.sta-league.org :

Client Settings:
1) The use of cl_lw or cl_lc with any value other than 1 is prohibited from STA. Any player doing so will be subject to discipline from STA. As of the most recent patches, these settings are disabled, however the rule remains as a reminder and a standard, pending any future options/settings changes that have yet to be discovered regarding latency and network issues.
Reason: Anti-concing

2) Fullupdate, axis locks/-mlook, forcecenterview are all prohibited in regards to being used as an anti-conc exploit.

Reason: Anti-concing, again
3) Pitchup and pitchdown settings are to be capped at 104.5.

Reason: Pipedown (shoot pipe straight down as demoman), it's pretty lame, but not a cheat.

tfleague.com ;
ex_interp MUST be kept at the default setting, which is "0.1"

edit 5billion:
http://tracker.thecatacombs.net/?steamid=2166765&ex_id=1&name=&ip= (me on WON)
http://tracker.thecatacombs.net/?steamid=STEAM_0%3A0%3A3116&ex_id=1&name=&ip= (me on Steam)

 

[hdeck]

Originally posted by: PseudoKnight
Some admins will ban you if you set your cmdrate below 20. (it's considered an exploit by many) So, don't do it.

ex_interp, back on WON, had the net effect of widening every enemy hitbox, plus enabling the user to hit unseen targets around corners.

I never heard this. Was there solid evidence to back this up? Either way, cl_interp is fine to use in CSS.

(it is CL_INTERP in CSS and EX_INTERP on CS 1.6)

not true. interp affects hitbox location, not size. the hitting targets around corners has to do with shooting ppl as they try to run for cover and still hitting their lagged hitboxes after they are behind the wall.