alwyuyang

After many tries, I would say it is the defect of the product. The same settings work yesterday, but today it does not work. For those getting similar issues, I wish you won't self doubt much. It works randomly, not a perfect product for eye tracking.

Like a girlfriend, she was angry with you😓

I am sorry to hear that. My one is still working as I checked it this morning. I didn't change any settings since our last discussion. I don't know if @Corvus can solve it.

@jboss Thanks, but I don't understand what is the "User Account Control" referring to. Could you explain about it? Is it the Steam Account or the PC admin account? Thank you.

Try this post, we did it:

Congratulations @DustProductions! I was admin account when I was stuck. Then I did what I suggested to you. Hence, I am not sure the admin account is necessary @Corvus . Hope the HTC Vive Eyer can make our life easier soon!

I just found my eye trackers worked. I removed all settings and applications and reinstall ViveProEye driver and SRanipal. And I went to the folders "Program Files/Vive" and "Program Files(x86)/Vive" to clean everything. Thank after reinstallation, I should have a folder like the photo attached. "SRanipal " should be under "Program Files(x86)/Vive", NOT under "Program Files/Vive". Anyway, the idea was to put together SRanipal and Vive driver under "Program Files(x86)/Vive" . Could you check in this way? It worked for me now.

@DustProductions Thank you. I hope so. Please keep us update if you got it.😀

Hello @DustProductions, exactly as you reported here, I am suffering. Do you have any new progress ? Thank you.

I have the same issue for a long time, very frustrating. Please share me if you solve it..Thank you so much. @Corvus

@stvnxu I need your help

Hello, I still have this problem unsolved, could you please give me a hand? @imarin18@Daniel_Obrien @Daniel_Y @Corvus Thank you.

I am suffering the same issue but still not fixed. How about you? Could you please give me a hand @VibrantNebula The issue I report is given at @Corvus @Jad

Dear @Daniel_Y, It succeeded before last Monday but it failed to work since then. I checked it with two different PCs but still the same problem. Do you know why? Another case when I ran the demo project provided in the SDK in “SRanipal_SDK_1.1.0.1-->02_Unity-->FaceGym-->FaceGym.exe”? Best regards, alwyuyang

Dear @原田空来 @PheonixLab @Jad @Nermeen @idontwantthis (I am sorry for repetively posting because I posted in a wrong place before ) My eye tracker suddenly doesn't work, could you explain me more in detail how did you fix the problem? I ran into the same problem. Thank you very much. I am frustrating also. Google translation from English to Japanese for @原田空来: アイトラッカーが突然動作しません。問題をどのように修正したのか、詳しく説明してもらえますか？ ありがとうございました

Dear @原田空来 @PheonixLab @Jad @Nermeen @idontwantthis My eye tracker suddenly doesn't work, could you explain me more in detail how did you fix the problem? I ran into the same problem. Thank you very much. I am frustrating also. Google translation from English to Japanese for @原田空来: アイトラッカーが突然動作しません。問題をどのように修正したのか、詳しく説明してもらえますか？ ありがとうございました

Dear Developers, @Daniel_Obrien @Daniel_Y @imarin18 @Corvus As a supplementary, here is the error I got when I was running my program (although I have posted in another place). [SRanipal] Initial Eye v2: NOT_SUPPORTED UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object) UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[]) UnityEngine.Logger:Log(LogType, Object) UnityEngine.Debug:LogError(Object) ViveSR.anipal.Eye.SRanipal_Eye_Framework:StartFramework() (at C:\Users\dn0855\Documents\UnityProj\Speed_Normal\Assets\ViveSR\Scripts\Eye\SRanipal_Eye_Framework.cs:104) ViveSR.anipal.Eye.SRanipal_Eye_Framework:Start() (at C:\Users\dn0855\Documents\UnityProj\Speed_Normal\Assets\ViveSR\Scripts\Eye\SRanipal_Eye_Framework.cs:59) The main problem is still the failing calibration. I don't why. I would appreciate it again if you could give me a hand on such an annoying issue. Best regards, Alwyuyang

Dear community developers, @Corvus @Daniel_Y @imarin18 I encounter an issue when I was calibrating the eye tracker. I started to launch the calibration procedure, and it asked me to "adjust your headset up and down to fit in the frame.". Then I adjust, but it stoped responding me. Normally, it should remind me when I make it; however, I am stuck in this page. If you know the possible issue, please give me a hand. Attached threee photos: 1. the solutions I am trying to follow, which didn't work; 2. my Nvidia driver information; 3. the page I am stuck in. Best regards, Alwyuyang

