USB 3.0 Eye Tracking Module Setup

Unfortunately too soon to say. In it’s current state? I would say no.

1 Like

Ok thx :shushing_face:

1 Like

It’s doesn’t work very well with current PiTool/aSeeVR software so I unmounted mine (left the magnet rings on though as they’re not in the way).

Hopefully it’ll be fixed in an upcoming release… :wink:

3 Likes

yeah, mine is still unopened in the shipping box. I have to get an RTX card before I could make use of it, but based on the reports so far it is not worth bothering with at this time anyway

2 Likes

I have the same problem. i askes me to delete v08 before installing v10. But first i would like to save the config files you mentioned…
Would be nice to hear where that config directory is. i could not find it. neither i the aseevr folder, nor in the pimax folder…

2 Likes

just a little up in this thread
https://community.openmr.ai/t/usb-3-0-eye-tracking-module-setup/30514/232

C:\7invensun\aSeeVR_UserSDK\runtime\devices\Pimax\config

2 Likes

THANKS! my install is under C:\Program Files\aSeeVR\runtime\devices\Pimax

2 Likes

did copy the config folder over, but it´s not working
amcap captures in 640x480@120hz

EDIT: for some reason the IR lights do not light up… hmm what a pimax mess again…

tried with amcap again and if i switch to 640x480@120Hz the device disconnects after a couple of seconds…

1 Like

I am fairly sure I am using 1.0.0.10 (need to double-check once I get home). I am using PiTool 1.0.2.084 (which IIRC is just *1.0.1.264 bundled with PE 0.6) so it should have downloaded aSeeVR 1.0.0.10.

I had the same issue you reported (2 green dots for 1 second and then black squares) when I was connected directly to my PC using a USB-C cable. After connecting to the headset instead (with the included cable) I was able to calibrate.

2 Likes

You are (I’m on the same version that came bundled with PiTool 1.0.2.084 or rather was downloaded for it):
image

2 Likes

good find, i guess thats the reason 1.0.0.10 worked for most(?) people, when hardware and calibration data already exits (1st try with internal usb of hmd) the external usb 3.0 connected eye tracking can run a calibration
the way i mounted it makes it hard to connect it internal again so i only tested with external usb

2 Likes

hello everybody, i got my eyetracking today , is it worth it to install it ?

using 8kx

1 Like

I tried it from the uninstalled state, and did additional trials.

  1. I connected the ET to the USB port of the HMD with the included cable,
    and installed the software 10.0.0.10 from pitool 1.0.2.084.
    Result: Calibration and DFR work fine, wow!

However, in my case, it doesn’t connect to USB3.0 anyway, even if I flip the plug.
Therefore, it operates at 30Hz. This included cable only looks like it’s acting as USB 2.0.

  1. Then I connected the ET directly from the PC with USB3.0 without uninstalling the software.
    Result: Calibration does not work (two greens disappear).

It doesn’t seem to fit in my case. I took this opportunity to try a little more.

  1. I copied only GearVrCfg.ini from the 10.0.0.8 config folder.
    Result: Calibration and DFR work fine, this is 120Hz.

  2. I connected the ET to my PC via USB 2.0.
    Result: Calibration does not work (two greens disappear).

  3. I reconnected to the USB port of the HMD.
    Result: In the calibration, the green of the left eye disappeared and the green of the right eye remained. Calibration is not complete.

  4. I removed GearVrCfg.ini and connected the ET to my PC via USB 2.0.
    Result: Calibration does not work (two greens disappear).

In my case, it works in the following cases, and something goes wrong in other cases.

30Hz operation:
When Connecting ET to HMD ports with the included cable (only USB2.0 is possible), and there isn’t GearVrCfg.ini in the config folder.

120Hz operation:
When connecting to USB3.0 directly to the PC and placing 10.0.0.8 GearVrCfg.ini in the config folder.

In GearVrCfg.ini, direct or reflection, monocular or binocular, single or double image, etc. are defined by two numerical parameter (vrType, cameraType), and also there are many parameters.

IMO, the interpretation of several parameters may have been unintentionally changed in the connection way (internal or external, USB3.0 or USB2.0), and resulting in disjointed behavior.

Edit: reformat and fix mis-translate.

3 Likes

if thats the only important file then we are down to few lines of text in one file
thats the content for my usb 3.0 120Hz
(all comments marked with # are removed)
GearVrCfg.ini

[MASK]
vrType=0
cameraType=3
vid=12308
pid=17435
cameraWidth=640
cameraHeight=480
imageWidth=640
imageHeight=480
cutType=1
leftRotation=3
leftFlip=0
rightRotation=3
rightFlip=0
brightness=2
exposure=371
gain=21
fps=0
ledLevel1=53
ledLevel2=64
ledLevel3=53
ledLevel4=64
tpid=17156
delay=0

[CONTROLCAMERA]
minExposure=371
maxExposure=371
minGain=21
maxGain=21
maxStep=10
idxType=1

[FRONTCAMERA]
vid=5546
pid=5461
cameraWidth=640
cameraHeight=480
imageWidth=640
imageHeight=480
rotation=1
flip=1
brightness=3
exposure=0
gain=16
fps=0

1 Like

I just wondering how many of you were wearing glasses when calibrating the eye tracking, I can pass it easily without glasses but having problem calibrating with glasses, not sure if it’s because of the frame or the light reflecting material, so it seems I still can’t benefit most of the VR functions with glasses afterall.

1 Like

i’d have to go back to my 5k+ to try it, and it’s too hideous to go back to for the moment.

Actually (off topic) , so i went back to pitool 261 so i can play Asgard again. And the 8kx image went back to underwhelming.

I think my initial reaction was because of the old pitool(261).

the latest pitool looks way higher res somehow. ill have to switch back to confirm.

EDIT ok so I just tried going back to the latest PiTool and I cant explain it but the quality of visuals just looks better somehow.

4 Likes

I came back here to ask the same question. Scrolling through the comments, doesn’t seem like it.

Hey dude , I also went back 261 to play stormland , I’d been saving it for the 8kx , but it looked terrible, lots of low res textures mixed with high res character models and proformance was crap , really hope the new PT will fix all this :thinking:
Also glad your enjoying your 8kx now it is a big jump forward :grinning:

3 Likes

yes im whelmed. but not overwhelmed. but is certainly better than underwhelmed.

I fired up Project Cars 3 and no matter what settings i was struggling to stay above 30 fps.

Game looked worse than my 5k+ Im going to try it on the quest 2 tomorrow. If it runs full res and smooth it may be more fuel on the “FOV isn’t everything pyre”

3 Likes

Mmmm I’m running dirt rally no pops, looks and feels great, might just be that game , also did you go for the eye tracking? I got mine but am waiting for a new PT to install it, that could make a huge difference to the game settings and smoothness! ( I hope ) :rofl: :rofl:

1 Like