Wtf people. I'm saying don't use -dxlevel 80, it seems to be very buggy and unstable for most people. -dxlevel 81 is fine.

Dx 81 is almost completely unsupported these days, the update yesterday was the first time I've seen an update for dx 8 in a while. But ex 8.0 has long been deprecated. Don't use it.

Has anyone tried using the tf_hud_show_servertimelimit 1 command yet? I can't get it to display on my hud (broeselhud) so I'm guessing that my hud needs to be updated/modified to show this?

My hud is packed into a vpk if that makes any difference.

Yeah whenever I've used it, I always screw up the "uber" by not cycling through the invulns fast/accurate enough. If there was a way you could bind a specific key to only switch to one of the invulns, that would be more precise/easier. However, it would require 3 extra keys to be bound to a command.

Mat_phong 0 is absolutely incredible. I'm in love with it.

It's another 4 hours until my teams match tonight, but with an update nearly an entire gigabyte large, will that affect the updating of the client?

edit: someone also mentioned to me, that considering the size of this update, and valve's history with updates, it's not unreasonable to be concerned about another update coming out in a few hours, to fix/patch something they forgot messed up in the original update. Obviously, this would complicate updating the ESEA client in time for matches.

Is it just me or does the bleed screen not look THAT different?

WOW. I might just try dx8 again now.

This sounds pretty neat, like an overlay of the server time left? As in like an additional timer?

Thank god, this was much needed

Why? This seems excessive as hell. :(

This also seems excessive, combined with the marked for death addition. Why is valve nerfing the fuck out of this weapon AGAIN?

Freaking awesome!

I think it's safe to say that the difference in fps from the dx9 frames to dx8 is very small, and the difference between the high frames and Max frames configs is even smaller. Indeed the blocky textures no longer work, but if your fps has taken that big of a hit, it likely is due to something else.

Is it just me or did anyone else cringe when he kept saying "can I check my ____ 'quick?'" It's as if he replaced "real" with a short pause. I don't know why that bothered me so much.

That's good to hear, it's not just me then. Be sure to keep the sensor clean. If you haven't yet, get a good flashlight, shine it into the area where the sensor is, and look for any debris like hair. To get things out, I use a q tip, and the tip of my spudger sometimes too. Hope the new settings make it playable again for you. Good luck.

No. That's not accel. The placement of the sensor is different than most mice but accel is not a physical entity, accel comes from software.

I actually own a g500 and also happen to use a cloth pad. I'm used to it though.

I would like to let everyone know, however, that I've found a couple of things that seem to mitigate the "weird" tracking feeling.

I used to swear by 800 dpi. I think that this if from when I used an optical sensor. I have this [perhaps anecdotal] feeling that optical sensors work better at low dpi than laser sensors. A while back I switched to 1600 (keep my sens the same by cutting my in-game sens in half) and it feels much, much better.

But what I've found helps even more, is using a polling rate of 333hz.

I swear it's not a placebo. 1000hz, for me, just feels waaaay to weird, and like there is some weird ass accel going on. 500hz for me is tolerable, but, when switching to 333hz, tracking feels damn near perfect.

I know that a high polling rate like 1000hz uses cpu processing, so perhaps my personal hardware affects my ability to use 1000hz. Either way, if you use this mouse, and you use a cloth pad, I highly recommend trying a polling rate of 333hz. Even if you don't think you have a problem with this mouse and/or a cloth pad, I'd like you to try this anyway and see if you notice a difference, just for my own curiosity.

http://www.esreality.com/index.php?a=post&id=2024663

If your windows multiplier is anything other than 1 (6/11) then you are forcing acceleration into your pointed speed.