If I don't cap screen tearing is actually unbearable

I've got it capped at 289, hasn't let me down yet.

Up to you really you have to play with it and find something that works. Like you say 50% of people have to have it or the game is just fucked and some other people have to keep it uncapped for the same reasons. It seems to differ from computer to computer.

Your fps cap should be the refresh rate of your monitor multiplied by a whole number.

Ideally you'd want to use the highest possible fps cap multiple that you don't frequently drop below.

So lets say I have a 120hz monitor and usually get around 300+ish fps. I'd want my refresh rate multiplied by 2 so I get a cap of 240. This way I'd have a almost always smooth but still responsive experience as my fps wouldn't drop below my cap and give as much tearing. Unlike if I set mycap to 360 where I'd always hover just below it and get a lot more tearing.

No
Source engine gets input lag if you are constantly hitting your FPS cap.
That said capping it at 999 is acceptable to prevent glitching on jump maps ect.

Source doesn't get input lag from having consistent fps, unless you are retarded and play with vsync but that's different from an fps cap.

idk I noticed the game micro freezing/stuttering/whatever whenever i capped my fps, uncapped worked fine though

Capping FPS gives you input lag no matter what engine you are using or what game you are playing because there is a longer delay between when the last frame was rendered and when the monitor displays it. That being said, it is much better to have a very slight input lag than to have your fps constantly dropping. That amount of lag is also so tiny that it won't make a difference if your fps cap is very high.
If your fps don't drop by more than 10-20 fps then you probably don't want an fps cap, otherwise put one at the highest fps you can consistently get.

you didn't think of trying it out in-game?

x

my game feels smoother when it's capped but I have 60hz and terrible reaction time so it might just be different for everyone

If you don't drop below 300 then cap it at 300

deetr im proud of ur first seriously articulated post that was well executed, great job, keep it up

i've never had a problem with or without capping

Uncapped has felt better on the diff pcs I've used for tf2 for 4 years.

I used to have integrated graphics on my crappy computer. At that time I capped my fps because my fps was all over the place, and capping it gave me some consistency. Now that I have a GPU, I don't cap it.

http://www.teamfortress.tv/26679/does-fps-max-cause-input-lag-when-turning

I would not use 288/289. Try using 720, best for me (144hz)

http://www.teamfortress.tv/23801/120fps-on-60hz-monitor

I don't use a FPS cap and if I did it would be around 999 to avoid the timing issue.

My notes on my config were a reflection of when ever I tried using FPS caps I felt like I was be inhibited the entire time I was playing. It always happened to me regardless of using a 60Hz IPS or 144Hz TN. Which led to my reasoning that FPS caps should be used either to achieve more consistent temperatures for your CPU (mostly laptops) or to prevent the speed issue at over 1000fps. Honestly I'd rather deal with my variable FPS that's consistently over 220 in HL mid fights with no cap at all than have a 220/250/300 cap that being said some people do prefer a fps cap cause they're basically guaranteed the same experience of input at all times, even if it's technically worse.

why? what's the reason people cap their fps at refresh rate x2 + 1?

x

i read somewhere that higher FPS gives you more consistent (better) hit detection

no, because hit detection is done server-side not clientside