In general, the eye-tracking latency works out to be the sum of:
Eye Camera exposure time (~8 ms) + USB transmission time (~8 ms) + processing time (~4 ms)
Therefore, the current latency of FOVE Eye Tracking is about 20 ms.
In practice, the total latency becomes:
+ however long it takes the application to use the eye tracking data and update
+ however long it takes until the screen to displays the next frame of the application
Which is more in the range of ~40-50 milliseconds for a complete turnaround from eye movement, to application reaction, to new image being displayed on the screen. However, the pure eye-tracking data is available much sooner than the complete turnaround time.
Various factors can affect the latency, especially the OS, and most especially the UVC camera driver. We've seen, for example, situations where the Windows UVC driver emits two frames at a time. The eye-tracking time stamps emitted from the FOVE SDK (as of v1.0) are taken upon receiving the camera frame from the OS.
Our eye-tracking algorithm uses some internal filtering but this is kept as minimal as possible so as not to affect latency much. As of v1.0, no predictive algorithms are in use by default.
A third party research paper by Niklas Stein also provides measurements of FOVE's latency, as well as comparisons with other HMD eye trackers.
視線カメラの露光 (8ミリ秒) + 情報伝達 (8ミリ秒) + 解析 (4ミリ秒)
第三者による論文(Niklas Stein, https://journals.sagepub.com/doi/full/10.1177/2041669520983338)にも、Foveとその他のHMD型アイトラッカーとのレイテンシ等の比較があります。