Vive Setup Download Failed

[Dimple Belousson]

As much as I enjoy the Vive when it works, it's getting really frustrating to use it regularly. My most common issue is the bluetooth link not working, which either causes the Base Stations to never go to sleep, or not wake up.

Clicking Restart obviously doesn't do anything. I tried power cycling everything. Link box first then stations, and the other way around. Tried uninstalling the drivers and re-installing them, unchecking the "use bluetooth" in the settings and re-checking it.

Is there a magic solution I'm unaware of? A very specific sequence of actions to make this work, ideally without having to do it everytime I use the Vive? The Base stations are quite loud so putting them to sleep is pretty important (not to mention power consumtion), and I would like to avoid un/plugging them from the wall everytime I want to jump into VR.

I was having this problem too, I gave up on the bluetooth thing and turned off that feature, I just have my lighthouses plugged into a switched power bar (one for each lighthouse) and at one of them, I also have the Vive's power plugged in also. So when I'm not using the Vive, I just turn off the two power bars and unplug the Vive's USB. Everything's been working well since, that Bluetooth option seems to be more of a pain than what it's worth. I did have it working decently at one time, but after a SteamVR update, it never did work properly afterwards, there has been many SteamVR updates since but I just can't be bothered to have the headaches to get it to work properly.

The Vive system is composed of about 9 different USB drivers, including Bluetooth, controllers, camera, receivers and audio, among others. Due to different reasons, like software updates, change of connections, system updates or malfunction of a device, the USB drivers might get into conflict and reinstalling them is a good way to get everything back to its working state.

Note: This list includes the drivers of the devices directly connected to the computer by USB, as it is the HMD and Link box. Controllers and Base Stations are connected to the headset through Bluetooth and then to the computer, so these devices are not going to be visible on this list.

Try the steps above and see if that works for you.

After doing that everything seemed to have went back to normal, but after a few days the issues came back - sometimes not waking up from sleep (forcing me to unplug and then replug the base stations), and sometimes not going to sleep.

So I never got the bluetooth base station power management to work, until today. I moved the link box USB plug from my USB 3.1 to one of my USB 3.0. And now it properly identifies my base stations when I scan for them.

I had this problem as well. I followed most of the guides on here and it would only temporarially fix it. After a while someone mentioned here or another forum that it might be windows bluetooth or the onboard bluetooth interfering. It actually was. In windows 10 I went to settings then airplane mode (don't turn airplane mode on) and turned off bluetooth in there. That turned off the windows blue tooth and it fixed my problem.

Not the problem with this is, is it turns off blue tooth everything but the vive bluetooth. I am personally alright with this, but others might not be depending on how you use stuff. I use corded everything so I don't need bluetooth for anything else.

Hi, I followed the tutorial and tried to install the SRanipal, but I failed the first time as my account is not a admin. But the second time when I am using an admin account, I encountered the Error 1001 problem.

I think @nickie123 gives a pretty clear explanation. The problem is likely due to the incomplete installation or uninstallation. I have tried all the solutions I can find online but still have no luck. I really don't wanna reinstall my computer just for this SDK. Any advice would be appreciated.

I found a fix for this today, if you look into the directory in which SRAnipal is being installed, usually Programfiles/Vive, then go into the SRAnipal directory and copy everything out into a temporary directory. Allow the installer to fail, and delete everything within the SRAnipal directory, (this may lead to you needing to kill a running sranipal process). Then, copy everything from your temporary directory over to the original SRAnipal directory and execute the sr_runtime.exe. This worked for me, and no clean boot is needed. Seems the error is thrown after the actual install process, so nothing is missing even though it didn't 'complete the install'.

I'm having a similar issue. We've recently upgraded from a wired vive setup to a wireless adapter paired with the vive pro. In the old setup viewing was smooth at ultra setting. The new setup with the vive pro and wireless adapter has what I would describe as "lag" at the ultra setting. My initial thought was that the wireless adapter was the cause of this lag. I have done both wired and wireless tests with the vive pro and found both connections to have this lag. After reading this thread I reduced the rendering quality but still saw lag up until the draft setting. I switched back to the standard vive headset and viewing was smooth at any setting.

This makes me believe that the increased resolution of the vive pro is the cause of my "lag" and possibly everyone else's "glitch". I have not experienced lag in any program other than the enscape stand alone files.

Kyle

I just sent my wireless receiver back per Htc's recommendation. I've spent about 2 to 3 hours with their tech support (awesome tech support). I have a vive pro with wireless and was getting lag in both games and Revit. I am not sure, but it appears that multiple sessions of the Vive software start running (looking with Microsoft Task Manager) with these clitches showing up. I'm running a new AMD treadripper 12/24, EVGA 2080Ti, 32 Gigs of ram off of a 1 TB M2 drive. Calculations have not been an issue. I could switch back to hardwired and all cleared up. I think it could be in the basic wireless technology.through it all I changed multiple times between wireless and hard wired, with consistent failure on wireless. I will report back when my new receiver comes in.

We've been able to reproduce some of the issues you've reported with our VivePro when it's running in wireless mode. Explicitly worse latency and reprojection artifacts (which lead to tearing/distortions of the image). These issue were a lot less visible when running on draft quality, so it's very likely that they're mostly performance/frame rate related.

Since Enscape is doing exactly the same thing when running in wireless or wired mode there's unfortunately not much we can do on our end the moment. We'll get into contact with Htc/SteamVR on that matter, since it's likely a hardware/driver specific issue of the wireless setup.

I'm also doing work with Vive Pro and Vive Wireless. One important note that we discovered is that currently the Wireless adapter does all video compression using CPU resources. This means that if you are running something that is very CPU intense, this will starve the Wireless adapter of CPU cycles to meet it's compression frame rate.

Have you guys heard back from HTC on this?

It's probably a massive change required in how enscape fundamentally works to incorporate how the wireless headset actually decompresses /transmits the data.
Weird one. I look forward to hearing about any developments on this. Good or bad. Always - Feedback IS progress.

Thanks guys!

I am having the quality issues mentioned here, as well as another problem. When I am running Enscape with our HTC Vive wireless headset, I am unable to make any keyboard or mouse inputs without having it crash. This happens whether I am running an .exe or running live from Revit. With the tethered headset, I could do this without ever experiencing a crash.

This is important, because we often have clients that are unable or unwilling to teleport by themselves (I'm still amazed that pointing and pulling a trigger is beyond the capabilities of some people). I will need to either move them through the project with the WASD keys, or select saved views for them. I cannot do either with the wireless headset due to the crashes.

c80f0f1006