Home Forums XR Discussions What would cause Gaze and Convergence data to become invalid?

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #19186
    Michael Duxbury

    Hi all,

    First time posting here, hope all are staying Safe, Sane and happy at the moment.

    I’m working on a piece of software that analyses the users movement and gaze within VR. However I’m occasionally getting invalid Convergence and Gaze data (as notified by the “TobiiXR_EyeTrackingData.ConvergenceDistanceIsValid” and “.GazeRay.isValid”). Apart from blinking, winking and any other act of closing ones eyes, what else might cause either of these flags to become invalid?

    Furthermore, I noticed that sometimes after finishing the act of blinking, the GazeRay.isValid flag would stay negative for a few frames. Is there a recommended amount of time that I should wait before continuing my analysis of the gaze data?

    Many thanks for taking the time to read this. All replies are welcome,


    Grant [Tobii]

    Hi @madmanmike, thanks for your query. When the valid-flag is set to false, the XR SDK can’t accurately determine the eye position.

    his can be due to for example blinking, bad positioning inside the headset, sharp angles, glasses frames hiding the eye, heavy makeup, etc.

    Our recommendation is to not use data where the accompanying valid-flag is set to false, because we can’t be sure that the data is trustworthy.

    Hope that clarifies our position, please let us know if we can offer any further information. Best wishes.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.