Originally posted by: ariafrost
I used to run a 66 tic 18 slot fy_iceworld CS:S server. Maybe I should start it up again...
Originally posted by: KeithTalent
So I created an autoexec.cfg with the changes in the OP and I think it is working out well so far. Last night I was playing for a while and I felt like my shots were hitting a little better than usual.
I have enabled the graph and am watching it a bit while I play, but to be honest I am not really sure what I should be looking for. I think I am close to 0 choke most of the time, which I think is good from what was posted above, but as for the rest of the stuff I am not quite sure.
Also, if I am playing the game and want to switch servers, do I need to go and change my autoexec file every time if I am, for example, switching between a 66tick server and a 100tick server? Is there an easier way to do this?
Originally posted by: AnMig
Is there any downside to using this?
or will this benefit you regardless of the server tick rate (30,66,100)
If its not going to do any harn then I will give it a go.
do you need to create the autoexec.cfg file anywhere in particular?
do you need to initiate this before playing ?
Originally posted by: AnMig
I think this really works. I had some stuttering issues when I joined a server that I was pinging 100's. Made me kind of dizzy.
But joining servers under 70 ping does not show this.
I am actually playing better, I now usually get K ratio 1.5 someitmes 2.
It could be my imagination but I think my bullets are actually hitting my opponent.
Good post.
Originally posted by: rstrohkirch
On the graph you'll have two lines, one labeled in and one labeled out. The number at the end of these lines represents your packets coming in and going out. You'll want to look at the incoming packets to know what kind of tick the server is currently running at.
Couple examples, I jumped on a DoD:S server yesterday...some assassin something...that said 100 tick in the subject line. Well, they had the server set at 20tick
Another example is the server I generally play on. It doesn't advertise a tick rate but it caps out at about 60ish and will generally be between 45-60.
You don't have to edit the autoexec and can just leave the settings alone. If you want to change them on the fly to fit the server your on you can do cl_cmdrate for outgoing related to choke and cl_updaterate for incoming and related to loss. Just type those commands in the console and change to the number thats more suitable.
Originally posted by: GundamSonicZeroX
Isn't this kinda unethical?
Originally posted by: 6StringSamurai
Originally posted by: tuteja1986
CS addiction has too stop , but WOW addiction is worse.
That has what to do with hit registration? btw I am worse than addicted, been playing CS since alpha stage...
Originally posted by: Tizyler
Originally posted by: 6StringSamurai
Originally posted by: tuteja1986
CS addiction has too stop , but WOW addiction is worse.
That has what to do with hit registration? btw I am worse than addicted, been playing CS since alpha stage...
Counter-Strike had no alpha stage.
The first release was Counter-Strike Beta 1
GG
Originally posted by: 6StringSamurai
Originally posted by: Tizyler
Originally posted by: 6StringSamurai
Originally posted by: tuteja1986
CS addiction has too stop , but WOW addiction is worse.
That has what to do with hit registration? btw I am worse than addicted, been playing CS since alpha stage...
Counter-Strike had no alpha stage.
The first release was Counter-Strike Beta 1
GG
So you knew Gooseman and Cliffe too? While your right, there was no official alpha release to the general public, there was an alpha version, and yes I played it.
From what I understand, choke means you are sending more data updates than the server can process.Originally posted by: HeroOfPellinor
So, doing this causes my client to "choke". But as far as I can tell, that's fine.....it just means you want more than the server can provide. Is that correct? I'm using netgraph 3 to monitor it.