Dear @Corvus @Daniel_Y @Daniel_Obrien I get the following error which is different to what you mentioned. [SRanipal] Initial Eye v2: NOT_SUPPORTED UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object) UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[]) UnityEngine.Logger:Log(LogType, Object) UnityEngine.Debug:LogError(Object) ViveSR.anipal.Eye.SRanipal_Eye_Framework:StartFramework() (at C:\Users\dn0855\Documents\UnityProj\Speed_Normal\Assets\ViveSR\Scripts\Eye\SRanipal_Eye_Framework.cs:104) ViveSR.anipal.Eye.SRanipal_Eye_Framework:Start() (at C:\Users\dn0855\Documents\UnityProj\Speed_Normal\Assets\ViveSR\Scripts\Eye\SRanipal_Eye_Framework.cs:59) I have tried different solutions, but I continually get the error. What's can I do? The icon in the system tray on my computer is always brown color. Best,

Dear @Daniel_Y, Thank you for your response and it works. @imarin18 so here is an update. Best, Alwyuyang

Dear @imarin18, 1. I didn't try to collect the data during eye closeness but I will share you updates once I got another different value in order to deepen our understanding. 2 . "My personal opinion is that it would be better to use only the data with 31 on the validity data." ---I agree with this point if we all don't understand what "8" means in the output. Thank you for sharing your opinions to me, it helps a lot. Sincerely, alwyuyang

Dear @imarin18, I explain you with the corresponding output from the code block : data.no_user, data.timestamp, data.frame_sequence, data.verbose_data.left.eye_data_validata_bit_mask, data.verbose_data.left.gaze_origin_mm.x, data.verbose_data.left.gaze_origin_mm.y, data.verbose_data.left.gaze_origin_mm.z, data.verbose_data.left.gaze_direction_normalized.x, data.verbose_data.left.gaze_direction_normalized.y, data.verbose_data.left.gaze_direction_normalized.z, data.verbose_data.left.pupil_diameter_mm, data.verbose_data.left.eye_openness, data.verbose_data.left.pupil_position_in_sensor_area.x, data.verbose_data.left.pupil_position_in_sensor_area.y, data.expression_data.left.eye_frown, data.expression_data.left.eye_squeeze, data.expression_data.left.eye_wide // When it failed ( because validity number is 8, according to your assumption ) to measure the eye data, I got the corresponding output True 4205749 5008 8 0 0 0 0 0 0 -1 0 -1 -1 0 0 0 //When it measured sucessfully (because validity number is 31, according to your assumption), I got the corresponding output like: True 4205699 5002 31 34,31874 2,921722 -40,23471 -0,09350586 -0,1259155 0,9876099 4,649445 0,850469 0,4580182 0,6275682 0 0 0 Are you still reckoning that "8" suggests the valid data only for eye openness, because it seems that other eye data such as gaze_origin_mm, gaze_direction_normalized, and pupi_diameter_mm are also invalid.

Dear @imarin18, Thank you for sharing your opinions. However, 1, although the timestamp is not measured precisely, how could it jump from 62613 to 4205382 in two subsequent collection? 2, i agree with your explanation of "31". However, I also got uint64 "8" for the eye_data_validata_bit_mask when it failed to measure, then it seems hard to explain by the summing theory. writeLeftEyeData.WriteLine("{0} {1} {2} {3} {4} {5} {6} {7} {8} {9} {10} {11} {12} {13} {14} {15} {16} {17} {18}", Sample_MainThread.UnityTime, unixTime, data.no_user, data.timestamp, data.frame_sequence, data.verbose_data.left.eye_data_validata_bit_mask, data.verbose_data.left.gaze_origin_mm.x, data.verbose_data.left.gaze_origin_mm.y, data.verbose_data.left.gaze_origin_mm.z, data.verbose_data.left.gaze_direction_normalized.x, data.verbose_data.left.gaze_direction_normalized.y, data.verbose_data.left.gaze_direction_normalized.z, data.verbose_data.left.pupil_diameter_mm, data.verbose_data.left.eye_openness, data.verbose_data.left.pupil_position_in_sensor_area.x, data.verbose_data.left.pupil_position_in_sensor_area.y, data.expression_data.left.eye_frown, data.expression_data.left.eye_squeeze, data.expression_data.left.eye_wide ); I attach my code and the corresponding output file so you can see that I got 31 when it worked and 8 when it failed. Anything to comment? Thank you:) @Daniel_Obrien @Daniel_Y Best regards, leftEyeDataSub.txt

Dear @imarin18, I am checking the timestamp and frame_sequence, but I found the following the results in the log file. Column name: timestamp, frame_sequence, eye_data_validata_bit_mask row 1: 62613 4848 31 row 2: 4205382 4964 31 row 3: 4205415 4968 31 row 3: 4205457 4973 31 @Daniel_Y I don't understand why there is a huge skip from row 1 to row 2 regarding the timestamp. The row 1 is first output I obtained from the system. In addition, what does "31" means for the eye_data_validata_bit_mask? I only know it is uint64 data type, but how to interpret it? Thank you.

Thank you. It works for me.