alwyuyang
-
Posts
38 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Blogs
Events
Store
Downloads
Posts posted by alwyuyang
-
-
1 hour ago, DustProductions said:
Ok, I MAY have figured out a root cause in my case. It seems to be related to having too many USB devices active. I noticed this error when I had my headset half on and half off while debugging just now. My guess is that the eye tracker was not able to initialize because the usb controller couldn't be loaded or something like that. The HMD was otherwise was working fine, but maybe the eye tracker was right at the threshold for me. I'm not sure HOW I managed to max it out, as I don't have 127 things plugged in to my machine, but I did a restart and unplugged a few phones and things, and it worked first try.
So, to prevent my particular issue, you might want to make sure you don't have too many USB devices plugged in to your machine. 🤦♂️
Like a girlfriend, she was angry with you😓
-
40 minutes ago, DustProductions said:
Well, bad news. After having it work for about 2 weeks, it suddenly stopped working again. I'm met, once again with Initialization failures, images of the "Move headset up" graphic, with the headset not moving anywhere and, a new thing, the headset not even showing up on the graphic, and instead it just telling me to move my headset to match with an empty dotted line. No idea what causes each of these states to happen, but I am not able to get calibration working either on my admin account, or otherwise. I also checked to verify in SRanipal got installed again in the wrong folder, and it did not appear so. At this point, I'm fresh out of ideas again. At least I was able to demo it working a few times for the client. This could potentially be related to a SteamVR update that happened within the last week? It worked last Wednesday, and now it doesn't. If anyone else makes any progress on this, please let everyone know. @alwyuyang, does it still work for 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.
-
29 minutes ago, jboss said:
I got rid of the popup by disabling User Account Control completely. This is of course not what you want and also not what you want to tell your customers.
On the other hand, one of the partners that I develop for does not report the issue, so it could be related to which account is used when installing the Vive software. Other threads also suggest that running it when looged in with the Windows administrator account works (which is the actual Administrator account, not a user account with Administrator properties, I guess, so also Run As Administrator will not help). I also noted before I disabled UAC that if I had allowed it once it woulld run without popup for subsequent checks. But as soon as I restarted the PC it needed permission again.
@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.
-
On 5/12/2020 at 10:44 PM, tamu.bhp said:
New HTV Vive user. I'm having the same issue here. I've tried some of the things in the first post but my PC is for work and I have to take it to IT for anything installation-related so I'm hoping to avoid that. I do have the SR_Runtime going as an admin (had them remote in for that). Still fails to initialize the calibration for eye tracking. Any updates?
Try this post, we did it:
-
11 hours ago, DustProductions said:
@Corvus Ok, I did a full wipe and reinstall, and it still did not work. I then did what @alwyuyang suggested and moved the SRAnipal folder to be in the x86 VIVE folder, and it still did not work. I THEN closed everything down, and signed into a sysadmin account on my computer with full privileges, and that worked. Even though I tried each combination of running both SteamVR and SRAnipal as an administrator on my account, that did not work. It wasn't until I went to the full admin account that it succeeded. After I succeeded on the sysadmin account, I went back to my account and ran it, and it succeeded again. So I have no idea what all is being done during the setup of the eye calibration, but it seems to need an account with full administrator privileges on the first go. I'm guessing it creates some stuff that a lesser account can use after it's succeeded once.
The bad news in all of this is that this is a really poor workflow for commercial / research usage, as most companies and universities I know of do NOT allow their users to have full administrative privileges on their PCs. So even though I have succeeded getting it working on my machine and will be able to write the code and test it here, it's not likely to work on their machines due to this restriction.
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!
-
1 hour ago, Corvus said:
@DustProductions Thanks for sharing the logs.
@alwyuyang & @Nermeen Have you tried the steps in the troubleshooting post? If you're still having issues please post or PM a SteamVR system report and the eye tracking logs.
https://forum.vive.com/topic/6482-vive-pro-eye-calibration-initialization-error-troubleshooting/
SteamVR System Report: In SteamVR, go to the Settings > General, click Create System Report, and click Save to File.
Eye Tracking Logs: Right click runtime robot notification icon > click Pack log and Save
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.
On 4/15/2020 at 3:04 PM, alwyuyang said:Hello, I still have this problem unsolved, could you please give me a hand? @imarin18@Daniel_Obrien @Daniel_Y @Corvus
Thank you.
-
9 minutes ago, DustProductions said:
@Corvus I sent you a PM with the requested information.
@alwyuyang I do not have any progress other than the logs showing it's not detecting my eye tracking sensors. No idea why it is not detecting them, the HMD is definitely a Pro Eye and it has the sensors around the lens. Hopefully something useful will come out of me sending my logs to Corvus.
@DustProductions Thank you. I hope so. Please keep us update if you got it.😀
-
On 5/21/2020 at 9:59 PM, DustProductions said:
Yeah, I have the same problem. The eye calibration is not working properly, no matter what I do, it does not calibrate. Half the time it gives me the Initialization Failed problem, the other half it just hangs at the positioning part. It tells me I'm low, so I move it up until the headset isn't on my head. It tells me to move it in the frame, and the headset is pictured in the frame. Honestly, it looks like the gaze calibration is a pretty big issue at this point considering all of the various threads about it. I don't know what I'm supposed to tell my client other than the Vive Pro Eye you spent thousands of dollars on for your research doesn't work.
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
-
35 minutes ago, Daniel_Y said:
Has it succeeded before or it always fails?
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,
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,
-
On 2/24/2020 at 2:46 PM, imarin18 said:
Dear @alwyuyang
As in the following thread, the combined data are not supported at this point.
Best regards,
imarin18
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 0Are 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.
-
3 minutes ago, imarin18 said:
Dear @alwyuyang
As explained in the following post, the timestamp cannot be correctly measured with the current SDK version according to the technical support team.
If I understand correctly, I reckon that the value of validity follows the table below. If you sum all the decimal digits (1+2+4+8+16), you get 31. Though again I am not sure if my understanding is correct.
Enumerator
Binary digit if valid
Decimal digit if valid
SINGLE_EYE_DATA_GAZE_ORIGIN_VALIDITY
00001
1
SINGLE_EYE_DATA_GAZE_DIRECTION_VALIDITY
00010
2
SINGLE_EYE_DATA_PUPIL_DIAMETER_VALIDITY
00100
4
SINGLE_EYE_DATA_EYE_OPENNESS_VALIDITY
01000
8
SINGLE_EYE_DATA_PUPIL_POSITION_IN_SENSOR_AREA_VALIDITY
10000
16
Best regards,
imarin18
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:)
Best regards,
-
21 hours ago, imarin18 said:
Dear @alwyuyang
I suppose you can get the validity data from "eye_data_validata_bit_mask" in your code. The type of the output is UInt64, not bool.
Best regards,
imarin18
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
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.
-
On 2/18/2020 at 5:04 PM, imarin18 said:
Dear @alwyuyang
No I have not got any response to the question. However, I suppose that the following document from Tobii might help us understand, though I am not sure about the mechanism of HTC VIVE Pro Eye.
Best regards,
imarin18
Thank you. It works for me.
Vive Pro Eye Calibration Initialization Error Troubleshooting
in VIVE Eye and Facial Tracking SDK
Posted
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.