Jump to content
 

Atiash

Verified Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Atiash

  • Rank
    Contributor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've been doing an absurd amount of fiddling with it, and I was wondering if it's possible for either the cable or the link box to be responsible for this? Because the one thing that consistently gets it to fire up is to unplug the box completely, uninstall the drivers through SteamVR and restart, and then plug it all in. But this only works for ~10 minutes before the same issue re-occurs.
  2. Unfortunately neither of those things have contributed results. Fiddling around with the driver types sometimes gets it to reinstall correctly, but only after a few tries. A friend of mine is having the same issue but only after a recent windows update. After any power cycle or sleep cycle, it begins to fail again. Update** I have fixed it once again by going into device manager, forcing it to install as a USB Composite Device, and then hitting update and search internet for driver. After doing this for about 15 minutes, it decided to install the correct ones. However I would not consider this a permanent solution. I still would like assistance in either understanding this problem or permanently fixing it. Update 2 This no longer works.
  3. Alright so, let me preface this by saying that I've tried troubleshooting it for hours and I just can't get this thing to stop fussing. So I was using my Vive Pro for about two hours, then I set it down to go and have myself a nap. During this time, the computer went into sleep mode and now the headset unrecognized by the system. So I have this grand old problem where the device in the Device Manager/Universal Serial Bus Controllers is known only as Unknown USB Device (Device Descriptor Request Failed) Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed. You know, that whole deal. Now no matter what port I plug it into, how many times I power cycle it, restart my computer, uninstall the drivers, manually assign the drivers or anything like that, it does not work. Here's where it gets interesting! The Vive Pro's red light is on, which tells me it has power. Additionally, the cameras are being picked up by things like Discord, and are fully functional. And we'll top that off with the controllers still sync to it when they are turned on. But wait, there's more! The standard vive headset works flawlessly using the same cords AND the same ports! This implies that it's a driver issue with the pro, now the question is how does my computer going into sleep mode destroy the driver so badly I can't fix it? I really enjoy using the Pro, I don't want to have to send it away or anything because of some ridiculous error. *Edit* Some more information. When SteamVR fails to detect the headset, I have tried rebooting it, and the service status message fails. I have tried running different cords and everything, even going so far as to run the link box without the headset at all. This issue only arises when the headset is connected to the link box. Every single time I put it into a new usb port, the only thing that installs is the camera. The rest fails to install.
  4. Now that the incoming sound has been addressed and hopefully fixed, will you be addressing the microphone aswell? I don't know about anyone else here, but the audio quality from the microphone is atrocious. It's by standard using a generic usb audio driver, as if the device itself installed none.
×
×
  • Create New...