We've just started rolling out a possible fix for the repeated sensor disconnection issue. This is a problem that could cause the sensor to disconnect while idle on certain hardware configurations. Although we had some trouble reproducing the exact problem in our lab, we have a good idea of what the core issue was and believe it may be resolved.
Some customers have already received the update, and everyone else should have it within a few hours. The update should happen automatically, but you'll have to just unplug and replug the sensor to reset its state.
I'd recommend people wait until later this evening to test and see if the fix actually resolves their issue. Either way, please report back so we can understand if the fix was a success. Thanks.
1.10 seems to be worse than 1.9. With 1.9 it seemed that Oculus reported they couldn't find the sensor, but tracking seemed to work and restarting the Oculus softwaer would get the sensor back. Now tracking no longer works when it loses the sensor, and the sensor won't come back on a restart. Oculus can't see it, even though 'Rift Sensor' is listed in Windows Device Manager.
I'm almost at the point where I'll have to pull my Vive out of the closet again.
@ftonin my I5 is also overclocked to 4.2GHZ, for me it was definitley the bad original W10 Microshit USB 3.0 eXtensible Host Controller driver. since i changed it to Intel original W7 driver i had no more problems at all.
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
