Jump to content

VRDave

Verified Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by VRDave


  1.  wrote:

    No, no asus software installed.

    , I have a lot of USB continuous connect and disconnect issues myself.  These started when I simply changed to a new vive pro (I had to RMA another one because of a single bad headphone).  That said, I think there was an update to Vive Wireless at the exact same time.

     

    Anyhow, a re-install of Windows will do the trick (temporarily) as will uninstalling and re-installing the Vive Wireless software.  The easiest way for me (i.e., this is what worked for me), so I can actually play my Vive uninterrupted, is to go to Device Manager and remove the Intel WiGig device.  Then simply right-click your computer name at the top of the tree in Device Manager and select "Scan for Hardware Changes".  After this, fire up the Vive Wireless software and wait a few minutes while it re-attaches all the drivers.  I'll repeat this process:

     

    (again, this works for me for a similar problem)

    1. Open Device Manager.

    2. Go to the Intel entry and select it.

    3. Uninstall the Intel WiGig adapter.

    4. Right-click the computer name at the top of the tree.

    5. Select "Scan for Hardware Changes".

    6. The Intel WiGig adapter you uninstalled should re-appear.

    7. Plug in the battery to your Vive.

    8. Open the Vive Wireless software and let all the drivers install.

     

    After this you should get no USB disconnect for your next play session at least. 

     

    For me, I've been having to do this every now and then.  The errors I get are:

     

    1. In device manager, a yellow "warning" icon is next to 3-4 USB Composite devices.  All of these have Error 38, "previous instance of driver in memory" (or something similar).  NOTE: USB Composite devices are basically "created" by software - in this case, the Vive Wireless software.

     

    2. In the *System* Event Log, there is a row for each connect and disconnect cycle (Windows only tries this about 10-20 times then gives up), each with Kernel PnP error 219 - I can't remember the driver off the top of my head but I don't think the error thrown is perfectly representative of the problem.

    ------------------

     

    In any case, if you're having a connect/disconnect USB problem, give that a try.  And note that I have *not* had this happen once everything is connected successfully - I can play games/experiences/apps/whatever until the battery goes dead.

     

     

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

×
×
  • Create New...