[...] [...] pc != lcd The work is done by a hardware upscaler in the monitor, not by the pc. It won't affect fps at all. The upscaler will add latency though. @Tseini: idle states are controlled by load not by resolution. Also I'm guessing you changed the resolution in TF2, with the desktop resolution still being native.

also do not understand why ppl downscale their resolution on a LCD... if you change the resolution ingame the pc has to recalculate everything AGAIN to get the lower resolution.

the lcd-screen has to interpolate the information so you can use that "custom" resolution which isn't native :) (fact)

I am aware of interpolation and its resulting loss of image quality on LCDs. But what does that have to do with your (until now unsourced) claim that the PC will render an e.g. 1080p frame regardless of the LCD's resolution and then downscale it to 720p, effectively giving a worse performance than running your LCD in its native resolution?

[...] Since statements like "the human eye sees about 100 fps" don't really apply and are wrong, it's difficult to give a hard limit on how many fps are enough. I would wager a guess and say that anything above 200 fps (stable fps, that is) makes an insignificant difference and is down to personal preference and imagination. But we had that discussion before, schocky :) [...] Are you claiming that your PC will render frames in, say, 1080p regardless of the resolution you are running your monitor at? That is most definitely not true. Lower resolutions mean fewer pixels to render, which in turn increases the performance.

[...] Isnt the "perfect" lock fps*2+1 or is that just a myth ?

myth 4sure. one reason to use a higher fps_max is that you will get a faster response time.

also do not understand why ppl downscale their resolution on a LCD... if you change the resolution ingame the pc has to recalculate everything AGAIN to get the lower resolution. native resolution ftw[...]

[...] why would you use such a number? ... with that you get screen tearing - with vsync on not. and again: why would you use vsync 1 if you get HUGE input-lag? try fps_max 300 @60hz and 600 with 120hz. Dunno if I am the only one but if I multiply the hz by 5 I do not get screen tearing at all. Even can see the difference between (fps_max) 599 and 600 ...

[...] why would you use such a number? ... with that you get screen tearing - with vsync on not. and again: why would you use vsync 1 if you get HUGE input-lag? try fps_max 300 @60hz and 600 with 120hz. Dunno if I am the only one but if I multiply the hz by 5 I do not get screen tearing at all. Even can see the difference between (fps_max) 599 and 600 ...