10-08-2018 12:26 PM
Just brought home my vive wireless adapter
Installed my WiGig card
Installed the software
Paired up the wireless adapter
Headset not detected.
I've tried restarting the pc, restarting the wireless software, restarting the drivers but i cant get it to detect my headset. the LED on the side of the vive remains red and the screen remains off. I also tried using my original long vive cable inbetween the headset and the module but this gave no better results
HTV Vive Pre (with Deluxe Audio Strap)
Asus X99-E WS motherboard
Intel i7 5960X CPU
32GB ddr4 Corsair ram
Any ways to get more info on "why" the headset is not detected?
Are there any logfiles or other troubleshooting tools i can use besides the indicator "it no workie" ?
10-08-2018 12:33 PM
Make sure you do not have any of the cables/linkboxes or anything else connected at the same time as Wireless. SteamVR may detect those cables and search for a Vive connected to them.
10-08-2018 01:31 PM
MissStabby, I've had that happen a couple of times both wired and wireless. The first time it happened, wired, I rebooted SteamVR and it still didn't detect. I turned off the link box then ran SteamVR then turned the link box on.
Once you turn the link box on or turn the wireless battery on, you should hear the Win10 "detected" sound indications (three of them). If not, then my money is on a conflict or a problem with detection.
10-08-2018 02:10 PM - edited 10-08-2018 02:11 PM
I have tried to run it with everything unplugged but the wireless transmitter cable.
Without any good results.
Also turning my linkbox off and on as was suggested before, though this would be able to help me since any disconnection of the linkbox seems to throw a 308 error until i reboot my PC. (for the regular "wired" operation)
10-08-2018 04:28 PM
11-09-2018 03:36 PM
My Setup (Gaming):
Windows 10 64Bit
GeForce GTX 1080
Vive(A) with Audiostrab
Setup NR.2 (Work):
Windows 10 64Bit
GeForce GTX 1080Ti
Vive(B) with Audiostrab
I Having the same problem, but didn't connected the USB wrong. (Tested, disconnected the cables whom where connected to the adapter and put them in the wired Linkbox, therfore i got a proper working headset[Gaming]).
I had the oppertunity to test my wireless adapter on another PC/Vive (Work) setup, where the adapter worked very well.
On the Second Setup i saw right after succesful WiGig connection some USB installations, therfore i checked the Windows log an found that some drivers from DisplayLink, wherent installed on my first setup. Tried to install them afterwards and checked if the Display gets connected now, but still the issue as the OP.
11-09-2018 03:41 PM
You did disconnect all the other Vive cables, though right? No linkbox, just the wireless antenna?
11-09-2018 03:44 PM
Yes dissconnected the Linkbox and tried to connect the Vive(A) with the wireless adapter on my gaming setup, without Linkbox connected. => Didnt work
Had linkbox connected on my Work setup with Vive(B) & Linkbox connected => worked
11-09-2018 04:04 PM
GPU drivers are both up to date? Reinstall the USB drivers for the Vive and Wireless Adapter?
11-09-2018 05:57 PM - edited 11-10-2018 05:07 AM
On my Gaming setup GPU (1080)Driver Version: 188.8.131.521
On my Work Setup GPU (1080Ti)Driver Version 184.108.40.2061
Im not sure which one is the correct wireless adatper USB driver, but did the developer uninstall steamvr driver.
Still not working
Collected logs over
"Wireless System Info"
Found an interesting entry in HtcCU_xxxx_.txt:
"USB node not found"
3 weeks ago
I did the same thing, on a separate drive, then I figured out what the issue was.
For me, at least, the issue was Asus AI Charger. I actually had uninstalled it previously to try and troubleshoot.
But it turns out the .sys file was still lurking in my SysWoW64\drivers\ folder.
The only reason I noticed this, was I opened Device Manager, and noticed there was a warning from Windows on the root USB Hubs about a driver that failed to load, showing Aicharger.sys.
After that, it worked for the first time.
I reinstalled AI Charger, and then uninstalled again.
3 weeks ago
Check the previous suggestions and make sure you've tried them. Also, make sure your drivers are up to day and your BIOS has been fully updated as well.