CS:S Tweaks

Just takes time... I used to be godlike with mouse accel on playing with a MS Intellimouse Explorer Mouse. It just takes time to get used to no mouse accel. You'll have less trouble switching between games like CS/HL, which utilize windows mouse accel settings, and Quake series/Battelfield series that don't use windows settings. Turn it all off and it's one less thing you have to get used to.

vsync... such a highly debated issue... LCD users... keep it on... yeah you won't see the 235412341234 fps that you get with it off, but your monitor won't display it anyways. CRT users... why don't you have a beautiful LCD yet? Seriously tho... them hardcore games who are about winning... CRT playing at 640x480 with pegged fps cuz their graphics are turned way too low so that it looks like you're playing wolfenstein 3d. Even then... the experts say to cap your fps to your monitors max refresh rate at that resolution which is why everyone used fps cap of 120 when I was big into Rocket Arena back in the day. Max refresh was hmm... 120 Hz! LCDs... all pretty much 60 Hz at the native resolution.

Yeah you may get 300 fps when you're staring into a corner with no one on the server, but the fluctuation say from 45 to say 180 fps is what causes stupid shit like "ghost bullets" because the range fluctuation is so great that when it does drop from 200 down to 50 Valve's wonderful "no lag" lag compensation doesn't have a steady flow of info for it's predictions. If something's erratic how can you predict it? Capping decreases that fluctuation range and basically evens the flow and relieves stress on your vid card. All that means is that if you have a badass video card you'll have 100 fps at shitty graphics setting and 100 fps also at ridiculously high graphics setting. Which translates into very consistent game play.

I'm sure everyone's experienced going from playing on 15fps to playing on a steady 100 fps computer. Seems like your sensitivity went up when it actually stayed the same right? What capping does for you is keeps your fps from having such a large fluctuation range from say 50-180 so you don't have to get used to such a wide range of varying "smoothness." Effectively giving you consistent game play.

Pre-Source, Counter-Strike was capped at 100 fps. You couldn't go higher than 100 fps. It just didn't allow it. Thus there was no reason to bring your rates higher than 100. cl_cmdrate was always recommend to be equal to your average FPS. Peaked at 100? Rates at 100. That's why now you can set cl_cmdrate up to 300 in source. Because Source actually goes that high. If the server would allow it you could set your cl_cmdrate to 300. 99.99% of all servers are capped at 100 anyways so you can't send more than 100 proverbial commands per second so why fps_max > 100? No reason. Simple. People try to make it all convoluted and explain the mathematics behind it and it just makes you confused.

cl_updaterate you ask? sv_maxupdaterate is usually capped at 100 on 100tic servers and obviously capped lower on 66 and 30 tic servers. Servers tend to run around 1000 fps. Why not get all the info you can to make an accurate picture of player positioning if your connection can handle it? You can set the server's sv_maxupdaterate to 300 per client, but that's just bad bandwidth and resource management. Only for a LAN or something.

So where the fuck did 101 come from? Why does everyone use it? And why do some use 100 instead of 101? It came around cuz some fucktard was sitting around comparing his fps peaked at 100 to his rates which were also set at 100. BUT Netgraph showed him that his rates were sitting at 99.9. WTFBBQPWN?!?!?!!!11ONE!!1 That wasn't good enough though so he tried 101 and it sat at 100 on netgraph. There's no reason for it to be 101 as opposed to 100. Just a mental thing. And now you got CAL servers capped at 101 101 25000.

And that's that... I'm so damn long winded =\