Jump to content

Daniel_Y

Employee
  • Posts

    251
  • Joined

  • Last visited

Posts posted by Daniel_Y

  1. 1. Yes, you need to lauch  eye tracking calibration from VR dashboard first.

    2. refering this thread for coodinate explaination, https://community.viveport.com/t5/Vive-SRanipal-SDK/Vive-Pro-Eye-Finding-a-single-eye-origin-in-world-space/m-p/31592#M10

    3. Refering to eye tracking accuracy in VIVE PRO EYE SPECS, https://www.vive.com/eu/product/vive-pro-eye/

    4. Combined gaze may be more fit your use scenario.

     

  2. A eye_data_validata_bit_mask defined in struct SingleEyeData to indicate which data's validness listed below. Usually, the data becomes invalid when eye closed.

     

    enum SingleEyeDataValidity {

    SINGLE_EYE_DATA_GAZE_ORIGIN_VALIDITY,/*!<The validity of the origin of gaze of the eye data */

    SINGLE_EYE_DATA_GAZE_DIRECTION_VALIDITY,/*!<The validity of the direction of gaze of the eye data */

    SINGLE_EYE_DATA_PUPIL_DIAMETER_VALIDITY,/*!<The validity of the diameter of gaze of the eye data */

    SINGLE_EYE_DATA_EYE_OPENNESS_VALIDITY,/*!<The validity of the openness of the eye data */

    SINGLE_EYE_DATA_PUPIL_POSITION_IN_SENSOR_AREA_VALIDITY/*!<The validity of normalized position of pupil */

    };
×
×
  • Create New...