11 Jul 10, 06:28AM
Not really... You can't see more than the refresh rate of your display, which on LCD is 60 to 75 max. More FPS than that means 2+ frames within the same display image, eg shearing type of distortion.
Also, that whisper link above reeks of biased nonsense; in particular, the "claim" towards the end of the article (about pilots seeing an image that was flashed for 1/200th of second) is just crap - that's persistence of vision, ie an image on retina takes a while to fade (around 40-50ms iirc, which is why cinema is happy with 24 fps). I searched for the original article and that guy wrote another one where he makes an even purer BS claim - that LCDs react instantly while phosphors don't. That's just... That's just degenerate. See response time wiki or just ask yourself why all (decent) LCD display specs quote response time.
Playing and watching are not the same thing though - increased responsiveness (lower latency) may well have a perceivable quality, but we're far more sensitive to variance as we can adjust to stable delay within reason. So a better test would be watching the same demo twice with different /maxfps (first few minutes should be enough). And to make sure you're not just practicing your placebo skills, test randomly a few times by putting if (rnd (2)) [maxfps 75] [maxfps 200] in your autoexec.cfg.
Also, that whisper link above reeks of biased nonsense; in particular, the "claim" towards the end of the article (about pilots seeing an image that was flashed for 1/200th of second) is just crap - that's persistence of vision, ie an image on retina takes a while to fade (around 40-50ms iirc, which is why cinema is happy with 24 fps). I searched for the original article and that guy wrote another one where he makes an even purer BS claim - that LCDs react instantly while phosphors don't. That's just... That's just degenerate. See response time wiki or just ask yourself why all (decent) LCD display specs quote response time.
Playing and watching are not the same thing though - increased responsiveness (lower latency) may well have a perceivable quality, but we're far more sensitive to variance as we can adjust to stable delay within reason. So a better test would be watching the same demo twice with different /maxfps (first few minutes should be enough). And to make sure you're not just practicing your placebo skills, test randomly a few times by putting if (rnd (2)) [maxfps 75] [maxfps 200] in your autoexec.cfg.