urk?!?

I've been using the DSP-500s since they came out. They are absolutely fantastic. You can hear everything and with incredible clarity. I'd suggest that you NOT use any of the "filters" or "equalizer" settings for either the microphone or the headphones though. While they may make things sound a little better, they tend to mask the high end sounds with all the bass they put out.

http://www.gotfrag.com/?node=feature&id=19&x=BBF8D85A Great article on how money works in the CS game.

Orbital, Thanks for clarifying. You're 100% right. I didn't read your guide sufficently, and after looking into it a bit, your follow up explanation is also correct. The server side params ARE what determine what your effective rate is. On the flip side though, it really doesn't make much of a difference what your rate is once you clear 10000. I tested that on a bunch of different servers ranging from DOH, to 3d (in texas) to CA, to a euro server (where playing with a 100+ ping is equivalent to self-mutilation... gawd those cats are good). At 10k+ rate, it really becomes a mental issue if you aren't experiencing choke. There's no percievable difference in how your shots register or not... and I'm mighty finicky about phantom shots. On another note, if everyone on the server has their rate set to 20k and the server can only handle 7500 or 10k, then it _WILL_ cause choke on that server. The server is going to expend cpu cycles rejecting packets that exceed it's buffer/param size. That causes delayed responses from the server, ergo, choke/lag. Again, this is my experience. I've been in more than one scrim/match where everyone had their rates tweaked to max it out, and everyone's connection has been choked to timbuktu and beyond, including spurts of lag and ping spikes exceeding +150ms due to the config tweaking. I'm not too sure if you were agreeing with me or not on the cl_cmdrate/updaterate, but those are (in my experience), best set to coincide with your FPS avg/min/max. The reason being that you want to have your commands (ie, click to shoot) sent to the server at the same rate that you're percivieving them on your screen. Ergo: "Frame 1" I see the target "Frame 2" I click to shoot (assuming I actually have lightning reflexes) "Frame 3" My target dies from a headshot because the server recieved my shot in Frame 2. If your cmdrate is not comparable to your max_fps (and the actual FPS that you experience in game), then you're going to get a shot that happens in Frame 3 or 4 or even 5... and the server will not register your shot where you think you put it since the target has moved 2-3 frames since you fired. Updaterate is the reverse flow (unless I'm mistaken, and pls correct me if I am). It's the server communications to your client. Ergo, you want that to be set roughly the same as your cmdrate. One last note, I owe you an apology for not complimenting you on your guide earlier. I saw information (re: the various rate settigns) up there that was basically accurate, but didn't have a couple things taken into consideration and I posted in haste. rotten P.S. Having gone thru this exercise with you, I've since adjusted my config.cfg to rate 20000. I adjust it in game as needed. cl_cmdrate and cl_updaterate are still set at 75. P.P.S. Another sidenote, on Gf4 cards, the HL engine actually runs better under 32bpp. It's not a perceptible difference either way, so it's really immaterial (like Orbital said). Check madonion for details.

Breakout...

Cat, apologies, you posted this on another board and I forgot to answer you Put: voice_loopback 1 in your config. I strongly recommend against it tho... I find it extremely distractign sicne there's a delay associated with it.

(Sorry fatty, I posted here before you were so nice as to give me access to the MCC forums without having to beg... maybe you shoulda made me beg ;/) /agree with Cane. The money amounts are a huge difference. It's entirely possible for the entire CT team on a CS map to have awp's by round 2. That's just unfair. A bomb planting and successful bombing, by comparison, is pennies.

Orbital, Not sure if you being beligerant there deliberately, but you came across as terse. Perhaps I could have introduced my post as "In my experience" --which is exactly what I was relaying. You may not experience choke at a rate of 20000. But I guarentee that I do. Ergo, in my eyes, I _have_ proven it. Rate above 20000 does choke the server, perhaps not for you, but definately for other players. It's also pointless unless you're on LAN. You're just increasing the window size for the number of packets that the "crappy Q2 engine" can use if it needs to. I didn't say anything at all about what the max_rate was, so I'm sure you weren't referring to that. As for the cl_ rates, the information I relayed is common knowledge after one of the HL devs posted that information several years ago during beta 1.3. I'm sure you can find the post on it somewhere on the CS forums if you want to double check. Aside from that, your guide was correct in what you conveyed. I was adding additional information to it that indicated that you didn't need to have the variables at different values. Either way, thanks for posting the guide. And thanks for being open-minded. rotten. P.S. Not sad. Just glad.

Rate over 10000 clogs the server under 1.4+ It doesn't do anything but introduce more choke. You should set your cl_cmdrate and cl_updaterate to something that's divisible aroudn the avg for your FPS in a good firefight. IE if you get 60fps you should set BOTH variables to 60. if you get 75, run at 75. These variables change some from server to server as well. If you start seeing choke in your netgraph (set this to 3 for onscreen display), then you should reduce the rate by 100 increments until it clears up. I set my config to readonly since alot of HLguard and WWCL servers will overwrite yer config when u quit HL.

urK?!? Just putting in mah voice to remove them from next season. CS maps unbalance the match from a money perspective... plus they just suuuuuuuuuuck

LoL... urK?!? Looking forward to the match with S!d. I'll chime in with some predictions... even tho there's a match going on atm =b. DOH 20 DW 10 Mmmm 16 DLM 14 MwR 20 S!d 10 (Ignore this one... I'm biased = TF 18 CsLs 12