Home Forums Software Development Get Eye XYZ Position – cannot find the functions for TX_INTERACTIONBEHAVIORTYPE_ Reply To: Get Eye XYZ Position – cannot find the functions for TX_INTERACTIONBEHAVIORTYPE_

Robert [Tobii]

Ok, thank you for clarifying. Let’s see if I can get you up and running again…

1) Regarding the weird data from RightEyeX and RightEyeY: From the symptoms you describe, it sounds like the Tobii.EyeX.Client.dll is not in sync with the header files. Please check so there is no old version of the Tobii.EyeX.Client.dll laying around somewhere in the output folder.

To make it easier to use the eye position data stream using the EyeX SDK for C/C++, we have added a new minimal code sample. It will be included in the next SDK release , but you can download it now if you want to try it out before that. EDIT: The new code sample in the EyeX SDK for C/C++ is called MinimalEyePositionDataStream.

2) Regarding synchronization of data streams: You are correct that the EyeX SDK is designed to deliver the different data streams asynchronously. The reason for this is that the EyeX Engine API is designed with consumer eye trackers in mind, where it is not guaranteed that the eye position data stream will be delivered with the same frequency as the gaze point data stream. It is technically possible to build some sort of synchronization functionality into the EyeX Engine API, but it is not prioritized in the short term. (As you might know, our current focus of the whole EyeX initiative is the gaming use cases, where synchronization between data streams has not been any important requirement so far.)

If your app is dependent on getting all data in a synchronous batch, you need to take care of the synchronization yourself, i.e. handle gaze point data and eye position data in different callbacks, put locks in the correct places etc. As an alternative you can also evaluate the Gaze SDK if you think it suits your needs better. The current version of the Gaze SDK delivers all data synchronously and will not change in the same pace as the EyeX Engine API and EyeX SDK:s.