The Tobii Driver compatibility

iPsych
Contributor

The Tobii Driver compatibility

Hello, My setting is below.

-HTC Vive Pro EYE

-NVIDIA Titan V 

-Unity 2018.4. Personal Edition.

 

Currently, No success with Any SDK except Calibration.

I tested SRanipal SDK with Unity example, Tobii Pro VR example.

Is there any compatibility issue with the Driver?

Nothing except already compiled calibration works.

 

If anybody succeed to implement the example to actual Unity project, please let me know the result.

Vive Staff

Re: The Tobii Driver compatibility

What calibration you run? From VR dashboard?

Please use SRanipal's Unity/Unreal plugin for Vive Pro Eye's content development.

sean_mann
Contributor

Re: The Tobii Driver compatibility

We're also having troubles. 

Our university partner has the Vive with Tobii Eye Tracking that we had to (expensively) purchase from Tobii a couple of months ago. We have their SDK implemented, but the new Vive Pro Eye does not work with that SDK. We were hoping the opposite was not true and that we could use the Vive with Tobii Eye Tracking with the new SRanipal SDK. It does not seem to work with FaceGym. We just get a blank screen after the robot head appears. Is the SRanipal SDK compatible with the Vive with Tobii Eye Tracking? Are there plans to unify these SDKs?

I'll upload some logs as soon as I get them back from our university partners. It was a VERY expensive HMD and they're going to be ticked if it's not compatible with the newer SDK!

@Corvus - tag added by moderator) 

sean_mann
Contributor

Re: The Tobii Driver compatibility

Any updates? Below is the log from Unity (Face Gym) but it doesn't say much, just the app says SRAnipal device not found.

 

Initialize engine version: 2017.1.0f3 (472613c02cf7)
GfxDevice: creating device client; threaded=1
Direct3D:
    Version:  Direct3D 11.0 [level 11.1]
    Renderer: NVIDIA GeForce GTX 1080 (ID=0x1be0)
    Vendor:   NVIDIA
    VRAM:     8079 MB
    Driver:   24.21.13.9731
Begin MonoManager ReloadAssembly
Platform assembly: C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\UnityEngine.dll (this message is harmless)
Loading C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\UnityEngine.dll into Unity Child Domain
Platform assembly: C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\Assembly-CSharp.dll (this message is harmless)
Loading C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\Assembly-CSharp.dll into Unity Child Domain
Platform assembly: C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\UnityEngine.UI.dll (this message is harmless)
Loading C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\UnityEngine.UI.dll into Unity Child Domain
Platform assembly: C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\UnityEngine.Networking.dll (this message is harmless)
Loading C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\UnityEngine.Networking.dll into Unity Child Domain
Platform assembly: C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\UnityEngine.Timeline.dll (this message is harmless)
Loading C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\UnityEngine.Timeline.dll into Unity Child Domain
Platform assembly: C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\Valve.Newtonsoft.Json.dll (this message is harmless)
Loading C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\Valve.Newtonsoft.Json.dll into Unity Child Domain
Platform assembly: C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\System.dll (this message is harmless)
Platform assembly: C:\Users\<redacted>\Desktop\FaceGym\FaceGym_Data\Managed\System.Core.dll (this message is harmless)
- Completed reload, in  0.022 seconds
<RI> Initializing input.

<RI> Input initialized.

<RI> Initialized touch support.

OpenVR initialized!
 
(Filename:  Line: 584)

UnloadTime: 0.596981 ms
[SteamVR] Loading actions file: C:/Users/<redacted>/Desktop/FaceGym/actions.json
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

[SteamVR] Successfully loaded action manifest into SteamVR
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Initializing steamvr input...
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Steamvr input initialization complete.
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Connected to lighthouse:LHR-6242035C
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

[SRanipal] Initial Lip : DEVICE_NOT_FOUND
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

[SRanipal] Initial Eye : DEVICE_NOT_FOUND
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Setting up 6 worker threads for Enlighten.
  Thread -> id: 2254 -> priority: 1 
  Thread -> id: 2600 -> priority: 1 
  Thread -> id: 45d0 -> priority: 1 
  Thread -> id: 2cb4 -> priority: 1 
  Thread -> id: fc0 -> priority: 1 
  Thread -> id: 2870 -> priority: 1 
[SRanipal] Release Eye : WORK
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

[SRanipal] Release Lip : WORK
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

OpenVR Shutdown
 
(Filename:  Line: 1253)

Vive Staff

Re: The Tobii Driver compatibility

Currently only the Vive Pro Eye is compatible with the Vive SRanipal SDK. I will follow up with more information about possible compatibility Tobii Eye Tracking.

HTC VIVE - Developer Relations Engineer
sean_mann
Contributor

Re: The Tobii Driver compatibility

Thanks. Seems like some major short-sightedness. Really don't want to be supporting 2 SDKs just because one person on our dev team has the older Tobii version. And they're reluctant to let it go because it cost a significant amount of money.