Hi Duff-Man

If you read all the technical stuff that you wrote you may understand how a simple layman like myself is left scratching his head at what the heck you are actually saying
I'm sorry if my writing style is somewhat unintelligible. I'm used to writing articles for scientific journals, or conferences, or technical reports. Sometimes it is difficult to express complex concepts in a way that a "layman" will understand. Sometimes simple analogies can't capture all the relevant facets of a technical problem.
What I would say is your work so far and the conclusions drawn are perhaps half baked . . . I certainly have not seen what I would consider "compelling" evidence that a normal layman needs concern himself with
I have to say I take exception at this statement. I have made a reasonably formal analysis of the phenomenon. You have already explained that you don't understand everything I have said, so to dismiss it as "half baked" is unfair. Please understand the entire set of points before dismissing them. If you have specific questions then ask them, but don't dismiss what I have done simply because you don't understand it.
You are welcome to undertake your own investigations into the phenomenon. No-one is stopping you.
. . . the worry I have is two fold, firstly your making claims on the Internet that are perhaps being misinterpreted, this "microstutter" scenario is being exaggerated to some extent thanks to the power of the Interweb-chinese-whispers-rumour-mill (9%-30% reduction . . whisper whisper . . 10%-30% reduction . . whisper whisper 20%-40% reduction etc) . .
I measure the quantitative effects, and report them. As with all data reporting, some people will misunderstand the results and their implications, and as a result, unwittingly spread misinformation. There is nothing that I can do about this. I can only report the facts - I can't force everyone to understand them.
The second thing is I am wondering to what extent some of this could be due to the . . . if you read post
#56 you will see a short post by me in reply to a friendly forum users video he posted as proof that "microstutter" was real . . . if you watch the video linked in the post and then read my reply I wonder . . . if this "judder, judder, judder" thingy to some extent being generated by the very tools you are using to measure the frames?
Just ignore the video post - it's ridiculous. The video is captured at 24fps. How can you observe a phenomenon that occurs over timescales much less than 1/24 th second? You can't... It isn't something you can see on a video.
Can I assume that in the sake of thorough Scientific method that you disabled fraps and any diagnostics tool that interact with the PC at a hardware level (CPU-z, RiverTuner etc) and then did some runs again to observe if you could percieved any issue with the naked eye? . . .
There is a good chance the very tools you are using to "observe" could be the tools creating a problem?
Yes to the above, but that is not at all scientific. It is 100% subjective and so is irrelevant. But yes, I have observed the phenomenon in all its forms without FRAPs etc.
You say the problem increases as GPU load increases? . . . this should be very easy to set-up and "observe" any differences (tool-less and with the nake-eye ) by doing different runs with more and more levels of AA and maybe working out the right balance of texture settings to push the average framerate down to 60/50/40FPS etc to see if your theory stands up to the naked eye . . .
I have tested many configurations as far as CPU limitation goes. If you have read my threads then you know this. As far as "naked eye" assessments go - these are subjective and irrelevant from a scientific point of view. But yes, if you can give enough load to really make the GPU crawl, you can actually see the framerate irregularity.
This has got to be sorted one way or another and clearly moved into either the black area or the white area . . . videos have to be made and one way or another the case closed . . .
Videos WILL NOT show the microstutter phenomenon. They only take a snapshot of the output every 1/24th second or so. MS occurs much more rapidly.
If this was Quantum Physics then I could understand it taking a bit longer to prove eitherway but its not . . . . can you get people to disable any FPS measuring apps and 3rd party software like your program and CPU-z etc and try to test again with the naked eye! . . .
I have demonstrated the phenomenon exists (as many others have before me), and I have used analytical data to describe the scenarios in which is has an effect, and the magnitude of this effect. If you don't consider this "proof" then that's no issue of mine. Run all the tests you like to convince yourself one way or another - all the tools are available.
What you are claiming clashes with many many people that have stated their SLI experience is great? . . . are they running v-Sync maybe or is it off? . . . are they running at 80FPS maybe and can't tell due to high FPS or are they running 40FPS and can't tell because there is no problem? . . . is there settings not enough to fully load their cards or are they CPU limited . . . tons and tons of scenarios which really ought to have been tested properly before any conclusions darwn . . .
Okay, this is the last time I will make this point:
- SLI can STILL GIVE "GREAT" PERFORMANCE
- Adding a second card will STILL IMPROVE PERFORMANCE over the single card solution
- BUT... Adding the second card will NOT give the same real-world performance increase as you might expect from the raw FPS increase
NOTHING I have said suggests people can't have a good gaming experience with SLI setups. The only practical effect for the end-user is a slight devaluation of mid-range SLI setups in comparison to single high-end GPU setups.
I don't think its reasonable to make claims like the following that attempt to void the validity of classic FPS charts and could put potential punters off a SLI purchase based on "conjecture", "non-exhaustive testing" and the fact this could all be called by "Observer effect"? . . . I appreciate your efforts so far btw and good luck trying to get closure on this one way or another!
I already have closure on the issue, from a scientific point of view. I don't care if people are offended because it makes their hardware look a little less slick. It is what it is. I made my tool publically available to gather results from a wider range of hardware configurations. As a part of this I analysed the results in the hope of letting people make a more informed decision about their GPU upgrades. If you, or anyone else, chooses to ignore the results, disbelieve them, or even misinterpret them, then that's not my concern either.
----------------------------------------------------
Look, I'll answer any more specific questions you have about the phenomenon, the way I analysed it, or the interpretation of the findings. But please - enough with the "I don't buy it", or "your work sucks" type comments. I don't have time to get caught up in such petty arguments. If you think the analysis is incomplete - then complete it. If you believe that what I have shown is false - then disprove it. But really - I do this kind of thing for a living (data analysis of numerical phenomena), and have a PhD in the area, so have a little faith that I know what I'm doing here and that I'm not a complete moron
I have no pre-set agenda to promote or dismiss microstutter. It was an interesting and generally misunderstood phenomenon, and so I wanted to understand its behaviour. Now I do.