VRDave

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.

wrote: No bsods but the vive headset goes black and steam vr software loses tracking of everything. the wireless adapter itself continues to stay connected to the link box. Cpu - Ryzen7 1700 mobo - Gigabyte GA-AX370-gaming 5 Gpu - GTX 1080 Hey , it looks like you and I have a very similar set up (mine listed earlier in thread). My SteamVR has behaved a little wonky at times as well both wired and wireless. I've had it not find or lose the tracking but that is usually during startup or if I let it sit idle. To fix it, I would usually just re-start SteamVR or disconnect and reconnect power (either battery or link box if not on wireless). That said, I *have* had it lose everything when I first set it up - it was the antenna. I had it clipped to the monitor and at one point it snapped off and fell behind the monitor. A few seconds later, everything was gone in SteamVR. I now have it on top of my case (Antec P110 Luce) in the *back* part of my tracking square. And the case is elevated ~2' off the floor. I haven't lost anything since. On a semi-related note - I'm a software Dev and one of my programs deals with wireless hardware. I've had clients with a myriad of problems, RF from the monitor being one of them. Of course the wireless device I deal with is way weaker than the Vive wireless but it's a thought to consider I guess.

wrote: I have the same problem, its getting way to hot. I meanwhile created something to prevent the heat from spreading downwards, hopefully a temporary workaround. Below are graphs of my last 2 game sessions. (snip) Nice information there. I haven't had a problem with heat issues because I run a ceiling fan on high while playing (directly over play area). This is in Houston, with high temps and high humidity and upstairs in the house (though, A/C *is* on, the humidity is still felt a bit upstairs). Unfortunately I need to pull out the fan because I keep smacking it and don't want to destroy my controllers. I will probably mount one nearby as it seems good airflow pulls the heat off of the wireless.

wrote: I have a Gigabyte GA-AX370-Gaming K7 and it doesn't work on mine. I don't think it's a very good idea to suggest people go out and buy a new motherboard to solve a compatibility issue that blatantly needs to be handled by the manufacturer of the product. whynotboth.jpg The good or bad idea is wheather or not one chooses to act on it and it is subjective at that. My Vive-pro starter kit came in before the system was built and the wireless 5 days after. There is *nothing* on the system but drivers (updated), Win 10 (updated), Steam/Steam VR, Vive software and a smattering of VR games. And the wireless worked fine as soon as I plugged it into the PCIEX4 slot. If someone has time and $100 and thinks another motherboard may be the answer, they have the info. On another note, our MBs are almost identical with the exception of the K7 being an Overclocker's board. Plugging the WiGig card into PCIEX8 does not work - again, my guess is that it is related to the fact that it is sharing bandwidth with PCIEX16 which is certainly where the vid card is plugged in. PCIEX4 worked fine - and I think I made a mistake in the last post - the PCIEX4 is a 2.0 slot...and the card works fine). NOTE: I contacted support *before* pre-ordering my wireless adapter and asked about the compatability of the PCI slots in the ax370 Gaming 5 (again, same config as the K7) and he said: "Regarding your inquiry, I want you to know that the PCIe WiGig card is compatible with x4, x8, and x16, but personally, I would like to recommend you to connect it to the x16 or x8, as it will run a lot better. It might work in the x1 but we cannot assure you that it will work smoothly, nevertheless, you can use it with x4, x8, and x16." Also, to try and provide more helpful info for your board - I was using the drivers that came with the MB and then updated to the current drivers (18.10.20 - we should have the *exact* same drivers for D/L from Gigabyte). Both the old and the newest drivers were no problem for the WiGig and adapeter. Specs (again): Gigabyte GA-AX370 gaming 5 Ryzen 7 1700 16gb DDR3200 Samsung EVO 970 1TB Gigabyte GeForce GTX1080 8GB (D5X) Win10

wrote: wrote: Hi All, Thank you to everyone that submitted the info I requested earlier. I wanted to send a quick note that all configurations are being examined by our engineering team and partners. As soon as I have an update I will post here. Thank you, JohnG (snip) I've tried placing the wGig card in socket 1 and sockets 2 and 3 (with the GPU in either 1 or 2, depending) and in every configuration, no matter weather I've forced PCIe Gen 3 speeds and/or 4x4x4x4x socket splits in my BIOS, I can't manage to make my system detect the wiGig card at all. Unlike some reporters with larger mobo's, I don't have a downclocked unstable x1/x4 socket; I just straight up can't get the card to be recognized in any of the x16 sockets that it aughta work fine in. I've seen a poster on reddit with pretty much the exact same issue with the slightly larger model of this motherboard (that does have the smaller pcie socket), except he can also repro the unstable system using the smaller socket (in addition to not being recognized in the larger sockets). Would be great to know when this gets fixed, since I doubt I'm going to be watching this thread like a hawk. I don't know if this helps but I managed to get mine to work in the 4x Gen 3.0 slot on my board (full slot). It would *not* work in the 8x slot which shares bandwidth with the 16x slot where my vid card is located - it would not be recognized in this slot. Take a look at which slots are sharing bandwidth, maybe that will help? I never tried it in a 1x slot. When it recognized and worked in the 4x, slot, I didn't tempt fate and try further configurations. Gigabyte GA-AX370 Gaming 5 Ryzen 7 1700 Gigabyte GeForce GTX1080 8GB D5X BTW, that GA-AX370 Gaming 5 is relatively cheap now and it seems solid - if anyone is looking for a quick solution (that costs a little bit).

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.

wrote: System crashes shortly after starting in Steam VR. AMD Ryzen 7 1800X Eight-Core Processor Crosshair VI Hero NVIDIA GeForce GTX 1080 Ti Striiker, what NVIDIA driver are you using? I have the same MB chipset (though your MB has more "oomph" than mine) and a GTX1080. The only stable drivers for VR thus far, that I can find, are 388.13. The 416.16 almost nuked my card (as in burned it up...the fans wouldn't run). Also, and I feel dumb for saying this but *I* miss little things all the time - make sure you didn't put the WiGig card in the PCI slot that shares bandwidth with your video card. I did that initially and got "jack" out of the card. I had to move it to a Gen 3, 4x slot.

Well, I got mine up and running. I used the link provided by Jeremy_SC2 (5th page) as a guide. I don't see the specific PCI settings in my BIOS but I did put it in an x4, Gen 3 slot. The main thing I notice is the slight fuzz that is really noticeable when in the blank/bland loading area between games or environments. I hope that is just a setting - the monitor mount was maybe 5-6 feet away. Gigabyte GA-AX370 Gaming 5 Gigabyte GTX1080 Ryzen 7 1700 Note: if you have similar, watch out for anything beyond the NVidia 388.13 drivers. I tried the 416.16 and almost fried my video card (the cooling fans do not work with that driver for some reason).

wrote: Mine seems to be working now. It was crashing every 10-30 min. I moved the wigig card to another slot and it got way worse, then I moved it again and I haven't had a crash since. Ryzen 7 1800x AsRock AB350 PRO4 What slot did you move it to? 8x, 4x, etc.? My adapter will be here today. I'll post back when it is up and running (before sunday).