DustProductions

This worked for me. I was able to "repair" SRanipal and get it installed. Thanks!

I too am having this problem with the latest SRanipal installer. I think it got to this point because the VIVE setup tool never completed and I clicked out of it after waiting for like 30 minutes when it said "1 minute until finished" or something similar. I have tried a few things to get this to work. I noticed that when "repairing" the install, it will add the files to the folder, but then it hits the 1001 error and removes them. My thought was I could try to kill the installer after it put all the files on the drive and see if it worked. Unfortunately, it looks like it's much the same. I get the following when trying to run sr_runtime.exe Which makes sense, because I killed the installer. So when I try to run the uninstaller, I get this: which looks very similar to the other ones... I also tried running CCleaner, and it found a bunch of stuff in the registry that I removed, but unfortunately this did not resolve the issue either. Any assistance would be appreciated here. EDIT: I also tried removing everything VIVE and SteamVR related through Add / Remove programs and Steam. This did not solve the issue.

Ok, nevermind on the second part about the callback, I just noticed this callback doesn't work yet. Looking forward to that functionality. Still wondering about the bad performance during calibration. @Daniel_Y

Hey folks, I've been running into an issue when launching my calibration from my Unity application. Here's what I expect to happen: Click on the button in my application to launch calibration Calibration launches as overlay I go through complete calibration Calibration succeeds Here's what is actually happening: Click on the button in my application to launch calibration Calibration launches as overlay I go through complete calibration Calibration usually fails I am able to complete calibration by launching it from the SteamVR menu within the HMD. I've noticed the framerate of the calibration seems very low and slow when running it from my application (though my application itself is performant). It seems like having both things running at the same time is a problem. My background application is attempting to access gaze information when it is running, so this could be part of the problem as well. I looked through the logs and found this: [EyeCameraModule] [2020-06-09 15:52:45] [LOG] eyefeature thread alive [EyeCameraModule] [2020-06-09 15:52:46] [LOG] do InitialCalibration [EyeCameraModule] [2020-06-09 15:52:46] [LOG] [Calibration] IPD config [EyeCameraModule] [2020-06-09 15:52:46] [LOG] do StartCalibration [EyeCameraModule] [2020-06-09 15:52:46] [LOG] [Calibration] Start [EyeCameraModule] [2020-06-09 15:52:46] [LOG] [Calibration] Clear [EyeCameraModule] [2020-06-09 15:52:49] [LOG] EyeCameraDevice::Process, alive [EyeCameraModule] [2020-06-09 15:52:50] [LOG] [Calibration] Collect [EyeCameraModule] [2020-06-09 15:52:55] [LOG] [Calibration] Collect [EyeCameraModule] [2020-06-09 15:52:58] [LOG] [Calibration] Collect Error : 13 [EyeCameraModule] [2020-06-09 15:53:00] [LOG] eyefeature thread alive [EyeCameraModule] [2020-06-09 15:53:00] [LOG] [Calibration] Collect [EyeCameraModule] [2020-06-09 15:53:03] [LOG] [Calibration] Collect Error : 13 [EyeCameraModule] [2020-06-09 15:53:05] [LOG] [Calibration] Collect [EyeCameraModule] [2020-06-09 15:53:07] [LOG] EyeCameraDevice::Process, alive [EyeCameraModule] [2020-06-09 15:53:08] [LOG] process alive [EyeCameraModule] [2020-06-09 15:53:09] [LOG] [Calibration] Collect [EyeCameraModule] [2020-06-09 15:53:12] [LOG] [Calibration] Collect Error : 13 [EyeCameraModule] [2020-06-09 15:53:13] [LOG] do ReleaseCalibration [EyeCameraModule] [2020-06-09 15:53:13] [LOG] do ReleaseCalibration Presumably "Error : 13" is the problem. Can you please tell me what Error 13 is? On a related note, launching the calibration allows passing a pointer for a callback via: SRanipal_Eye_API.LaunchEyeCalibration(IntPtr callback); But this is a little too low level for me to understand how to use. Are there any examples of how to use this callback in C#? Right now I'm just passing IntPtr.Zero to it, but it would be nice to know when calibration completes, and it would be especially nice to know if calibration succeeded or failed so I can put it on the monitor for the researchers. Cheers!

Makes sense. It's plugged in to the USB3 and the Vive device is also plugged into a 3.0 port.

Sent you the logs. I checked my motherboard user manual, and don't see anything about whether it's xHCI or not (https://us.msi.com/Motherboard/support/Z97S-SLI-Krait-Edition#down-manual). It might be worth noting that I'm plugged in to a USB on the front of my case, so the motherboard USBs probably aren't relevant anyway. Not a whole lot of really technical information available about the case USBs either. For what it's worth, I'm plugged in to a USB 3.0 port on the case. The case is an AeroCool-800.

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. 🤦‍♂️

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?

@TimmyVonMoerkel Unfortunately not. I was not in my Unity application when it worked the first time, I launched the Eye Tracker after a fresh reinstall in my Windows Admin account from the HMD / SteamVR menu. I was not in my application when I launched it, my application / Unity was not running at all. But after I had my successful calibration, I was able to go back to my non-admin account and run it both from the Steam VR / HMD and my application. I don't think I launched SRAnipal before I launched the calibration. I let the calibration launch it. One other thing I noticed was that even though I moved SRanipal from the Program Files folder to the (x86) folder, is that it was still launching from the non-(x86) folder (in other words it was reinstalling itself there somehow). It didn't actually work until I was able to make that stop happening. How did I make that stop happening? Unfortunately I can't remember, but I eventually got it to stop installing in the wrong spot.

@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.

@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.

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.