[citation][nom]Cleeve[/nom]Perhaps, but in your original post you complained about cutting the frames-over-time chart off at 60 FPS. There's no reason to have a chart that shows a combo achieving 200 FPS, and it certainly wouldn't show any info about micro-stuttering.
I never asked for 200fps tests.., all I asked for was to have the rest of the chart. Seriously, what is the point of cutting a chart in half? You like looking at charts that are cut in half missing half the data? Why not just show it? And yes, graphing out the FPS on a line graph can give you a clue about microstuttering. They actually used line graphs in the article on tomshardware using line graphs.[/citation]
I never asked for 200fps tests.., all I asked for was to have the rest of the chart. Seriously, what is the point of cutting a chart in half? You like looking at charts that are cut in half missing half the data? Why not just show it? And yes, graphing out the FPS on a line graph can give you a clue about microstuttering, if you know what to look for. They actually used line graphs in the article on tomshardware about microstuttering. And, exactly as I stated, this article does nothing for a gamer with who games at super high resolutions, you can't just say because it gets high FPS on mid range resolutions it's going to be fine at high resolutions. Thats why they benchmark games at high resolutions, some games, a lot of games actually, just act funny when they are set to higher resolutions. Thats one reason I even read articles on toms, so I get an idea of how games will run on a setup similar to mine, or if I plan to upgrade, to see how it performs on the latest hardware. And since higher resolution gaming is much more common then it was a few years ago, i'd assume that they would test it on higher end systems with higher resolutions. Honestly, if I wanted to play on a console, i'd just buy a console. o_o