cancel
Showing results for 
Search instead for 
Did you mean: 

Resilient "Sensors can't track headset" error (update: they came around)

Knutsi
Protege
Update June 26th: I replied yesterday that I believed their last request was illegal in the EU/EAA (*) and they finally came around and told me that after a review of the case they would not send me a new headset. I got a tracking number today. UPS can still not see the package, but I choose to believe this is the end of this story. I will not post further updates unless this derails yet again. 

* You can read up on your rights here. I consulted a few people around me as well, who agreed this case was very bad. I have sent a request to a national consumer rights authority, but will cancel this if everything works out now.

Update June 25th
:  Oculus informed me today that "it looks like we were unable to replace just the headset at this time, and must replace the full kit instead". They now want all the items back despite explicitly saying otherwise initially. I will have to pay for the shipment myself, and the address is provided. The rep. is also saying there might be promotion credits as a thank you for my patients. Before I comply with this I need to check with my EU/EAA consumer rights organisations if they are allowed to do this. I believe they need to cover the cost of the returns of a broken product? In any event, this is outrageous, and all the burden in placed on the consumer. I'm five weeks in, and this process is preventing me from buying a new headset + the partial return made it hard to request a refund and close the whole process. This is without doubt the worst online retail experience I've ever had, and I want everyone to know they need to be very cautious ordering directly from this company. 

Update June 24th
: Oculus has still not sent my replacement. It's been a full month now. In two days it will be five weeks since the broken headset arrived, and I am still not able to use the headset I pre-ordered for release from Oculus.com. All this time they have not been out of stock.

Update June 19th
: The replacement for the pre-ordered Rift S headset that arrived broken (worked for 5 minutes) will now take more than a month to arrive to me. The package arrived in their facility before the weekend. Despite assurance the replacement would be sent immediately when they see the package "moving in the system", the replacement has not been sent from them yet. No matter how much problems they've had, 30+ days for them to replace something broken is not nice. (I dont live in a place where shipping takes long either - their facility is reasonably close).

Update June 8th
: shipping labels arrived two days ago, and I sent the package yesterday. 

Update June 4th
: Oculus Support (@OculusSupport) has still not sent the labels for the return of the broke headset, and their support notified me this night that "it looks like we have encountered a number of issues on the backend which have created some delays with processing replacements". I appreciate that they reached out to me to let me know this (the message was personal, not boilerplate), but the wait keeps adding up. They are basically saying getting a replacement will take a while. Meanwhile, new headets ordered from Oculus.com ship within a day, I've asked if I can just get a refund, and I could just buy a new headset from their site or retail.

Update May 31st 2019:
So they did yesterday decide to replace the headset, as expected. The time projection is my new headset will arrive within 10 days of returning the old one. The return label has not yet arrived (it will be from a local partner, I suspect), but I'll keep updating this post with what happens next. I'm happy there is some movement at least. 

Update May 30th 2019
:  Oculus support has still not committed to taking the headset back or replacing the cable, but said they are looking deeper into the issue at least.. They have once requested I run the log collection again, and sent a general notice they are overloaded. Since the OP was written I have tried the new firmware from the public test channel as well, and asked support if there was any way to hard reset the headset or its firmware/components (there was not). Let me also add that the two machines I tested the headset on have different architectures. One is a MSI VR-ready laptop, and the other a self built tower with a very recent ASUS motherboard targeted at gaming,.

Original post May 24th 2019: Just wanted to share the lack of progress on my apparently broken Rift S after discussing it with Oculus support today. So one important thing is that the headset actually worked for a few minutes when I first set it up, lost hand tracking and never recovered. On the next setup, it got stuck in "sensor check".

After trying everything from reformatting the disk and reinstalling Windows, using a different machine, different USBs 3/2, a powered hub, re-installing software, checking I was not running Windows N, ensuring camera privacy settings were right, restarting the service, and much more I got through to Oculus Support (on Chat) which today suggested:
  1. Re-installing the software in safe mode and deleting some folders in AppData etc.
  2. Trying to at least three times un- and re-plug the cable at the headset end, giving it one minute before reinserting.
The headset still does not get past the headset sensor check, and fails with the error in the screenshot. "Skip setup" leads to the headset having sound, but no tracking, and the video being three blinking dots, as seen in the video: https://www.youtube.com/watch?v=tphMVNJFN2E&feature=youtu.be 

The rep said the logs did not look like there was faulty hardware, but what else can it be at this point? The USB plug on the PC side of the cable gets very very warm. Maybe it's the cable, who knows. I'm awaiting a reply from them now.

fke37hl40orh.png8mvjsrd7p8qo.pngevlfk2sjcpx5.png560qcyh3uzbi.png
90 REPLIES 90

cafs1
Explorer


Ok, I just fixed mine. Hopefully this can help some of you too. I had to go into device manager, and change the driver for the ASMedia USB3.1 eXtensible Host Controller. For some reason, even though that controller works fine for other USB 3.0 hardware, it causes problems for the Rift S.

