Help with resolving "Gaze Point not connected"

[shehan]

Hi All,

I'm using a GazePoint GP3 HD eye tracker running on Windows 11. The eye tracker works fine when using the GazePoint Control & Analysis software. I now want to use the eye tracker with iTrace.

I receive a "Gaze Point not connected" when I run iTrace-Core (screenshot attached).
Prior to executing iTrace-Core I have the GazePoint Control software running.

Can you let me know how to resolve/troubleshoot this issue?

Thanks,
Anthony

[shbonita]

Thanks @shehan for bringing up this issue. That message comes for a different reason. We are working on getting that message removed. For Gazepoint you have to do the calibration using it's own software and then you can use iTrace to record. Ignore that error in the console and see it it is tracking after the calibration.

Do you see the GazePoint tracker in the dropdown when connected? Also can you let me know which GazePoint tracker you have?

I have assigned @KangilPark to this issue and we will test it on our end and get back to you.

[shehan]

The GazePoint tracker does not show in the dropdown when connected. Only "Mouse" is shown in the dropdown.

We are using GazePoint GP3 HD eye tracker at 150Hz.

I was digging around, and something I noticed is that when I open the GazePoint Control software setting, the API address is different from what is hardcoded in the iTrace code. See the two attached images. Could this be the reason iTrace doesn't detect the tracker? I can't change the address in the GazePoint software; its read-only.

[samuel0correia]

I am also facing this same issue. However, currently, iTrace core is freezing during launch with the console only presenting:
"Gaze Point not connected!
Attempting to connect to Smarteye..."

About two days ago, when I was still able to launch iTrace Core, I was also not able to connect my Gazepoint GP3 device even when launching Gazepoint Control and running calibration.

[shbonita]

@wildpiggie thanks we are testing this on our end. Can you let us know what version of GazePoint software you have and what version of iTrace Core you are running?

It might be the IP addresses changed and we are working towards a solution for it.

[samuel0correia]

I am running Gazepoint Control v6.11.0 with iTrace Core 0.2.0 on Windows 11 (21H2)

[samuel0correia]

I would just like to add that I have tested a few different configurations which all didn't work.
I have tried using older versions of gazepoint control (with the oldest one I have access to being Version 6.7.0 (August 20, 2021)), on two different systems one running Windows 11 21H2 and another with Windows 10 22H2.

[michaeldejournett]

We found the issue you have been having, it is caused by the Gazepoint IP being different from what is found in the configuration in-app. For a quick fix you can go in and change the configuration manually if you are running ITrace-Core from VsCode. If not we are adding a user interface to change it from an installation.
If you would like, I could guide you through the quick fix for now, while I work on adding the necessary features. You can find where I made the issue here.