[Vive_SRWorks_Demo doesn't run on PC with Titan V]

@mstengel

You could leave a request in this thread List of Supported GPUs for v0.8.5.0.0 beta program.

[Accuracy over distance]

Accuracy is 0.5°~1.1° within FOV 20°, not related to distance. Eye surgery, eye disease, heavy makeup, and high myopia may affect eye tracking performance.

 

@dagillespie

[An error may occur in Unity.]

May I have your detailed test scenario? always been reproduced?

[Room Scale VR/AR integration of real world objects]

A simpler way,

1. Perform 3D reconstruction like this video first and save the scanned result as OBJ.

2. Reload the OBJ into you scene.

3. Through SRWorks Unity API, ex: GetAllHorizontal(Vertical) / GetLargestHorizontal(Vertical) / GetColliderWithProperties( property array ), to get your desired collider property for your virtual object placement.

 

4. Or, you could even perform 3D Semantic Segmentation like this video to find wall or floor. A Sample code provided in Experience_Unity > Assets > ViveSR_Experience > Scenes\Sample9 – Semantic Segmentation.

 

[Problems running SRWorks in Unity]

The current version on developers website v0.8.0.2 does not support Turing architecture, ex: RTX 2080. You could leave a request in this thread, List of Supported GPUs, for Beta trial program.

[Problems running SRWorks in Unity]

May I know your SRWorks version and GPU model?

[The camera resolution]

It is same as Vive Pro EYE.

[The camera resolution]

May I know what is your display resolution?

Vive Pro Eye's front camera is a fisheye camera in 640x480 and HMD's panel is 1440x1600 per eye, so it may not be as good as seen in the desktop display.

[Update 1.1.2.0 eyelids getting stuck???]

Do you use EyeData.timestamp in your code? 

 v1.1.2.0 addressed an issue existed in v.1.1.0.1 that returns a wrong unit of timestamp. If you did your own workaround for it in your code with v.1.1.0.1, it may have unexpected behavior with  v1.1.2.0.

[Enable Eye Version]

v2 is recommended.  The major differences are

1. O-mouth is split into multiple blend-shape for better animation
2. To support Tongue
3. To support eye's Wide blend-shape

[SRWorks's Camera latency]

vivecosmos"s passthrough is different pipeline from SRworks with vive pro.

The passthrough latency of SRWorks with Vive Pro is ~ 100ms since v0.7.5.0.0.

 

[Pro eye unsuitable for research - data SUPER heavily filtered during fixation.]

 @marcellotham

VIVE_SRanipalInstaller_1.1.2.0.msi + SRanipal_SDK_1.1.0.1.zip

[Pro eye unsuitable for research - data SUPER heavily filtered during fixation.]

It has been addressed in SR_runtime to v1.1.2.0. please update it here, https://hub.vive.com/en-US/download.

[See Through module doens't work in some environments？？]

camera feed will stop if HMD has tracking lost.

[Expanded depth map refinement]

You could try Eroding and Dilating in OpenCV to remove small islands, referring to https://docs.opencv.org/2.4/doc/tutorials/imgproc/erosion_dilatation/erosion_dilatation.html

[measure Eye IPD data]

If you do not plan to use SteamVR, what way you use to render the content to HMD?

[Eye expression data]

"eye_frown" and "eye_squeeze" data has not been supported in the current version.

[Vive Cosmos can't use SRWorks?]

@wky1995 SRWorks is not formally supported on the Cosmos at this time. We will have more communication about SDK support on Cosmos in the coming weeks.

[measure Eye IPD data]

SingleEyeData as its name you can only know single eye's information but without the relation between 2 eyes. Thus, you need to use OpenVR API to know the current distance of 2 lens of HMD, i.e IPD.

[How to get output from the eye-tracker faster than Update in Unity]

There is callback mode supported in 120 FPS now after check "Enable Eye Data Callback" as the figure shown below; And, then register a callback function by SRanipal_Eye_v2.WrapperRegisterEyeDataCallback(). Could refer to its usage in sample included in SDK.

 

 

[measure Eye IPD data]

After you performance eye calibration, you could read IPD via SteamVR/OpenVR.

[SR Works GPU]

Leave your request for v0.8.5.0 in this thread List Of Supported GPUs

[Point of regard]

@yanscheu You could consider your gaze vector mapping to HFOVxVFOV is ~110 degree covering 1440x1600 resolution per eye although it is not precisely because it is distorted image shown on LCD panel via a Fresnel lens to your sight.

[Is it impossible to get eye images with an infrared camera?]

No, it is not allowed.

@yayumura

[List of Supported GPUs]

One possibility is due to OpenCL is not configured correctly on your PC. You could use a tool like GPU-Z to check if OpenCL is detectable on your PC..

@Mila