Right click it, choose "update driver", then choose "browse my computer for driver software". Choose "let me pick from a list..". Untick "show compatible hardware", choose "(standard USB Host Controller) from the menu on the left and select "USB xHCI Compliant Host Controller" from the box on the right.

This will replace the ASMedia USB driver with a generic USB3.0 driver from Microsoft. As soon as I did this, the Oculus Rift S sensor check worked fine, and I could use the Rift S without and dramas.


genius!!!! It worked

I3reeze
Honored Guest


Ok, I just fixed mine. Hopefully this can help some of you too. I had to go into device manager, and change the driver for the ASMedia USB3.1 eXtensible Host Controller. For some reason, even though that controller works fine for other USB 3.0 hardware, it causes problems for the Rift S.

Right click it, choose "update driver", then choose "browse my computer for driver software". Choose "let me pick from a list..". Untick "show compatible hardware", choose "(standard USB Host Controller) from the menu on the left and select "USB xHCI Compliant Host Controller" from the box on the right.

This will replace the ASMedia USB driver with a generic USB3.0 driver from Microsoft. As soon as I did this, the Oculus Rift S sensor check worked fine, and I could use the Rift S without and dramas.


Be cautious when doing this.
I tried this solution about a week ago and ended up having to reinstall Windows 10.
Replacing my Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft) with a Generic USB Controller seemingly broke all of my USB ports. Mouse and Keyboard could not connect once Windows was loaded. Thankfully, they were recognized before Windows was fully loaded, so I could get it to boot into Repair Options (hold shift when restarting). It wiped and reinstalled Windows 10, meaning everything had to be reinstalled.
I'm very hesitant to try a solution like this again.

weyyber
Honored Guest
Hey I am having the exect same problem, although I sometimes get it to connect randomly and play without a problem.
@KnutsiVRTV-twitch how did your story end? Are you able to play now?

Knutsi
Protege

weyyber said:

Hey I am having the exect same problem, although I sometimes get it to connect randomly and play without a problem.
@KnutsiVRTV-twitch how did your story end? Are you able to play now?


Sorry to hear you have the same issue. After testing the headset on two separate gaming-capable PCs and getting the same error, it became obvious that it was a hardware error. I got the headset replaced my Oculus, and the replacement has worked flawlessly ever since (:

I think in many cases the issue is related to other things. If it's intermittent it might be a USB issue, such as power? In any case, I recommend talking to support.  My replaced system has been wonderful, and I am very happy with the Rift S.

weyyber
Honored Guest
Ok thanks @KnutsiVRTV-twitch, I am so glad to hear things eventually worked out for you, enjoy:)

I already contaced them and I am now waiting for an answer. Can I ask you how long you had to wait in the end for your replacement?

Knutsi
Protege

weyyber said:

Ok thanks @KnutsiVRTV-twitch, I am so glad to hear things eventually worked out for you, enjoy:)

I already contaced them and I am now waiting for an answer. Can I ask you how long you had to wait in the end for your replacement?


The support was the worst customer relations experience I have ever had, and I don't say that lightly.

If you look at the first post in this thread, I posted updates along the way. It took several weeks, and ended with then making an unlawful request under EU customer protection rights.

I suspect you will get your support more quickly though, as the time I got mine was the release period of the S and the Quest and their support was overwhelmed ?

Will_i_am_Hunte
Honored Guest
Greetingz, i've the same Problem with the Rift S, now there is a Streak of Light 🙂

Its the USB Drivers, I've ASMEdia Drivers on my machine, my Rift S worked not really as expected, but it worked for a couple of Times... Here's my Solution

I've uninstalled my ASMedia-Drivers, restarted my PC. and let Windows install the newest USB Drivers (My old Drivers are from 2018, and the newer ones are from 2020) now my Rift runs as expected...

As a Troubleshooting Guide for ASMedia Users

1.Uninstall the ASMedia-Drivers and restart your PC
2. Head to Control-Center / Device Manager and let Windows search for the actual Drivers
3. Restart your PC again

My Rift S was always plugged in during the Process. Now i can use the HMD without any Problems 🙂

Before this Solution i've done always the same Steps

1. Reinstall / Repair the Oculus Software
2. Setting up the Rift S and getting stuck in the Sensors cant track headset-Struggle
3. Unplug and Plug-In
4. With Luck and 40 times of Step 1 the Rift S was running...

This was annoying and i've returned the Rift-S. I got a completly new Device and the same Problems...
Now 6 Months later i've tested the Solution posted by The_BassPlayer

and... It works perfectly 🙂

I hope this helps out

Will_i_am_Hunte
Honored Guest
After 4 Days of Intense Testing, the Solution works fine. The Rift S starts up and works as expected. No more Reinstalls of the Oculus Software, no more Blackscreens 🙂

I've noticed that the Rift S starts within a Second. Before i used this new Solution my Device takes up to 5 Seconds until start. No Audio Problems, no Problems with starts after Firmware Updates or Software Updates 🙂

Runs Smooth 🙂

justKirian
Honored Guest
this is my literal issue right now... tried using powered hub.. didnt work.

THANKS SO MUCH! THIS FIXED IT FOR ME!!!!
FINALLY.