I'm keeping it top secret until launch of the new TestUFO Lag Test in 2017
Otherwise, people will infer ideas of how I'm pulling it off, and beat me to this motion test.
I want to be #1 for a millisecond-accurate browser-based lag differential test.
As long as your TestUFO browser passes the Frame Skipping Test (perfect browser vsync), then the TestUFO lag test is capable of SMTT-accuracy.
flood wrote:afaik even if you specify the same refresh rate for crt/lcd, the actual values may be off by a tiny bit (i.e. their vblanks aren't synchronized)
whether this thing works depends on the how the os and graphics card handles stuff when cloning with the gpu
That's why a splitter is recommended. Just like for SMTT 2.0
However, there's a simple SLR photography test (short exposure photograph with two identical monitors, identical firmwares, and identical settings, on specific tests such as TestUFO Flicker Test) that verifies correctness of Cloning accuracy to <1ms for the particular tested inputs. I will be publishing instructions, for people who want to use Clone Mode instead of a simple splitter. That said, a splitter is obviously preferred since you don't have to wonder about scan sync. Once verified, Clone Mode can be used for either SMTT 2.0 or the TestUFO Lag Test. The clone sync issue is identical regardless of which Lag Test you use, but verifying clone accuracy is simple with a good short-exposure-capable SLR if you have two identical monitors for a clone sync verification. Accuracy of a sync check is better when holding the SLR upsidedown, due to rolling-shutter camera sensor scan direction opposite the display scan direction. (You'd be surprised at how rolling shutters interfere with the accuracy of SMTT 2.0... even a 1/1000sec shutter often scans in a 1/250sec top-to-bottom scan in a rolling shutter). There's clever tests to compensate for rolling-scan error in lag tests, and still get millisecond accuracy, but I'll keep quiet on rolling-shutter-error-compensation on these till the release, lest explaining how to compensate for rolling-scan-error reveals too much info on how I'm pulling this all off...
Also both SMTT 2.0 and the new TestUFO lag pattern equally require non-strobed-mode in order to be millisecond (or better