Finally installed the eye tracker on my 8kx. I installed the guppy express version and followed the instructions.
The Cali ration tool worked originally, but I had to re-install Pitool because the HMD was disconnecting.
Once in re-installed Pitool, AseeVR crashes in the middle of calibration and doesn’t get to the end where you look at the 8 or so dots to confirm calibration.
I have re-installed Pitool and aseeVR, but the calibration doesn’t complete.
Any ideas?
Thanks!
Ok-I downloaded just the.exe file from guppy express’s github and it fixed the calibration issue. 
Now how to get rid of the draw image1 and 2 windows on the desktop?
Hello,
I will ping @guppyexpress , he should be at here any moment to provide the solution.
That would bet awesome! I’ve run into another issue as well-neither iRacing nor MSFS2020 recognize AseeVR, so I am not getting any eye tracking in those apps. @mbucchia has been helping me track down the problem, but it may be the AseeVR installation itself, since the installation didn’t really go smoothly. I might need a little troubleshooting there.
Thanks!
No worries mate.
I spoke with him regarding your issue, so you shall receive a reply from him shortly.
Per user log, the call to aSeeVR_connect_server() with port 5777 does not complete successfully.
Re: OpenXR Toolkit support, @hammerhead_gal @PimaxQuorra, any chance I could get a loaner eye tracker module for my 8KX, or you could maybe sponsor a device for me 
so I can be on top of these issues and also add support to PimaxXR? (Asking nicely shouldn’t hurt ).
Thanks!
Hello,
We can figure the sponsorship though.
Please allows me to check with my team and come back to you later! 
Hello rsbell!
please visit
C:\7invensun\aSeeVR_UserSDK\runtime\devices\Pimax\config\EyeTracking.ini
please make it say
[GAZESETTING]#gaze算法的设置
Enabled=1
eyeType=1
fdimg=0
fdimgline=0
the reason for the eye images showing is due to popular request the eye images will be shown by default as more requested that it do than dont.
but it is able to be changed in a config
@mbucchia a long while ago AseeVR did swap to a new port system!
ports used are port 5347 and port 5777
if there is an issue with port 5777 please swap to port 5347.
the reason for this port swap is it is now on a less used port, this port allows for a lessoned error log buildup and less port noise the aseevr calibration software now runs on port 5347 as well as the built in OSC system.
as per most people using the original PimaxEyeTracker.dll i am assuming you are using it as well. if you need the latest dll for developers, please see here it is the dll attached, not the rest of the files.
Thanks for the reply. I’m using the aSeeVR API directly through the client DLL, no intermediate PimaxEyeTracker.dll.
Back in April/May that port 5777 worked, do you know when that change was made?
I see that struct aSeeVRInitParam has an array of 10 ports! Can I just specify both port 5777 and 5347 and the API will try them all until it can connect to one?
i mean. i havnt changed it port wise since then.
didnt know if 5777 stopped working for you for some reason. it shouldnt as thats one of the two ports used haha.
but if something did happen, it wouldnt hurt to try to ping both hahaha. of course that would be easier to bug fix with the module in hand haha
Thanks. That is quite unfortunate. @rsbell unfortunately I don’t have a timeline for you, while this is a simple change, OpenXR Toolkit is on a release model, where a new release takes weeks to make (because of testing and stability). I will ping you with a test build when I have a stable release.
Meanwhile, maybe you can try this and give me the output:
netstat -o -n -p tcp udp
This way we can see which ports are open.
Unfortunately it looks like there is a 2s seconds timeout, so this means for all users who don’t have eye tracker, trying both ports will add 4-5s loading time to the application.
Doesn’t give me the ports. Sorry I’m not more familiar with this.
C:\Users\rsbell>netstat -o -n -p tcp udp
Displays protocol statistics and current TCP/IP network connections.
NETSTAT [-a] [-b] [-e] [-f] [-n] [-o] [-p proto] [-r] [-s] [-t] [-x] [-y] [interval]
-a Displays all connections and listening ports.
-b Displays the executable involved in creating each connection or
listening port. In some cases well-known executables host
multiple independent components, and in these cases the
sequence of components involved in creating the connection
or listening port is displayed. In this case the executable
name is in [] at the bottom, on top is the component it called,
and so forth until TCP/IP was reached. Note that this option
can be time-consuming and will fail unless you have sufficient
permissions.
-e Displays Ethernet statistics. This may be combined with the -s
option.
-f Displays Fully Qualified Domain Names (FQDN) for foreign
addresses.
-n Displays addresses and port numbers in numerical form.
-o Displays the owning process ID associated with each connection.
-p proto Shows connections for the protocol specified by proto; proto
may be any of: TCP, UDP, TCPv6, or UDPv6. If used with the -s
option to display per-protocol statistics, proto may be any of:
IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, or UDPv6.
-q Displays all connections, listening ports, and bound
nonlistening TCP ports. Bound nonlistening ports may or may not
be associated with an active connection.
-r Displays the routing table.
-s Displays per-protocol statistics. By default, statistics are
shown for IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, and UDPv6;
the -p option may be used to specify a subset of the default.
-t Displays the current connection offload state.
-x Displays NetworkDirect connections, listeners, and shared
endpoints.
-y Displays the TCP connection template for all connections.
Cannot be combined with the other options.
interval Redisplays selected statistics, pausing interval seconds
between each display. Press CTRL+C to stop redisplaying
statistics. If omitted, netstat will print the current
configuration information once.
Sorry maybe try netstat -o -n -p tcp
Active Connections
Proto Local Address Foreign Address State PID
TCP 127.0.0.1:1042 127.0.0.1:49776 ESTABLISHED 6336
TCP 127.0.0.1:1042 127.0.0.1:49781 ESTABLISHED 6336
TCP 127.0.0.1:1042 127.0.0.1:49875 ESTABLISHED 6336
TCP 127.0.0.1:5347 127.0.0.1:51097 ESTABLISHED 4848
TCP 127.0.0.1:9012 127.0.0.1:49984 ESTABLISHED 4336
TCP 127.0.0.1:9013 127.0.0.1:49876 ESTABLISHED 4336
TCP 127.0.0.1:17532 127.0.0.1:49752 ESTABLISHED 5780
TCP 127.0.0.1:27062 127.0.0.1:50434 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:52895 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:52925 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:52929 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:52931 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:56283 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:63423 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:63429 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:63431 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:63434 ESTABLISHED 15028
TCP 127.0.0.1:27062 127.0.0.1:63437 ESTABLISHED 15028
Indeed no 5777 and just a 5347.
Basically the eye tracking service had breaking changes that are not backwards compatible. This broke support in OpenXR Toolkit.
Thank you @guppyexpress, changing to port 5347 worked!