MB Geek

Hey, I'm up for trying anything at this point ... if you told me I have to sacrifice a chicken I'd deal with the stain on my carpet LOL. I'll follow up when I can. Using the link box has helped but not entirely fixed the issue.

At this point the only thing that would work is a class action lawsuit ... they are selling a $300~$360 product with a widespread and known issue and do nothing about it. Just in this thread alone is enough to show that it's not any one PC setup or incompatibility, but inherent in their hardware. Anyone know where to start one?

POSSIBLE and I'm going to stress POSSIBLE FIX!!! So after reading of other people having the issues and realizing that it's not limited to a CPU, motherboard, video card type or whether it's a base Vive or Pro I saw that someone had said they did not have the problem using the Cosmos, which doesn't use the lighthouses as it has inside out tracking. So that got me thinking that therefore it's a lighthouse based issue. Saw that people were having the problem with both 1.0 and 2.0 lighthouses, so that made me think that communications with the lighthouses is getting wonked. For giggles I hooked up the original link box for the cables via USB 3.0 and the power plug with nothing else attached and then installed the bluetooth drivers and setup for the lighthouse power to be controlled via Steam VR. Tested that the lighthouses were powering up and down when starting and closing Steam VR and they were. The main problem I always had was after starting a game, within 7~10 minutes the HMD would go grey and I would here Windows losing and re-finding the hardware which could take anywhere from 20 seconds to a minute or two, and would get the grey drop out randomly after that. Now? I have tried it over a dozen times, rebooted, the whole enchilada and now at the same 7~10 minute mark (I use fpsVR as a timer) I get a 2~3 second black screen and it comes back ... and then no other drops during the whole play session, and at the moment it's been EVERY TIME, which it me is WAY more livable. Don't hold me to this as everyone's mileage may vary and I thought that changing the headset channel fixed it and it ultimately turned out to be wrong, but if everyone can give it a shot (as I'm guessing most people still have their link box sitting somewhere) and report how it does, maybe even if it doesn't work for everyone it can narrow it down.

POSSIBLE and I'm going to stress POSSIBLE FIX!!! So after reading of other people having the issues and realizing that it's not limited to a CPU, motherboard, video card type or whether it's a base Vive or Pro I saw that someone had said they did not have the problem using the Cosmos, which doesn't use the lighthouses as it has inside out tracking. So that got me thinking that therefore it's a lighthouse based issue. Saw that people were having the problem with both 1.0 and 2.0 lighthouses, so that made me think that communications with the lighthouses is getting wonked. For giggles I hooked up the original link box for the cables via USB 3.0 and the power plug with nothing else attached and then installed the bluetooth drivers and setup for the lighthouse power to be controlled via Steam VR. Tested that the lighthouses were powering up and down when starting and closing Steam VR and they were. The main problem I always had was after starting a game, within 7~10 minutes the HMD would go grey and I would here Windows losing and re-finding the hardware which could take anywhere from 20 seconds to a minute or two, and would get the grey drop out randomly after that. Now? I have tried it over a dozen times, rebooted, the whole enchilada and now at the same 7~10 minute mark (I use fpsVR as a timer) I get a 2~3 second black screen and it comes back ... and then no other drops during the whole play session, and at the moment it's been EVERY TIME, which it me is WAY more livable. Don't hold me to this as everyone's mileage may vary and I thought that changing the headset channel fixed it and it ultimately turned out to be wrong, but if everyone can give it a shot (as I'm guessing most people still have their link box sitting somewhere) and report how it does, maybe even if it doesn't work for everyone it can narrow it down.

LOL ... then I apologize also, didn't realize that you were sincerely trying to help. I have taken the extra card out and had the same issue. I update the driver to the latest almost as soon as they are released and none have made a difference. Also despite everyone and their mother claiming that 'SLI is dead' I see significant verifiable performance gains in almost everything I run and that includes in VR . That being said I appreciate the effort to help but it's definitely something deeper.

And I heard smoking is bad for you as well ... You think I (we) haven't tried that? LOL Gimme a break here Anyone have a Vive Pro, or a 20 series Nvidia card have the same issue? Since I would find it hard to believe it's EVERYONE that has the wireless (I would expect a greater uproar) and just in this small group it been determined that it's not motherboard/CPU dependent , I'm just trying to find a common denominator.

Chronuss I am still having the problem. I do NOT overclock anything . Also happens with the stock battery and the larger one I have identically. The problem is consistent enough that it makes me believe it is some hardware combination issue but I have yet to find a common denominator. Just to repeat in case any of the devs are listening or care (LOL), I have changed motherboard and CPU AND reinstalled a fresh copy of Windows 10 and the issues still occurs just as before. I'm am thinking that it is a lighthouse issue (I have a Vive which was on release date so they would be the first revision) but could be the headset also. I'm not in the position to buy the upgraded lighthouses and don't even know if I could, but is it still really annoying to this day

Don't hold your breath for a fix, I've been part of a thread on this support board for well over a year now with similar issues ( see 'Vive wireless adapter disconnects after a few minutes' ) and not a peep of help I upgraded my CPU and motherboard with no luck ... I'm out of ideas but going back to a cable is not going to happen so I'm stuck with the annoyance @VibrantNebula @jagibson

I am using the index controllers but this was happening prior to that. I also have 1080's in SLI but a regular Vive (leading me to believe again it's nothing with the headset itself as you are using a Pro) ... anyone else using SLI? I have tried turning it off with no help ... now I wonder if I should remove one card and try it.

Galatoni, same issue here with the exception that it always comes back for me so in your case, I'd be screaming bloody murder LOL. Pretty sure it's not a computer hardware related issue (with our rigs as we have shown it happens on completely different chipsets) and I've done a fresh install of Windows 10 and same issue. Now my gut is thinking it's the wireless hardware itself ... I got mine on preorder, how about you?

Still waiting ... LOL

Issue still exists, upgraded the BIOS and to a Intel 9700k and same issue. Changing the channels does NOT work (as Galatoni has said) and my problem is EXACTLY as they state and have tried the same things ... it cuts out once and then it's OK. To me the timing seems to be about 5~10 minutes into a session. Guessing it is WAY down on the priority board. It is annoying but not fatally so, but still would like a fix. Would also wonder if it happens with the Cosmos headset @VibrantNebula @Synthesis

I "WAS" still having the problem but then I found in the wireless settings "Connection Mode" so for giggles I set it to mode 3 and have not had the problem since. I will update if that changes. However my specs are as follows; ASRock Z370 Gaming K6 motherboard i7 8700k 32 gigs 2666 GSkill memory 2 Zotac Nvidia 1080 cards (I've tried SLI on and off) SSD M2 hard drives (a Samsung 960 and a 970) I urge anyone having the problem to try changing the connection mode and see what happens and post here. Little confused as to why in all the time of reporting the issue that no one at HTC has even mentioned it exists ... :P

I'm in the same boat, even got the Valve index controllers (and was hoping that the Steam VR update might fix it 'accidentally) and the same issue. I feel silly having to start up the VR and then wait for the 'new hardware' sound to happen before putting the headset on. Something tells me we're not getting a solution. The tech in me tells me it's a motherboard chipset issue. My motherboard has a Intel Z370 chipset, what does everyone else have?

My problem has been similar from day one of installing the wireless. After a couple of minutes the headset goes black, I hear my PC losing the device and then refinding it, the headset comes back and works fine until the end of the VR session. New VR session, same thing happens again. The period of time before it goes out has seemingly become shorter after the various software and firmware updates but still happens every time